Difference between revisions of "PROC09 Resource Centre Registration and Certification"
Line 87: | Line 87: | ||
== Operations Centre == | == Operations Centre == | ||
# The Operations Centre is responsible | # The Operations Centre is responsible for registering (if applicable) and for certifying the site. | ||
# The Operations Centre is responsible | # The Operations Centre is responsible for registering an accepted site in the EGI configuration repository [[GOCDB|GOCDB]]. | ||
# The Operations Centre MUST collect the mandatory information specified by the site registration procedure, and MUST accurately input the supplied data into GOCDB. | # The Operations Centre MUST collect the mandatory information specified by the site registration procedure, and MUST accurately input the supplied data into the GOCDB. | ||
# The Operations Centre MUST integrate site information in all operations tools as needed, such as the local NAGIOS server for monitoring of uncertified sites, the local helpdesk (if available) for the registration of the Resource Centre support staff, etc. | # The Operations Centre MUST integrate site information in all operations tools as needed, such as the local NAGIOS server for monitoring of uncertified sites, the local helpdesk (if available) for the registration of the Resource Centre support staff, etc. | ||
# In case of an existing site that is starting certification after suspension or security reasons, the Operations Centre MUST contact the EGI CSIRT to verify that all requested repair operations have been successfully applied to fix the issue. | # In case of an existing site that is starting certification after suspension or security reasons, the Operations Centre MUST contact the EGI CSIRT to verify that all requested repair operations have been successfully applied to fix the issue. |
Revision as of 11:33, 15 March 2011
Title | Resource Centre (Site) Registration and Certification Procedure |
Document link | to be determined |
Last modified | |
Policy Group Acronym | OMB |
Policy Group Name | Operations Management Board |
Contact Person | Vera Hansper |
Document Status | DRAFT |
Approved Date | |
Procedure Statement | A procedure for the steps involved to both register and certify new Resource Centres (sites) in the EGI infrastructure. The certification step can also be used to re-certify suspended Resource Centres (sites). |
Introduction
Certification is a prerequisite for a Resource Centre (aka site) to become part of a Resource Infrastructure such as a National Grid Initiative (NGI) and EIRO (in Europe), or multi-country Resource Infrastructure.
This document describes the steps required
- to register and certify a new site,
- to re-certify a site which has been suspended.
Note: A separate document provides the process for decommissioning a site.
Through its parent Resource Infrastructure, a certified Resource Centre becomes member of the EGI Resource Infrastructure to make resources available to international user communities.
A certified Resource Centre (site) guarantees a minimum quality of service of these resources (currently expressed in terms of monthly availability and reliability): the site must ensure troubles are handled in a timely fashion and the site must understand and adhere to a common set of policies and procedures. This compares to an uncertified, or test Resource Centre, which does not provide a guarantee on the availability or usability of it's resources.
Definitions
The 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 (or Site) Operations Manager, who is responsible of initiating the certification process by applying for membership to a Resource Infrastructure
- Resource Infrastructure Operations Manager, who is responsible of approving the integration of a new Resource Centre into the respective Infrastructure
- Operations Centre, the entity who is technically responsible of carrying out the Resource Centre certification part of the procedure, once the membership is approved
The Resource Infrastructure Operations Manager can determine with the Site Operations Manager the level of involvement of other actors.
Contact information
- EGI Operations: operations (at) mailman.egi.eu
- EGI Resource Infrastructure Providers are listed on the EGI site
- Operations Centres with the respective contact information is available from GOCDB
- EGI CSIRT: egi-csirt-team (at) mailman.egi.eu
Actions and responsibilities
Site Operations Manager
- A Resource Infrastructure Provider is responsible for all sites within the respective jurisdiction (for example, an NGI is responsible for all site in its country). For this reason, the Site Operations Manager of a new site is REQUIRED
- to contact the respective NGI if the Site is located in Europe,
- to contact the respective Resource Infrastructure Provider active in a relevant geographical area if the Site is outside Europe,
about the intention to join the EGI infrastructure. If needed, EGI Operations can assist the Site Operations Manager to get in contact with the relevant partners (see the Contact information section).
- The Site Operations Manager is REQUIRED to provide the necessary Site information needed to complete the registration process, is responsible for its accuracy and maintenance.
- In order to be certified, the Site Operations Manager is responsible for reading, understanding and accepting the Resource Centre Operational Level Agreement, which defines the obligations of a Resource Centre and the commitment to deliver a minimum quality of service to its future users. Endorsement of the OLA implies - among other things - the acceptance of:
- the Grid Security Policy
- the Grid Site Operations Policy
- the Site Registration Security Policy
- all other policies for all EGI participants from the Security Policy Group
Resource Infrastructure Operations Manager
- A Resource Infrastructure Provider is REQUIRED to be responsible for all sites within its respective jurisdiction. For example, an NGI is responsible for all sites in its respective country.
- The Resource Infrastructure Operations Managers MUST attend site certification applications and MUST provide feedback to the requesting partners in a timely manner to accept or reject the requests received.
- If the Site needs to be certified, s/he MUST provide information to the Site Operations Manager about the Resource Centre OLA, and is responsible for keeping records of the Site Operations Manager agreement, as deemed suitable by the Resource Infrastructure Provider (for example, through a signed e-mail agreement, the collection of signatories on a paper copy of the OLA, or other means).
- For the case where a request is accepted, the Resource Infrastructure Operations Manager MUST contact the relevant Operations Centre to start the site registration as a candidate and the certification procedure. Registration is only needed for the case of new sites.
Operations Centre
- The Operations Centre is responsible for registering (if applicable) and for certifying the site.
- The Operations Centre is responsible for registering an accepted site in the EGI configuration repository GOCDB.
- The Operations Centre MUST collect the mandatory information specified by the site registration procedure, and MUST accurately input the supplied data into the GOCDB.
- The Operations Centre MUST integrate site information in all operations tools as needed, such as the local NAGIOS server for monitoring of uncertified sites, the local helpdesk (if available) for the registration of the Resource Centre support staff, etc.
- In case of an existing site that is starting certification after suspension or security reasons, the Operations Centre MUST contact the EGI CSIRT to verify that all requested repair operations have been successfully applied to fix the issue.
- The Operations Centre is responsible of verifying that all tests during the 3 calendar day certification process are successfully passed. The Operations Centre SHALL proceed with changing the site status in GOCDB to certified only if this condition is met.
Workflow
The various steps then required by both the Resource Infrastructure Operations Manager and the Site Operations Manager are explained in the tables below. The first part for a new site is the registration process. The actual certification process, in the second table, is applicable to both new and suspended Sites.
The general status flow that a Site is allowed to follow is illustrated by the following diagram. Information on site status and on how to manipulate it available from GOCDB Documentation.
Site registration
Requirements
- A Site MUST be part of a Resource Infrastructure and MUST be operated by an Operations Centre. If there is no suitable provider for your country, it may be that the an Operations Centre MUST first be created. A procedure exists for this, and it is documented in the Operations Centre creation procedure.
- To satisfy Grid security requirements a Site registration procedure must capture and maintain at least the following information. The comprehensive list of required information is available (here).
- The full name of the Site.
- An abbreviated name of the Site, which must be unique within the Grid, and preferably globally unique.
- The name, email address and telephone number of the Site Operations Manager and Site Security Contact in accordance with the requirements of the Site Operations Policy.
- The email address of a managed list for contact with Site Administrators at the site.
- The email address of a managed list for contact with the site security incident response team.
- If a Site wishes to leave the Grid or the Grid decides to remove the Site, the registration information MUST be kept by GOCDB for at least the same period defined for logging in the Traceability and Logging Policy. Personal registration information of the Site Operations Manager and Security Contact of the Site leaving the Grid MUST NOT be retained for longer than one year.
- It is RECOMMENDED that email contacts for the Site Administrators and Security Officer(s) are mailing lists, and not individuals.
<Comment: additional constraints - if any - on information that is registered need to be specified here>
Steps
The following steps are only applicable if the Site is not already registered in GOCDB. They describe the steps for a Site Operations Manager that is requesting the respective Site to join the EGI infrastructure.
- Actions tagged Site are the responsibility of the Site 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 |
---|---|---|
0 | Site |
|
1 | RIP |
|
2 | OC |
|
3 | OC |
|
4 | Site |
|
5 | Site or OC |
|
6 | OC |
|
7 | OC |
|
8 | OC |
|
After the successful completion of all these steps, the site is considered as to be in the "Candidate" state and is ready for the certification process.
Site certification
Requirements
- The Site Certification procedure is only applicable for both Sites in "Candidate" or "Suspended" status state and for suspended sites.
- In order to enter certification the Site Operations Managers SHALL accept the Resource Centre OLA.
- A Site can successfully pass certification only if the conditions required by the Resource Centre OLA are met.
Steps
The following is a detailed description of the steps required for the transition from the "Uncertified" to the "Certified" state of the site.
- Actions tagged Site are the responsibility of the Site 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 |
---|---|---|
0 | RIP |
|
1 | Site |
|
2 | RIP |
|
3 | OS |
|
4 | OS |
There are detailed examples for how to do this in SiteCertMan/GIIS_BDII_check. |
5 | OS |
Details for submitting manual tests can be found at SiteCertMan/Grid_manual_tests. |
6 | OS |
|
7 | OS | #After two days check that the site appears in all operational tools. If there are problems with a specific tool, open GGUS tickets to the relevant Support Units. The major tools that are relevant are:
|
8 | OS | #Ensure that, before the end of the maintenance downtime
|
9 | OS |
|
10 | OS |
|
11 | OS |
|
After the successful completion of these steps, the site is considered as "Certified".
Revision history
Version | Authors | Date | Comments |
---|---|---|---|
0.8 | Tiziana Ferrari | 2011-03-11 | Updated introduction, adopted MUST SHALL etc. terminology, proposed some changes to terminology, added a section with a list of responsibilities, added a few comments into the text to request clarifications. |
0.7 | Vera Hansper | 2011-02-02 | Updated introduction to include roles, etc. and added required documentation link for policies |