Agenda-2018-06-11

From EGIWiki
Jump to: navigation, search
Main EGI.eu operations services Support Documentation Tools Activities Performance Technology Catch-all Services Resource Allocation Security


Documentation menu: Home Manuals Procedures Training Other Contact For: VO managers Administrators


General information

Middleware

  • CMD-OS 1.2.0 released http://repository.egi.eu/2018/05/23/release-cmd-os-1-2-0/
    • cloudkeeper 1.6.0 (NEW) - Cloudkeeper checks the EGI App DB for new or updated images that need to be supported on the site. It downloads images and registers them with OpenNebula, so that they can be used in resource instantiation.
    • cloudkeeper-os 0.9.9 (NEW) - Cloudkeeper-os is able to manage OpenStack cloud - upload, update and remove images and templates representing EGI AppDB appliances. cloudkeeper-os runs as a server listening for gRPC communication usually from core cloudkeeper component.
    • cloud-info-provider 0.9.1 - makes OCCI optional, avoiding failures if no OCCI endpoint is configured; updates on documentation, now stored on a dedicated EGI Foundation github store
    • found dependency problem with cloudkeeper-os (UMD team on it) https://ggus.eu/index.php?mode=ticket_info&ticket_id=135539
  • CMD-ONE upgrade in preparation
    • cloudkeeper, cloudkeeper-one, cloud-info-provider need Early Adopters on OpenNebula 5


Preview repository

to be released a new update containing: frontier squid 3.5.27, xrootd 4.8.3, gfal2 2.15.5, APEL 1.6.2

Operations

ARGO/SAM

FedCloud

  • starting decommissioning campaign for old OpenStack and OpenNebula versions: all software must follow the Service Operations Security Policy, so out of support software/versions should go through decommissioning procedure https://wiki.egi.eu/wiki/PROC16
  • 23 sites: 15 Openstack, 7 OpenNebula; OpenNebula 4 to be decommissioned, OpenStack <Ocata and !=Mitaka/Xenial LTS to be decommissioned
  • EGI Operations is going to asking sites about plans (no hard suspensions) for the update to a supported version (timeline, which version, feedback (using CMD? Using dockers? Using FedCloud appliance?) )

Feedback from Helpdesk

yearly review of the information registered into GOC-DB

2018-05-09

On a yearly basis, the information registered into GOC-DB need to be verified. NGIs and RCs have been asked to check them. In particular:

  1. NGI managers should review the people registered and the roles assigned to them, and in particular check the following information:
    • E-Mail
    • ROD E-Mail
    • Security E-Mail
NGI Managers should also review the status of the "not certified" RCs, in according to the RC Status Workflow;
  1. RCs administrators should review the people registered and the roles assigned to them, and in particular check the following information:
    • E-Mail
    • telephone numbers
    • CSIRT E-Mail
RC administrators should also review the information related to the registered service endpoints.

The process should be completed by June 6th.

To track the process, a series of tickets has been opened.

Status on June 11th: 12 Solved, 4 in progress. out of 32 NGIs

Notifications from ARGO about the nagios probes failures

In the process of implementing the notification system in ARGO, it was introduced the following changes in GOC-DB:

  • Notifications flag at the site level
  • Notifications flag at the service endpoint level

In this way ARGO will retrieve from GOC-DB the information about the sites and services whom sending the email notification and the related recipients.

The logic of the notifications is the following:

Site Service Notify?
Y Y Y
Y N N
N Y N
N N N

If there isn't any email contact defined at the service endpoint level, it will be used the site contact. Please review your contacts.

You can enable the notifications.

NOTE: It is not mandatory for the sites

Monthly Availability/Reliability

  • Underperformed sites in the past A/R reports with issues not yet fixed:
  • Underperformed sites after 3 consecutive months, underperformed NGIs, QoS violations: (May 2018):
    • no new A/R violations, several Qos Violation: decided not to open new tickets:
      • AsiaPacific: very urgent and top priority
      • NGI_ARMGRID: urgent
      • NGI_CHINA: top priority
      • NGI_FRANCE: very urgent and top priority
      • NGI_IL: urgent
      • NGI_IT: top priority
      • NGI_NL: top priority
      • NGI_PL: very urgent and top priority
      • NGI_UK: top priority
      • ROC_CANADA: very urgent

suspended sites: none for OLA violation

Decommissioning EMI WMS

WMS servers can be decommissioned. Please follow the procedure PROC12. The plan is:

  • Starting from January 2018, put the WMS servers in draining: this will block the submission of new jobs and will allow the jobs previously submitted to finish
    • inform in advance your users that you are going to put in draining and then dismiss the WMS servers (as per PROC12)
    • there might be several VOs enabled on your WMS servers: in case only few of them need to use the service for few weeks more, you might disable the other VOs
  • On Dec 14th EGI Operations sent a new broadcast to the VOs reminding the users the forthcoming WMS decommission
  • From March, the nagios probe eu.egi.sec.WMS will return a CRITICAL status for the servers still in production, and the ROD teams will open a ticket to the sites that haven't finished the decommission process yet

WMS servers in downtime on GOC-DB

8 WMS still registered on GOC-DB as production and monitored (1 month ago they were 16)

Status on nagios

IPv6 readiness plans

webdav probes in OPERATORS profile

The webdav probes was included in the ARGO_MON_OPERATORS profile after the approval in the January OMB: in this way the failures will generate an alarm on the dashboard, and the ROD teams can open a ticket to the failing sites. If no particular issue occurs, and if at least 75% of webdav endpoint are passing the tests, the probes will be added in the ARGO_MON_CRITICAL profile, so the results of these probes will be taken into account for the A/R figures.

List of sites that not have completed the configuration yet:

List of sites that disabled webdav: UNIGE-DPNC, GR-01-AUTH, HG-03-AUTH, CETA-GRID, WUT

Storage accounting deployment

During the September meeting, OMB has approved the full-scale deployment of storage accounting. The APEL team has tested it with a group of early adopters sites, and the results prove that storage accounting is now production-ready.

Storage accounting is currently supported only for the DPM and dCache storage elements therefore only the resource centres deploying these kind of storage elements are requested to publish storage accounting data.

In order to properly install and configure the storage accounting scripts, please follow the instructions reported in the wiki: https://wiki.egi.eu/wiki/APEL/Storage

IMPORTANT: be sure to have installed the star-accounting.py script v1.0.4 (http://svnweb.cern.ch/world/wsvn/lcgdm/lcg-dm/trunk/scripts/StAR-accounting/star-accounting.py)

After setting up a daily cron job and running the accounting software, look for your data in the Accounting Portal: http://goc-accounting.grid-support.ac.uk/storagetest/storagesitesystems.html. If it does not appear within 24 hours, or there are other errors, please open a GGUS ticket to APEL who will help debug the process.

Test portal: http://accounting-devel.egi.eu/storage.php

IMPORTANT: Do not encrypt the storage records with your host certificate, please comment out the “server_cert” variable in sender.cfg

List of sites already publishing and of tickets opened is reported here. Several sites are not publishing the storage accounting data yet. NGIs please follow-up with the sites the configuration of the script in order to speed-up the process.

Sites with wrong configuration (2018-05-22):

AOB

Next meeting

  • July 9th, 2018