1 / 7

Updates from EGI

Updates from EGI. Peter Solagna – EGI.eu. SHA-2 Monitoring. Probes for detection of SHA-2 non compliant services deployed on midmon, will generate alarms in the ROD dashboard Services (EMI-2) CREAM-CE ( eu.egi.sec.CREAMCE-SHA-2 ) – 184 instances VOMS ( eu.egi.sec.VOMS-SHA-2 ) – 38 instances

loman
Download Presentation

Updates from EGI

An Image/Link below is provided (as is) to download presentation Download Policy: Content on the Website is provided to you AS IS for your information and personal use and may not be sold / licensed / shared on other websites without getting consent from its author. Content is provided to you AS IS for your information and personal use only. Download presentation by click this link. While downloading, if for some reason you are not able to download a presentation, the publisher may have deleted the file from their server. During download, if you can't get a presentation, the file might be deleted by the publisher.

E N D

Presentation Transcript

  1. Updates from EGI Peter Solagna – EGI.eu

  2. SHA-2 Monitoring • Probes for detection of SHA-2 non compliant services deployed on midmon, will generate alarms in the ROD dashboard • Services (EMI-2) • CREAM-CE (eu.egi.sec.CREAMCE-SHA-2) – 184 instances • VOMS (eu.egi.sec.VOMS-SHA-2) – 38 instances • WMS (eu.egi.sec.WMS-SHA-2) – 42 instances • StoRM (eu.egi.sec.StoRM-SHA-2) – 47 instances • GGUS ticket reporting a load problem, StoRM will not generate alarms until there is a SHA-2 enabled StoRM available • Documentation • https://wiki.egi.eu/wiki/MW_SAM_tests#SHA-2_tests • Sites will be asked to upgrade their services, but without hard deadline for the moment • Situation to be reassessed in the August OMB (27th)

  3. Next UMD-3 updates • The target is to complete the UMD SHA-2 readiness • dCache 2.6.5 was release on 16.07 • UMD needs to have it in the EMI repositories (22-26.07) • Current release date for UMD-3 is middle of August • dCache 2.6.5 and VOMS admin 3.2.0

  4. Training sessions at EGI TF2013 • EGI TF 2013 in Madrid (16-20 September) • Draft timetable available, trainings to highlight among the others: • GLUE2 training: how to properly publish and debug Site information in BDII • Tuesday 17 (tentative date)

  5. Release Frontier-squid in UMD • Discussion started from a request of a site manager (frontier-squid in UMD) • Sites now must enable another repository (on top of EMI/UMD and EPEL) to install frontier-squid • Repository may conflict with site’s security policies • Maintainer is willing to contribute to UMD • In principle also with formal agreements between EGI and the product team

  6. Frontier-squid deployment status • How many sites are deploying frontier-squid? • Currently there are ~10 instances registered in GOCDB • Is it correct? If not, are there more accurate figures about squid deployment?

  7. Is it needed in UMD, is it worth? • The release in UMD requires verification and staged rollout • Need for “committed” early adopters • How many sites would consider beneficial to have frontier-squid in UMD? • With the additional quality assurance of staged rollout?

More Related