Difference between revisions of "EGI-InSPIRE:NSRW New Software Release Workflow"
Jump to navigation
Jump to search
Line 12: | Line 12: | ||
### '''In case of a failure:''' The Repo updates the RT, setting the RepoStatus of the ticket to “Failed”, plus it updates the ticket with a comment that contains the info related to the failure | ### '''In case of a failure:''' The Repo updates the RT, setting the RepoStatus of the ticket to “Failed”, plus it updates the ticket with a comment that contains the info related to the failure | ||
# In both 4.3 cases, the RT Notifies the EGI Technology Unit group (i.e the Ticket is Assigned to the EGI TUG) | # In both 4.3 cases, the RT Notifies the EGI Technology Unit group (i.e the Ticket is Assigned to the EGI TUG) | ||
## '''EGI TUG -- | ## '''EGI TUG -- The ticket is assigned a verifier''' | ||
## '''EGI TUG -- | ## '''EGI TUG -- The verifier checks the information available and fills the GQC template and the SQC template for the component .''' | ||
## '''EGI TUG -- If the verification is OK, the ticket is moved to stage-rollout and the SP get a notification''' | |||
## '''EGI TUG -- If the verification is not OK, and minor issues are found, the SP is notified and has 1-2 days (depending on the type of release) to solve or clarify the issues''' | |||
## '''EGI TUG -- If the verification is not OK, and has major issues or the grace-period has passed without correcting the issues, the ticket is moved to rejected and the SP get a notification''' | |||
# If the TUG team decide that the release it is ready to move to stage-rollout phase, the RepoAction field of the ticket it is marked as MoveToStageRollOut | # If the TUG team decide that the release it is ready to move to stage-rollout phase, the RepoAction field of the ticket it is marked as MoveToStageRollOut | ||
# Upon RepoAction field change, the RT Notifies the Repo that there is a ticket to be processed | # Upon RepoAction field change, the RT Notifies the Repo that there is a ticket to be processed |
Revision as of 15:00, 23 September 2010
Ticket LifeCycle
- The SW Provider creates a Ticket in GGUS accompanied with all the necessary info
- The ticket is transferred from GGUS to RT, the RepoAction field of the ticket is “MoveToUnverified“
- Upon RepoAction field change, the RT Notifies the Repo that there is a ticket to be processed
- The Repo Processes the ticket
- Downloads the software bundle and puts it on the “Unverified” Repository
- The Repo parses the attached xml
- Based on the metadata contained at both, the ticket itself and the attached xml, the Repo performs the necessary actions
- Upon success: The Repo updates the RT setting the RepoStatus of the ticket to “Unverified” + the Uri where the new software can be found, etc.
- In case of a failure: The Repo updates the RT, setting the RepoStatus of the ticket to “Failed”, plus it updates the ticket with a comment that contains the info related to the failure
- In both 4.3 cases, the RT Notifies the EGI Technology Unit group (i.e the Ticket is Assigned to the EGI TUG)
- EGI TUG -- The ticket is assigned a verifier
- EGI TUG -- The verifier checks the information available and fills the GQC template and the SQC template for the component .
- EGI TUG -- If the verification is OK, the ticket is moved to stage-rollout and the SP get a notification
- EGI TUG -- If the verification is not OK, and minor issues are found, the SP is notified and has 1-2 days (depending on the type of release) to solve or clarify the issues
- EGI TUG -- If the verification is not OK, and has major issues or the grace-period has passed without correcting the issues, the ticket is moved to rejected and the SP get a notification
- If the TUG team decide that the release it is ready to move to stage-rollout phase, the RepoAction field of the ticket it is marked as MoveToStageRollOut
- Upon RepoAction field change, the RT Notifies the Repo that there is a ticket to be processed
- The Repo Processes the ticket
- Move the SW to stage-rollout
- The Repo updates the RT setting the RepoStatus of the ticket to “Stage-Rollout” + the Uri where the new software can be found, etc.
- RT Notifies the EA and/or MarioD or whoever is responsible to handle the stage-rollout process (MarioD?? any suggestion on this?)
- If everything it is OK, MarioD change the RepoAction field to “MoveToProduction”
- Upon RepoAction field change, the RT Notifies the Repo that there is a ticket to be processed
- The Repo Processes the ticket
- Move the SW to production
- The Repo updates the RT setting the RepoStatus of the ticket to “Production” + the Uri where the new software can be found, etc.
…. and the life goes on ….
...
Required Fields
RepoAction : Actions to Be Performed by the Repo, Values MoveToUnverified,MoveToStageRollOut,MoveToProduction,Reject,Depreceate
RepoStatus : Response to RepoActions, Values Uverified,StateRollOut,Production,Depreceated,Failed
Work Flow
MetaData
NRMS New Release MetaDATA schema
Ticket Status Values
Questions/Issues
Insert any question / issue you may have here to keep track of them
MDavid: the (in)famous below graph needs to be updated