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-02-12-2013

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

New releases:

  • ARC 4.0
    • ARC CE probes update
    • ARC Doc update
    • CanL
  • EMI-3 Update 11
    • BDII core, v. 1.5.5 - affected services: ALL services publishing information through BDII
    • BDII top, v. 1.1.4 - affected services: BDII top
    • BLAH, v. 1.20.4 - affected services: CREAM
    • dCache server v. 2.6.16 & dCache SRM client 2.6.12 - affected services: dCache server, UI, WN
    • WMS, v. 3.6.2 - affected services: WMS
  • EMI-2 Update 20
    • BDII core, v. 1.5.5 - affected services: ALL services publishing information through BDII
    • BDII top, v. 1.1.4 - affected services: BDII top
    • dCache, v. 2.2.20 - affected service: dCache server
    • UMD-2 is considered in security support. BDII products are released in UMD-3 (usually they do the same release for EMI-2 and EMI-3), and dCache 2.2.* did not make into UMD-2 for lack of EAs. Please contact me if you consider critical to have those products in UMD-2.
  • Globus 5.2.5
    • Being tested by the PT for compatibility
    • Released in EPEL stable

1.2 Next Release

https://wiki.egi.eu/wiki/UMD-3:UMD-3.3.0

1.3 Staged rollout updates

  • UMD-3:
    • cream-torque v. 2.1.2
  • UMD-2:
    • emi-wn v. 2.0.2
    • cream v. 1.14.6

2 Operational issues

2.1 Updates from DMSU

Nothing to report.

2.2 SHA-2 update

Currently there are 17 sites deploying non SHA-2 compliant middleware:

One site (CA-ALBERTA-WESTGRID-T2)requested an extension of the deadline to allow data migration. The other sites were not reporting longer timelines (for SEs).

ROD teams should check with the remaining sites (very few of the total, fortunately) and ask for an updated timeline. The proposed timeline would be:

  • Sites must report a new timeline by the end of the week.
    • Open a downtime for the affected services in case of a unresponsive site
  • Sites should upgrade their non compliant services by SHA-2 by Dec 19th
    • And they must document the target date in the GGUS ticket
  • All the non compliant services must be in downtime starting from Dec 20th

3. AOB

3.2 Next meeting

4. Minutes