RI EGI-InSPIRE RI Operations Portal Lightweight Release Process Cristina Aiftimiei EGI.eu

RI Overview Lightweight Release Management – why Operations Portal Release Procedure –As it was –As it will be

RI Lightweight Release Management – why? Release Management: – Wikipedia: “release management is the process of managing software releases from development stage to software releaseWikipedia –Ageless battle: Devel. does not understand Ops and Ops wishes Devel. would quit breaking production.  RM - it bridges the gap and reduces the paranoia of Ops, by using logical policies and reducing the uncertainty of a release and changes.  The key = transparency -> “what, when, why, and how”

RI Lightweight Release Management – why? Release Management: – 4 basic “things”: Takes some existing code from somewhere Builds the code into a test environment Facilitates testing the code Puts the code into production –Challenges – management of softw. defects, issues, risks, softw. change requests, softw. devel. requests (new features, functions) deployment/testing All EGI’s Central Operations Tools, under JRA2, have well established development and release processesCentral Operations Tools “Lightweight Release Management”  We are trying to improve the management of.. the challenges  First volunteer – Operations Portal

RI Operations Portal Release Procedure Present process: –Code – on SVN Ops Portal : Access by svn + ssh for the access in write mode –Issues (bugs, features) addressed: Team tracker - GGUS tickets Various s –Infrastructure: 1 web development instance web pre-production instance test database Several Instances of Lavoisier –Production - –test and preprod : cloud instances not reachable from outside. –One release is composed with one version of the web code and one version of Lavoisier configuration.

RI Operations Portal Release Procedure Release Procedure proposed changes – by the team –One release per month (next : September 20th) –Tested on test DB + preprod instance –Tested on GGUS test instance –1 week for the test –List of features impacted Expectations: –Tests done by different users (ngi, site, vo users) –Bugs registered in the IN2P3 forge

RI Operations Portal Release Procedure - Improvements Goals: –Well tested Ops Portal releases –Changes aligned with users needs and expectations Proposed Solution: – small testing/advisory team gathering representatives from: RODs & site admins EGI.eu - operations + user support Security VO managers –lightweight monthly meetings of TAG & devels to discus next release (eventual priorities) & timelines for (beta) testing –testing of the release by the team after Sept. release -> lightweight releases containing only bug fixing, small features -> testing should not take long, couple of weeks –All issues recorded in forge.in2p3.fr (by devels) GGUS tkts or requests will also be copied/recorded

RI Conclusions Request for Participation to the TAG is open!!! –We will contact experts BUT please feel free to join if interested –First meeting – F2F at EGI’s Sept Conference