1 / 13

EGI Quarterly Report - May, June, July 2012

This quarterly report provides updates on the progress and developments in the EGI community from May to July 2012. It includes information on the release of UMD 2.0, updates on high priority products, EMIR deployment, VOMS migration towards SHA-2, resource allocation policies, and the sustainability of NGI operations.

afulton
Télécharger la présentation

EGI Quarterly Report - May, June, July 2012

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. Introduction T. Ferrari/EGI.eu OMB, 17 July 2012

  2. Quarterly Report QR9 • End of EGI-InSPIRE QR9 approaching • May, June, July 2012 • All NGI and SA1 task leaders are requested to provide a report and metrics • NGI reports: https://wiki.egi.eu/wiki/NGI_QR_Reports • NGI metrics: http://metrics.egi.eu/

  3. UMD 2 • UMD 2.0 released on 10/07 (http://repository.egi.eu/2012/07/10/release-umd-2-0-0/) • Subset of high priority products (globus-gssapi-gsi new version causing problems to UI, WN, LB and CREAM) • UNICORE TSI, UNICORE Registry 6, UNICORE Gateway 6 • DPM 1.8.3 and StoRM 1.9.0 • LFC 1.8.3 • BDII site 1.1.0 and top 1.0.1 • APEL 3.3.0 • VOMS 2.0.8 • UMD 2.1 expected in early August • Including ARC, UNICORE other products, CREAM, LB, UI and WN

  4. EMIR • EMI 2 service endpoint registry for discovery of Service Endpoints (static information and service metadata) • collection of services that enables storing service records in a federated manner • GLUE 2.0 standard • Deployment: EMIR network over WAN • NGI rooted hierarchy with a single EMIR server aggregating all the information within a federation • Sharing of information at root level among peered EMIR servers • EMI proposing a joint testbed • Use cases to be defined • EMIR will play a role in the long-term evolution of BDII (site and top-BDII functionality will be reduced, after-EMI activity)  architectural document requested

  5. EMI WN testing 1/2 • gLite 3.2 end of security support: 01 October 2012 • EMI 1 WN introduces changes in library paths  changes in the execution environment of the user payload • Various problems encountered by VOs when migrating to EMI 1 WN • Impact of the transition to EMI 1 WN needs to be assessed for a larger number of VOs • NGI coordination of testing needed for • regional VOs • other VOs whose VOMS is affiliated to the NGI

  6. EMI WN testing 2/2 • Proposal • By Sep 07: NGIs to provide information about which VOs are successfully running on EMI 1 WN at a national level • Input collected through wiki • By July 20: broadcast to all VOs to • Provide information about experience with EMI 1 (through GGUS) • Otherwise recommend testing  contact the NGI hosting the VO VOMS

  7. Migration towards SHA2 • IGTF concerns about long-term safety of current SHA-1 encryption algorithm  move to SHA-2 signatures • ALL IGTF CAs should have or get the capability of issuing SHA-2 based certificates by Jan 2013 • EUgridPMA: all CAs MUST implement this a.s.a.p, and report on the implementation of SHA-2 issuing capabilities by October 1, 2012 • EUgridPMArisk assessment of hash function vulnerabilities

  8. RFC 3280 proxy certificates • dCacheand BeStMan(OSG) use JGlobus 1.x, which does not support SHA-2 • JGlobus2.x  support of SHA-2 and only RFC proxies (no Globus legacy proxies being used today • EMI CANL?

  9. SHA-2: EGI plan • EGI document in collaboration with EUgridPMAby end of July explaining problems, EUgridPMA risk assessment activities and actions: • (EMI/IGE/JRA1) Table with SHA-2/RFC proxy compliance information per product • SHA-2/RFC proxy verification added to UMD quality creteria (SA2) • (EGI CSIRT) extension of security nagios with probes for assessment of deployed software • VO software testing solicited

  10. Survey on resource allocation • Different policies at NGI and site level • Many international VOs relying on opportunistic usage of resources • Problem • Better coordinated support of new international VOs • Proposal • Collect information across NGIs about national and site-level existing policies (survey, 07/09) • https://wiki.egi.eu/wiki/Operations/Resource_Allocation

  11. NGI operations sustainability 1/2 • Future strategy: EGI in 2020 (PY2 EGI-InSPIREreview)* • “Community funding operates EGI • EC Project funding for innovation & support” • What impact on NGI operational services? • What EGI ”global tasks” are necessary and need to be supported after EGI-InSPIRE? • [*] https://indico.egi.eu/indico/getFile.py/access?contribId=1&resId=0&materialId=slides&confId=1046

  12. NGI operations sustainability 2/2 • Survey • Assessment of impact of end of EC funding for NGI operations and of other national funding models being implemented • Requirements to attract national funding • Assessment of the EGI Global Tasks • Your role with EGI in HORIZON2020 • What types of innovation do you consider important for EGI for which you would like to participate? • Deadline: 07 Sep • Discussion at TF12  D4.7 Sustainability assessment of operational services (Nov 2012)

  13. SA2 Activity Management • SA2 activity manager - Michel Drescher on sick leave • P. Solgna temporarily deputizing Michel until end of August

More Related