Difference between revisions of "PROC12 Production Service Decommissioning"
Jump to navigation
Jump to search
(→Steps) |
(→Steps) |
||
Line 127: | Line 127: | ||
#:[''If the service is a storage or data management service''] After the announce of the service decommissioning the Resource Centre MAY disable VO writing access to prevent further VO activity - except infrastructure VOs (If selective permissions are not possible, the service must remain enabled also in writing until the begin of the downtime). | #:[''If the service is a storage or data management service''] After the announce of the service decommissioning the Resource Centre MAY disable VO writing access to prevent further VO activity - except infrastructure VOs (If selective permissions are not possible, the service must remain enabled also in writing until the begin of the downtime). | ||
|- valign="top" | |- valign="top" | ||
| | |4 | ||
| VO | | VO | ||
| | | | ||
Line 135: | Line 135: | ||
# [''If the service is a central service like VOMS or LFC for a given VO''] VO Manager, Resource Centre Operations Manager and Resource Infrastructure Operations Manager should discuss finding a new Resource Centre for hosting these services, taking into account pre-existing agreement between VO and NGI. For international VOs, this discussion could be held at the EGI level, especially if a solution cannot be easily found within that Resource Infrastructure Provider. | # [''If the service is a central service like VOMS or LFC for a given VO''] VO Manager, Resource Centre Operations Manager and Resource Infrastructure Operations Manager should discuss finding a new Resource Centre for hosting these services, taking into account pre-existing agreement between VO and NGI. For international VOs, this discussion could be held at the EGI level, especially if a solution cannot be easily found within that Resource Infrastructure Provider. | ||
|- valign="top" | |- valign="top" | ||
| | | 5 | ||
| RC | | RC | ||
| | | | ||
#According to the dates announced in the broadcast or differently agreed in step ''' | #According to the dates announced in the broadcast or differently agreed in step '''4''', the Resource Centre puts the service in downtime to prevent any further usage. This downtime shall last for the scheduled period or until phase 5 is over - which ever is the shorter. | ||
#* The downtime must be recorded in the ''master ticket'' <br> | #* The downtime must be recorded in the ''master ticket'' <br> | ||
|- valign="top" | |- valign="top" | ||
| | | 6 | ||
| RC | | RC | ||
| | | | ||
Line 148: | Line 148: | ||
*Once the service is in downtime and closed for write access (if possible) the Resource Centre Operations Manager opens N child tickets of the procedure's ''master ticket'' to each of the N VO managers of the N VOs the service supports. | *Once the service is in downtime and closed for write access (if possible) the Resource Centre Operations Manager opens N child tickets of the procedure's ''master ticket'' to each of the N VO managers of the N VOs the service supports. | ||
*The VOs are given up to the amount of time agreed in step ''' | *The VOs are given up to the amount of time agreed in step '''4''' - to retrieve their data from the decommissioning service. During this period, the Resource Centre should make sure that the servcie works for the different VOs to allow them to migrate their data. The VO managers can specify any specific requirements in their child ticket. For instance: | ||
**Request in the child ticket from the Resource Centre Operations Manager the time limit needed to retrieve data. | **Request in the child ticket from the Resource Centre Operations Manager the time limit needed to retrieve data. | ||
** (If the service is an SE) Request from VO central services admins the list of LFNs/DNs still having SURLs on SEs at that Resource Centre. | ** (If the service is an SE) Request from VO central services admins the list of LFNs/DNs still having SURLs on SEs at that Resource Centre. | ||
Line 161: | Line 161: | ||
|- valign="top" | |- valign="top" | ||
| 7 | | 7 | ||
| | | RC | ||
| | | | ||
#At the end of the scheduled downtime period or when step 6 is completed and validated: | #At the end of the scheduled downtime period or when step 6 is completed and validated: | ||
Line 178: | Line 178: | ||
|- valign="top" | |- valign="top" | ||
| 10 | | 10 | ||
| | | RC | ||
| | | | ||
#Service is removed from ''GOCDB''. | #Service is removed from ''GOCDB''. |
Revision as of 17:40, 3 February 2012
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 | Service Decommissioning Procedure |
Document link | |
Version - last modified | |
Policy Group Acronym | OMB |
Policy Group Name | Operations Management Board |
Contact Person | operational-documentation@mailman.egi.eu |
Document Status | DRAFT |
Approved Date | N/A |
Procedure Statement | A procedure for the steps involved to decommission a Service operated by a Resource Centre in the EGI infrastructure. |
Grid Service Decommissioning Procedure
This procedure drafts the good practices between a Resource Centre (aka site) and its users when a grid service is being decommissioned.
Definitions
- Resource Centre refers to the definition in the "Resource Centre OLA".
- In this document, the term "site" is deprecated, and Resource Centre has been used in its place.
- Other entities involved in this procedure are defined in the EGI Glossary.
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.
Entities involved in the procedure
- Resource Centre Operations Manager: person who is responsible for initiating the decommissioning procedure by contacting the Resource Infrastructure Operations Manager.
- Resource Infrastructure Operations Manager (aka NGI manager) : person who is responsible for finding and agreement with the VO Manager about the migration of the service in another site, in case the service is a VO specific service hosted by the site according to an agreement between the Resource Infrastructure Provider and the VO.
- Virtual Organizations (VO's): Data and other stateful objects of the supported VO's may be stored at the Resource Centre.
- Virtual Organizations (VO) managers: persons who are responsible for retrieving this data from the Resource Centre in due time. Tracking is done through their support unit in GGUS. If such support unit is not available, the VOs should be contacted directly using the contact information available in the VO ID card.
Contact information
- EGI Resource Infrastructure Providers are listed on the EGI web site
- A list of EGI Operations Centres with their respective contact information is available from the GOCDB
- The list of VO's served by a specific Resource Centre and their ID cards can be retrieved from the Operations Portal.
- The VO managers and their contact information for a specific VO can be retrieved from the Operations Portal.
Actions and responsibilities
Resource Centre Operations Manager
- The Resource Centre is responsible for decommissioning the service.
- The Resource Centre is responsible for updating the corresponding entries in the EGI configuration repository GOCDB.
- The Resource Centre Operations Manager is REQUIRED to provide the necessary Resource Centre information needed to complete the decommission process, and he/she is responsible for its accuracy and maintenance.
Resource Infrastructure Operations Manager
- A Resource Infrastructure Provider is REQUIRED to be responsible for all Resource Centres within its respective jurisdiction. For this reason the Resource Infrastructure Provider is responsible for assuring that all the Resource Centres follow this procedure for services decommissioning.
VO's and VO managers
- give the users the relevant information about the decommissioning (deadlines, involved resources, files, how to handle it)
- follow-up and support users in their file migration procedures until the deadline
- inform Resource Centre about the status of the migration(s)
Workflow
Service Centre decommissioning
Steps
- Actions tagged RC are the responsibility of the Resource Centre Operations Manager.
- Actions tagged RIP are the responsibility of the Resource Infrastructure Operations Manager.
- Actions tagged OC are the responsibility of the Operations Centre
# | Responsible | Action |
---|---|---|
1 | RC |
|
2 | RC |
|
3 | RC |
|
4 | VO |
|
5 | RC |
|
6 | RC |
If the service is a stateful service containing VO data:
If the service does not contain user/state persistent data (e.g. CE):
|
7 | RC |
|
9 | RC |
|
10 | RC |
|
11 | OC |
|