EGIIn SPIRE Update from EGI Operations Peter Solagna

  • Slides: 8
Download presentation
EGI-In. SPIRE Update from EGI Operations Peter Solagna – EGI. eu 10/17/2021 EGI-In. SPIRE

EGI-In. SPIRE Update from EGI Operations Peter Solagna – EGI. eu 10/17/2021 EGI-In. SPIRE RI-261323 1 www. egi. eu

Summary • Past requirements overview • New set of security requirements for EMI and

Summary • Past requirements overview • New set of security requirements for EMI and IGE • Upcoming survey for SLURM requirement • IPv 6 survey outcome EGI-In. SPIRE RI-261323 www. egi. eu

Waiting for an answer The following tickets are waiting for an answer from EMI:

Waiting for an answer The following tickets are waiting for an answer from EMI: • 1186: New features for UNICORE Target System • 1384: DOS attack • 881: Requirement for VO renaming / migration The following requirements have been officially endorsed by the technology provider, but no timeline has been provided • 1388: Better documentation on services migration • 1386: EMI Data clients should be able to offer the file: // protocol to SRM services 10/17/2021 EGI-In. SPIRE RI-261323 3 www. egi. eu

Tickets modified The following tickets have been modified changing their scope: • 1381: Improving

Tickets modified The following tickets have been modified changing their scope: • 1381: Improving automatic service configuration (Was: Improving yaim configuration) • 1236: generic Information system for EGI-In. SPIRE RI-261323 www. egi. eu

Security Tickets The following tickets have been presented in the security session @ EMI

Security Tickets The following tickets have been presented in the security session @ EMI AH Oct 2011, but they apply to Globus middleware as well • 3079: Default key size for any generated proxy • 3080: RPDNC constrains • 3078: Support for SHA 2 proxies • 3076: Support for OCSP • 3081: Support drop-in trust anchor distribution • 3075: Common Authentication Library to configure the accepted proxy lifetime • 3074: Unit test for CRL refresh EGI-In. SPIRE RI-261323 www. egi. eu

Survey for the support of SLURM In a survey run across the sites six

Survey for the support of SLURM In a survey run across the sites six month ago SLURM resulted not to be largely deployed • The survey asked for the LRMS currently deployed, or planned to be deployed in the near future Recently the interest in SLURM has increased • It was reported in our community to be a viable replacement of PBS/Torque especially in large stes, thanks to its scalability and good functional capabilities. • In the next days we will start a new survey in order to assess the need for support of SLURM in CREAM • The survey will be addressed to sites deploying the CREAM CE, because SLURM is supported by ARC and UNICORE • The survey will be open for few weeks • If the results will be relevant, they will be forwarded to EMI as a requirement. EGI-In. SPIRE RI-261323 www. egi. eu

IPv 6 - survey results Outcome of the survey • 27 NGIs answered (~70%)

IPv 6 - survey results Outcome of the survey • 27 NGIs answered (~70%) • One NGI is planning to set up an IPv 6 -Only site • 16 NGIs available to join a distributed IPv 6 testbed • Testbed for: UMD components, operational tools and other tools • Can support and complement similar Technology Providers’ activities EGI-In. SPIRE RI-261323 www. egi. eu

IPv 6 – proposed steps ahead • Tech Providers and EGI Network Support could

IPv 6 – proposed steps ahead • Tech Providers and EGI Network Support could begin to focus on core site services for the UMD • • • Site Resources Information System Computing Element ( ARC, g. Lite, UNICORE) IGE site components Storage Elements EGI Net. Sup coordinates with NGIs for assigning tasks on general purpose testing • • For ARC SWITCH/SWING gave some availability For g. Lite GARR Need to identify volunteering NGIs for UNICORE, IGE and d. Cache Many NGIs gave their principle availability • • • Requires further coordination Tech Providers start thinking/prototyping what should be done to include IPv 6 in their certification process EGI Network Support further investigate integration options: • • Protocol translation at the site level ? Gateway towards IPv 6 -resources in the IPv 4 infrastructure (and vice versa)? IPv 6 testbed planned for Dec/Jan 2011 -12 • The proposal needs to be re-assessed and updated by Feb 2012 EGI-In. SPIRE RI-261323 www. egi. eu