Difference between revisions of "PROC17 Decommissioning of service type"
(→Steps) |
|||
Line 8: | Line 8: | ||
|Policy_name = Operations Management Board | |Policy_name = Operations Management Board | ||
|Contact_group = operations at mailman.egi.eu | |Contact_group = operations at mailman.egi.eu | ||
|Doc_status = | |Doc_status = Final | ||
|Approval_date = | |Approval_date = 18.06.2013 | ||
|Procedure_statement = A procedure for removal of service type from production infrastructure. | |Procedure_statement = A procedure for removal of service type from production infrastructure. | ||
}} | }} | ||
Line 25: | Line 25: | ||
= Steps = | = Steps = | ||
The process starts when the COO opens a GGUS ticket to the Operations SU (via GGUS). Each step which require contact with other teams should be done through GGUS as well (as a child ticket the main one). | The process starts when the COO opens a GGUS ticket to the Operations SU (via GGUS). Each step which require contact with other teams should be done through GGUS as well (as a child ticket the main one). | ||
This procedure is run if a software related to the service type is unsupported or it was decide to change the name of the service type. | This procedure is run if a software related to the service type is unsupported or it was decide to change the name of the service type. | ||
Line 41: | Line 41: | ||
| 2 <br> | | 2 <br> | ||
| COO | | COO | ||
| The broadcast is send to NGI managers | | The broadcast is send to NGI managers, Site administrators, VO managers | ||
|- valign="top" | |- valign="top" | ||
| 4 | | 4 | ||
Line 52: | Line 48: | ||
|- valign="top" | |- valign="top" | ||
| 5 | | 5 | ||
| | | COD<br> | ||
| Followup the process till the decommission deadline | | Followup the process till the decommission deadline | ||
|} | |} | ||
Line 60: | Line 56: | ||
After '''Decommision deadline''' | After '''Decommision deadline''' | ||
<br> | |||
{| class="wikitable" | {| class="wikitable" | ||
Line 77: | Line 74: | ||
|- valign="top" | |- valign="top" | ||
| 2 <br> | | 2 <br> | ||
| GGUS | | GGUS | ||
| If for the service type specific SU in GGUS exists, the SU should be removed from GGUS. | | If for the service type specific SU in GGUS exists, the SU should be removed from GGUS. | ||
|- valign="top" | |- valign="top" | ||
| 3 | | 3 | ||
| GOCDB | | GOCDB | ||
| The service type should be disabled in GOCDB (i.e. service entries can no more declared to be of the service type), but not removed. | | The service type should be disabled in GOCDB (i.e. service entries can no more declared to be of the service type), but not removed. | ||
|- valign="top" | |- valign="top" | ||
| 4 | | 4 | ||
| COO | | COO | ||
| The broadcast is send to NGI managers | | The broadcast is send to NGI managers, Site administrators and VO managers that the service type was decommissioned.<br> | ||
|} | |} | ||
Line 98: | Line 95: | ||
! Comments | ! Comments | ||
|- | |- | ||
| <br> | | <br> | ||
| <br> | | <br> | ||
| <br> | | <br> | ||
| <br> | | <br> | ||
|} | |} | ||
[[Category:Operations_Procedures]] | [[Category:Operations_Procedures]] |
Revision as of 14:08, 18 June 2013
Main | EGI.eu operations services | Support | Documentation | Tools | Activities | Performance | Technology | Catch-all Services | Resource Allocation | Security |
Documentation menu: | Home • | Manuals • | Procedures • | Training • | Other • | Contact ► | For: | VO managers • | Administrators |
Title | Decommissioning of service type |
Document link | https://wiki.egi.eu/wiki/PROC17 |
Last modified | 1.0 |
Policy Group Acronym | OMB |
Policy Group Name | Operations Management Board |
Contact Group | operations at mailman.egi.eu |
Document Status | Final |
Approved Date | 18.06.2013 |
Procedure Statement | A procedure for removal of service type from production infrastructure. |
Owner | Owner of procedure |
Overview
The Service type decommission procedure was created to define steps which have to be taken to remove a service type from the production infrastructure.
Definitions
Please refer to the EGI Glossary for the definitions of the terms used in this procedure.
The key words "MUST", "MUST NOT", "REQUIRED", "SHALL", "SHALL NOT", "SHOULD", "SHOULD NOT", "RECOMMENDED", “MAY", and "OPTIONAL" in this document are to be interpreted as described in RFC 2119.
Steps
The process starts when the COO opens a GGUS ticket to the Operations SU (via GGUS). Each step which require contact with other teams should be done through GGUS as well (as a child ticket the main one).
This procedure is run if a software related to the service type is unsupported or it was decide to change the name of the service type.
Responsible | Action | |
---|---|---|
1 | COO | Decides and announce decommission deadline for the service type to OMB |
2 |
COO | The broadcast is send to NGI managers, Site administrators, VO managers |
4 | Nagios team | A security probe is developed for the security nagios that extracts hostnames from GOCDB and BDII associated to the decommissioned service type and raises critical alarm in the security dashboard |
5 | COD |
Followup the process till the decommission deadline |
After Decommision deadline
Responsible | Action | |
---|---|---|
1 | SAM team | Probes for the service type are removed from profiles:
|
2 |
GGUS | If for the service type specific SU in GGUS exists, the SU should be removed from GGUS. |
3 | GOCDB | The service type should be disabled in GOCDB (i.e. service entries can no more declared to be of the service type), but not removed. |
4 | COO | The broadcast is send to NGI managers, Site administrators and VO managers that the service type was decommissioned. |
Revision history
Version | Authors | Date | Comments |
---|---|---|---|