EGI-InSPIRE RI EGI-InSPIRE EGI-InSPIRE RI EGI Release Process Michel Drescher, EGI Kostas Koumantaros, GRNET 7/5/2016 TCB F2F, 20 Jan 20111

EGI-InSPIRE RI Agenda Software Release Process –Release phases –Contacts and documentation EGI Software Repository –Current implementation –Future plans 7/5/2016 2

EGI-InSPIRE RI Agenda Software Release Process –Release phases –Contacts and documentation EGI Software Repository –Current implementation –Future plans 7/5/2016 3

EGI-InSPIRE RI Process Overview 1.Delivery 2.Verification 3.StageRollout 4.GA to Production

EGI-InSPIRE RI Delivery Dedicated GGUS instance for EGI Technology TP Release Managers submits ticket –With additional technical information GGUS ticket is linked to new EGI RT ticket RT sanity checks delivered information –Instructs Repository to prepare release

EGI-InSPIRE RI Verification Verification effort and focus based on: –Ops and User Requirements –TP test plans and results –Issue history, new features, etc. Verification coverage is determined Verification is conducted Results and decision are documented

EGI-InSPIRE RI StageRollout EA exposes software to production Partly functional, partly non-functional tests conducted –Test coverage based on many information resources Results and decision are documented No release enters production without dedicated StageRollout testing.

EGI-InSPIRE RI GA to Production SW placed in Production repository RT ticket resolved GGUS ticket updated with RT ticket info –GGUS notifies the TP Announcement via CIC Ops Portal –NGI Operations managers –Production Site admins

EGI-InSPIRE RI Resources and contacts Quality Criteria Definition –Lead: Enol Fernandez, CSIC, –Quality Criteria Roadmap: –Current Quality Criteria: Quality Criteria Verification –Lead: Carlos Fernandez, CESGA, –Report templates: StageRollout –Lead: Mario David, LIP, –Report template:

EGI-InSPIRE RI Agenda Software Release Process –Release phases –Contacts and documentation EGI Software Repository –Current implementation –Future plans 7/5/

EGI-InSPIRE RI Current implementation Technology Provider orientated –Software will be identifiable by TP Release orientated –Multiple major releases are supported –Implements the Release Workflow Releases are accepted/rejected as such –All or nothing, no further discrimination

EGI-InSPIRE RI Current implementation (2) Structure mirrors what TPs provide –We need to define what we want it to be and enforce it through SLAs Installing software –YUM/APT Issue command to install specific component –“yum install Nagios”

EGI-InSPIRE RI Current implementation (3) RepoFile Creation –Based on info provided by TP Example: –[egi-sam] name=EGI SAM repo baseurl= m/1/$basearch enabled=1 priority=10 gpgcheck=0 Then Yum install nagios … This info will soon be published at the repo portal including a link to the corresponding documentation.

EGI-InSPIRE RI Current Implementation(4) Frontend is WordPress CMS based. Thus we can –publish through it necessary info. –Sync with RSS from egi.eu –Get rss from CIC portal Etc.

EGI-InSPIRE RI Screenshot 1

EGI-InSPIRE RI Screenshot 2

EGI-InSPIRE RI Screenshot 3

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)

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