Alert.png The wiki is deprecated and due to be decommissioned by the end of September 2022.
The content is being migrated to other supports, new updates will be ignored and lost.
If needed you can get in touch with EGI SDIS team using operations @ egi.eu.

Difference between revisions of "Agenda-13-03-2017"

From EGIWiki
Jump to navigation Jump to search
Line 42: Line 42:
ARC 15.03.12
ARC 15.03.12
canL 2.2.8
canL 2.2.8
* including XrootD 4.6.0, fix for DPM 1.9.0





Revision as of 10:11, 9 March 2017


General information

Middleware

CMD

UMD

UMD 4.4.0 almost ready

  • CentOS7

Davix 0.6.4 GFAL 2.12.2 GFAL Utils 1.4.0 CGSI gSOAP 1.3.10 gfalFS 1.5.1 srm-ifce 1.24.1 FTS3 3.5.7 GRAM5 13.16.0 yaim core 5.1.4 GridFTP 11.8.1 MyProxy 6.1.25 globus-default-security 6.4.0 dCache SRM client 3.09.1 ARC 15.03.12 canL 2.2.8

  • SL6

VOMS Admin server 3.5.1 GFAL 2.12.2 GFAL Utils 1.4.0 CGSI gSOAP 1.3.10 gfalFS 1.5.1 FTS3 3.5.7 GRAM5 13.16.0 yaim core 5.1.4 Davix 0.6.4 GridFTP 11.8.1 MyProxy 6.1.25 globus-default-security 6.4.0 CGSI gSOAP 1.3.10 ARC 15.03.12 canL 2.2.8

  • including XrootD 4.6.0, fix for DPM 1.9.0


Preview repository

Operations

Decommissioning EMI WMS

  • action needed from NGIs

Feedback from Helpdesk

IPv6 readiness plans

  • December OMB presentation: https://indico.egi.eu/indico/event/2815/ WLCG is going to deploy their services under dual-stack mode (v4+v6) by April 2018
  • EGI Operations started checking the core services against IPv6 compatibility
  • EGI Operations is going to assess the IPv6 readiness of the EGI infrastructure
  • early draft plan
    • Technology Providers: assess the IPv6 readiness of the middleware products
    • UMD team: perform verification of all services under IPv6 setup
    • EGI core services developers: assess the IPv6 readiness of the products
    • EGI core services hosts: assess the IPv6 readiness of the services
    • Resource Centres: assess the IPv6 readiness of the site infrastructure (real machines, cloud managers)
      • NGIs/ROCs please start discussing with sites and provide suggestions for the overall plan

Decommissioning of dCache 2.10

  • support for the dCache 2.10 ended at December 2016
  • according to EGI policies, dCache 2.10 must be decommissioned https://wiki.egi.eu/wiki/PROC16_Decommissioning_of_unsupported_software
  • broadcast sent on Feb2 https://operations-portal.egi.eu/broadcast/archive/1631 + email sent on Feb7 to noc-managers mailing list
  • sites to upgrade their 2.10 endpoints to a newer "golden release" of dCache
    • 2.13, whose support ends on July 2017, which means in about 7 months from now, or
    • 2.16, whose support ends on May 2018: here take care that the dCache team does not support the upgrade from 2.10 directly to 2.16; only 2.10->2.13 and 2.13->2.16 transitions are supported.
  • decommissioning campaign will be started by EGI Operations to monitor the upgrade of the dCache 2.10 instances and follow up with the NGIs/sites; tickets will be opened this week
  • deadline is end of April, having all the sites more than 2 months to plan and perform the upgrade
  • probe will be WARNING for two months until April 17th, when it will switch to CRITICAL
  • in May EGI Operations will open tickets against sites still publishing dCache 2.10 and follow up on the upgrade plans
  • reference: https://www.dcache.org/downloads/1.9/index.shtml

Testing the new webdav probes

Site Host GGUSID note
CYFRONET-LCG2 se01.grid.cyfronet.pl https://ggus.eu/index.php?mode=ticket_info&ticket_id=126776 Registered
GR-01-AUTH https://ggus.eu/index.php?mode=ticket_info&ticket_id=126777
GRIF https://ggus.eu/index.php?mode=ticket_info&ticket_id=126778
IGI-BOLOGNA darkstorm.cnaf.infn.it https://ggus.eu/index.php?mode=ticket_info&ticket_id=126779 Registered
INFN-T1 https://ggus.eu/index.php?mode=ticket_info&ticket_id=126780
NCG-INGRID-PT https://ggus.eu/index.php?mode=ticket_info&ticket_id=126781
UKI-NORTHGRID-LIV-HEP hepgrid11.ph.liv.ac.uk https://ggus.eu/index.php?mode=ticket_info&ticket_id=126782 Registered
egee.irb.hr lorienmaster.irb.hr https://ggus.eu/index.php?mode=ticket_info&ticket_id=126783 Registered

Testing of the storage accounting

As discussed during the January OMB, the APEL team would need one site per NGI for testing the storage accounting. The eligible sites are the ones providing either dCache or DPM storage elements.

More information can be found in the following wiki: https://wiki.egi.eu/wiki/APEL/Storage

List of sites available for test.

Proposal to modify the declaration of scheduled interventions

Monthly Availability/Reliability

ARGO proposal to use GOCDB as the only source of topology information

  • Timescale:
    • New GOC-DB release on Dec 7th including a boolean ‘monitored’ flag for the service endpoints
    • Then creation of a web UI view for uncertified sites in ARGO
    • Uncertified sites will be asked to fill in the service endpoints information. Follow the How to add URL service endpoint information into GOC-DB
    • As information is added in the GOCDB, uncertified sites/services will be picked up by the ARGO Monitoring Engine and they will start to be monitored
    • By Q2 2017: support for multiple service endpoints

VAPOR

AOB

Next meeting