EGI-InSPIRE RI EGI-InSPIRE EGI-InSPIRE RI EGI Software Repository Progress Report Kostas Koumantaros et al, GRNET 7/3/2016 WP5 F2F, Brussels 1

EGI-InSPIRE RI Current Status Workflow Implementedand Tested Notification System Created WebService for RT GGUS Integration done (waiting for GGUS)

EGI-InSPIRE RI Notification System … W RollOut ProgressGroup to Be notified Submitted UnverifiedSW-REL-QC InVerification Waiting For Response Stage RolloutSW-REL-SR ProductionSW-REL-PRODUCTION Rejected SW-REL-ADMIN is always in Admin CC We need to fill in the blanks as needed.

EGI-InSPIRE RI Repo Creation … YUM or APT related repositories (and the relative repofiles) should be (re- )created. 3 possible options toward this direction. 1.The EGI repo could (re-)create every YUM/APT repository/repofile as this described/commanded by the TP (using the release.xml) 2.In addition to the case 1, the EGI repo could ALSO (re-)create the YUM/APT repositories, which are part of the submitted release but they are NOT declared within the release.xml 3.If SA2 decides to force the TPs (i.e. through the SLA) that each submitted release should follow a specific structure (f.e. base/ updates/ security/), the EGI repo should build the YUM or APT repository on specific directories. 7/3/2016 EGI TF 2010, Amsterdam 4

EGI-InSPIRE RI Future plans (short term) Adapt the Front End to carry more information for the releases to be available. Adapt the frontend to the latest EGI look and Feel. Provide RSS of new release info. Get to do trial releases in Collaboration with EMI. (aka get feedback) Establish a load balancing mechanism for scalability.

EGI-InSPIRE RI

EGI-InSPIRE RI Future plans ??? Decoupling EGI Repository from TPs (UMD) Capability orientated –Which components implement which capability? Component orientated –Components have release cycles, not TPs –Components may be accepted individually

EGI-InSPIRE RI Future plans (2) Contents of EGI Repository mirrors closely what is accepted by EGI –And not what is published by TPs Site Administrators need only two sources –Platform (e.g. SL5, Ubuntu LTS) –EGI Repository

EGI-InSPIRE RI Future plans (3) Clear association between –Capability, and –Available components Query YUM for available implementations –“yum install ComputeJob” –“Three implementations are available: GRAM, CREAM, gLiteCE. Choose which to install.” –“yum install GRAM”

EGI-InSPIRE RI Future plans (4) UMD will be a slice through the repository –Only proven components are part of UMD –“Best of breed”, i.e. a subset of EGI Repository May serve as canonical baseline for uniform site configuration

EGI-InSPIRE RI Thank you Questions to Michel ?