Alert.png The wiki is deprecated and due to be decommissioned by the end of September 2022.
The content is being migrated to other supports, new updates will be ignored and lost.
If needed you can get in touch with EGI SDIS team using operations @ egi.eu.

Difference between revisions of "Software Provisioning Process"

From EGIWiki
Jump to navigation Jump to search
Line 1: Line 1:
{{Tech menubar}}
{{SWProv menubar}}
{{SWProv menubar}}
{{SWProv UMD Prov submenu}}
{{SWProv UMD Prov submenu}}

Revision as of 13:47, 24 October 2014

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



Template:SWProv UMD Prov submenu


The Software Provisioning process consists of

  1. 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).
  2. Software Assessment, is done in two phases
    1. Quality Assurance
    2. Stage Rollout
  3. Reporting, this is the last process that reports back to Technology providers the outcome of the software provisioning process.

SW-Assesment.png

SW-Reporting.png


File:UMD Software Provisioning Process summary.pdf