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 "EGI DMSU"

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

Revision as of 13:44, 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 DMSU submenu


In years 1--2 of EGI-InSPIRE DMSU was a standalone task TSA2.5 dedicated to 2nd line support of middleware components (DMSU == Deployed Middleware Support Unit). Since year 3 (September 2012 technically) it is merged with TPM (within TSA1.7) to povide aggregated 1st and 2nd line support to all deployed software.

Within GGUS, the legacy DMSU unit is still used to keep the in-progress software related tickets.

The purpose of the software support team work is twofold: to find solution to problems which do not require changes in code, documentation, ... (whatever is released by the TP), and to provide thorough analysis, yielding well-specified bug report otherwise.

The team also carries sufficient expertise to provide emergency fixes to the software problems in the unlikely case the TP fails to deliver, for whatever reason.