EGI Cloud Middleware Distribution process

CMD menu:

Overview

Products

Process

Release schedule

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	-
2	Injection	UMD 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	QC Verifier	the QC verifier starts the verification process	one month; 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

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

1. The RT ticket is in "Verification" status
   • This means that the UMD team is verifying the product in the testbed.
   • An RT ticket cannot stay longer than one week in verification
   • After one week, if it has not been verified it is moved to "Delayed" status, with an explanation of the reasons of the delay. PT to be informed as well.
2. Product is in "Staged Rollout" Status
   • The product is announced to the early adopters testing in staged rollout the product.
   • #* RT cannot stay longer than one month in the "Staged Rollout" status
   • After one month, if it has not been tested in staged rollout it is moved to "Delayed" status, with an explanation of the reasons of the delay. PT to be informed as well.
3. After the staged rollout product is ready to be included in the next UMD release