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.

Agenda-14-07-2014

From EGIWiki
Jump to navigation Jump to search
Audio conference link Conference system is Adobe Connect, no password required.
Audio conference details Indico page



1. Middleware releases and staged rollout

1.1 News from URT

Recent, or future planned, releases from the product teams:

1.2 UMD release

UMD 3.7.0 released on 12.06.2014 : http://repository.egi.eu/2014/06/12/release-umd-3-7-0/

1.3 Staged rollout updates

  • In verfication:
    • gfal2 v. 2.5.5
  • active:
    • globus-info-provider-service v. 0.2.1
    • cream v. 1.16.3


  • Ready to be released:
    • storm v. 1.11.4
    • lb v. 11.1
    • wms v. 3.6.5
    • dcache v. 2.6.28

UMD 3 EA

  • Some sites have the contact points for the EA adopters outdated so please check in table if all contacts and products are still correct and send me email if you need to add / remove some contacts (SSO account mandatory): (full site list)

New Products

FTS3, squid and CVMFS will soon be include in UMD and it is important to have some early adopters for this components. So if you anyone interested please contact me or cristina to be included in the early adopter list.

1.4 Next releases

  • Middle/End of July
  • October

2. Operational issues

2.1 Report from DMSU

ARGUS/WMS Certificate Chain Mixups

  • Affecting several sites, where WMS is unable to make SSL connection to ARGUS.
  • With all probability this is a combination of using curl from the SL6 distribution, which in built with NSS SSL rather than OpenSSL and, as such, does not really support proxy certificates, and a bug in Java, hopefully fixed since Java 7 Update 60.
  • Related issues:
  • This issue is already being investigated at 3rd level but PTs cannot decide who is responsible ant DMSU is overseeing.

CREAM CLI/GridSite SegFaults at Long-Lived Proxies

L&B & CREAM Update Issues - on EMI repositories

  • UPDATE
    • EMI 3 Update 18 solves some of the issues introduced with the previous update:

2.2 Migration of Central SAM services & reconfiguration of NGIs SAM instances

Action closed:

  • Central SAM services were migrated from CERN to the new consortium (GRNET, CNRS and SRCE). In order to enable smooth transition we have agreed to start using new hostnames:
    • mon.egi.eu for grid-monitoring.cern.ch
    • opsmon.egi.eu for ops-monitor.cern.ch
  • All Regional & VO SAM instances were reconfigured.

2.3 EMI-2 decommissioning

  • Probes are running in midmon: Documentation.
    • All products but dCache are being retired as previously announced. dCache extended the support for the 2.2.x versions until July 2014.
    • Important Notes:
      • APEL is one of the UMD 2/EMI 2 services no more supported - but there are still sites (23 sites as of 15.06.2014) publishing accounting information using UMD 2/EMI 2 APEL clients - see list available at: APEL consumer
      • Tutorial on how to migrate APEL clients from EMI 2 to EMI 3 - available at APEL @ EGI CF 2014
   Emi2 accounting.jpg


  • Following up with COD - GGUS #106354
  • NGIs with UMD2/EMI2 services - TOBE UPDATED for 14.07.2014:
    • AsiaPacific
      • TW-eScience, Taiwan-LCG2, IN-DAE-VECC-02, TW-EMI-PPS, IN-DAE-VECC-02, TOKYO-LCG2, TW-NCUHEP (in downtime)
    • NGI_DE
      • TUDresden-ZIH (in downtime), GoeGrid
    • NGI_FRANCE
      • GRIF (2 hosts in downtime), IN2P3-IRES
    • NGI_IBERGRID
      • UB-LCG2 (in downtime)
    • NGI_PL
      • ICM (in downtime)
  • ALL SITES PROVIDING UMD 2/EMI 2 services MUST BE IN DOWNTIME

2.4 SAM Nagios probes re-factoring

  • TF started the work regarding re-factoring of SAM Nagios probes, after discussion during OMB/26.06.2014

3. AOB

3.1 EGI UMD usage survey

  • BROADCAST send on 28.05.2014:
    • Survey - please take the survery - IT IS STILL OPEN

Partial results

  • 78 answers submitted (1/4 ~ 1/5 of production sites)
  • ~60% of the sites are using UMD repositories to install at least a subset of their services
    • Of which, 92% (41) think that UMD is a useful service.
  • Most important features of UMD
    • Unique repository containing most of the packages to install at site level
    • Protection from untested updates in the community repositories
    • Additional testing on top of developers certification
  • Where to improve
    • Increase the frequency of the UMD releases, reduce the time to release new updates in the repositories
    • Test more the products, with more real users

Participate to the survey

  • It can take from less than one minute to few minutes (let say 10-15 minutes)
  • We will use the feedback collected by the survey to evolve the UMD services

3.2 Next meeting

July 28, 2014 - if enough participants available

4. Minutes