Operations Portal Lightweight Release Process Cristina Aiftimiei - - PowerPoint PPT Presentation

www.egi.eu EGI-InSPIRE RI-261323 www.egi.eu EGI-InSPIRE RI-261323

Operations Portal Lightweight Release Process

Cristina Aiftimiei EGI.eu

www.egi.eu EGI-InSPIRE RI-261323

Overview

• Lightweight Release Management – why
• Operations Portal Release Procedure

– As it was – As it will be

www.egi.eu EGI-InSPIRE RI-261323

Lightweight Release Management – why?

• Release Management:

– Wikipedia: “release management is the process of managing software releases from development stage to software release – 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”

www.egi.eu EGI-InSPIRE RI-261323

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 processes

• “Lightweight Release Management”

Ø We are trying to improve the management of .. the challenges

Ø First volunteer – Operations Portal

www.egi.eu EGI-InSPIRE RI-261323

Operations Portal Release Procedure

• Present process:

– Code – on SVN

• Ops Portal : https://svn.in2p3.fr/operations-portal/
• Access by svn + ssh for the access in write mode

– Issues (bugs, features) addressed:

• Team tracker - https://forge.in2p3.fr/projects/opsportaluser/issues
• GGUS tickets
• Various e-mails

– Infrastructure:

• 1 web development instance - https://operations-portal.in2p3.fr/test/frontend_test.php/
• 1 web pre-production instance - http://operations-portal.in2p3.fr/next/frontend_test.php/
• 1 test database
• Several Instances of Lavoisier

– Production - http://cclavoisier01.in2p3.fr:8080/lavoisier – 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.

www.egi.eu EGI-InSPIRE RI-261323

Operations Portal Release Procedure

• Release Procedure proposed changes – by the team

– One release per month (next : 3.0.5 - September 20th) – Tested on test DB + preprod instance – Tested on GGUS test instance – 1 week for the test – List of features impacted

• https://forge.in2p3.fr/rb/release/1
• Expectations:

– Tests done by different users (ngi , site , vo users) – Bugs registered in the IN2P3 forge

www.egi.eu EGI-InSPIRE RI-261323

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 e-mail requests will also be copied/recorded

www.egi.eu EGI-InSPIRE RI-261323

Conclusions

• Request for Participation to the TAG is
• pen!!!

– We will contact experts BUT please feel free to join if interested – First meeting – F2F at EGI’s Sept Conference