EGI Cloud Middleware Distribution process

From EGIWiki
Jump to: navigation, search
Technology Software Component Delivery Software Provisioning Middleware Cloud Middleware Distribution Technology Glossary


CMD menu: Overview Products Process Release schedule

Contents


Description of the process

Step Action Action on Description Timeline
1 Submission Technology Provider submit a GGUS ticket, assigned to Support Unit "EGI Software provisioning support", providing them with the following information:
  • Product release and version number
  • Link to the release notes
  • Full list of packages that compose the release and that need to be released
at TP convenience
2 Injection UMD Team SR Manager inject the product release in the EGI SW provisioning infrastructure:
  • One or more RT tickets are created to track the progress of the inclusion of the new product release; the status of the product release will then be tracked in RT, the status of the RT ticket just is initially Unverified
  • The UMD Staged rollout manager answers to the GGUS ticket with the link to the RT and closes as 'solved' the GGUS ticket
5 working days
3 Quality Verification starts UMD Team QC Verifier the QC verifier starts the verification process, switching the status of the RT ticket from "Unverified" to "Verification" the QC verification must start in one month after the creation of the RT ticket; after a month with the verification not yet started:
  • the RT ticket will be updated with an explanation for the delay
  • the status will be changed to "Delayed" [*]
  • the Technology Provider will be informed (using the contacts in the product ID card)
4 Quality Verification execution UMD Team QC Verifier the UMD team is verifying the product in the testbed; after the verification process is completed, the RT ticket status is switched from "Verification" to "Staged Rollout" an RT ticket cannot stay longer than one week in verification; after one week with the verification not yet completed:
  • the RT ticket will be updated with an explanation for the delay
  • the status will be changed to "Delayed" [*]
  • the Technology Provider will be informed (using the contacts in the product ID card)
5 Staged Rollout UMD Team Staged Rollout manager The product is announced to the early adopters testing the product in staged rollout. RT tickets cannot stay longer than one month in the "Staged Rollout" status; after a month with the staged rollout not yet completed:
  • the RT ticket will be updated with an explanation for the delay
  • the status will be changed to "Delayed" [*]
  • the Technology Provider will be informed (using the contacts in the product ID card)
6 Inclusion in the next release Release manager include the product in the next release see the CMD release schedule

[*] Being in the "Delayed" status RT tickets can be identified as problematic by the UMD team and followed up more closely.

Verification

For further details on the Verification Process, please visit https://wiki.egi.eu/wiki/EGI_Quality_Assurance

Staged-Rollout

For further details about the Staged-Rollout process, please visit https://wiki.egi.eu/wiki/Staged_Rollout

Release process

TBD

Personal tools
Namespaces
Variants
Actions
Navigation
Toolbox
Print/export