Software Provisioning Process
|Technology||Software Component Delivery||Software Provisioning||UMD Middleware||Cloud Middleware Distribution||Containers Distribution||Technology Glossary|
|Software Provisioning menu:||Software Provisioning Process||UMD Release Process||Quality Assurance||UMD||Staged Rollout|
EGI's UMD Provisioning activity governs and executes two main processes:
- Software Provisioning Process: That handles software delivery from software development teams, aka Technology Providers (TP), Quality Assurance and Reporting.
- UMD Release Process: That collects tested Products per Platform and Architecture (PPAs) into UMD Releases
The following picture depicts the processes as described:
Software Provisioning process
The Software Provisioning process consists of
- Software Delivery – Technology Providers submit new software releases
- Software Assessment – through Quality Assurance & Staged Rollout
- Reporting – inform TP about outcome of the software provisioning process
Software Delivery this is the process according to which Technology Providers submit through GGUS new software releases. Software delivery is performed using one of the three different user interfaces available, i.e. a web form, e-mailing and a web service interface, that create tickets including all the necessary information about the software delivered in order to be processed. GGUS forwards the tickets to RT creating one RT ticket per Product per Platform and Architecture (PPA).
- After the first successful release, TP should request the subscription to the UMD Release team
- Communication Channels of new updates:
- E-mail to URT team
- Update the information on the URT meeting agendas
- Information needed for each update:
- Product Name & Version
- Release Notes as:
- What’s New – bug fixes, new features
- Installation & Configuration instructions – what needs to be done to correctly update the product (package, service) on production infrastructure
- List of Packages to be updated
- Location where the packages are available:
- TP repositories
- APP DB
- TP repositories
Software Assessment is done in two phases
- Quality Assurance
- Stage Rollout
Reporting this is the last process that reports back to Technology providers the outcome of the software provisioning process.
The software provisioning process, step by step
- The product team submits a ggus ticket for the "EGI Software provisioning support" support unit 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 in UMD
- The product release is injected in the EGI SW provisioning infrastructure
- One or more RT tickets are created to track the progresses of the UMD software provisioning of the new product release
- The UMD Staged rollout manager answers to the GGUS ticket with the link to the RT and close as 'solved' the GGUS ticket
- The status of the product release will be tracked in RT
- This action must be closed in 5 working days by the UMD team
- The RT ticket is in "Unverified" status
- This is the "waiting line" for the verification process
- RT cannot stay longer than one month in the "Unverified" status
- After a month if the verification has not started the RT ticket will be updated with an explanation for the delay and the status will be changed to "Delayed"
- Product team (using the contact in the Product ID card) will be informed of the delay, with the reasons that caused the delay
- Being in the "Delayed" status RT tickets can be identified as problematic by the UMD team and followed up more closely.
- 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.
- 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.
- After the staged rollout product is ready to be included in the next UMD release
- The overall process should not take longer than *two months*, without the PT be informed of any delays