Difference between revisions of "PROC09 Resource Centre Registration and Certification"

From EGIWiki
Jump to: navigation, search
Line 283: Line 283:
 
#Check that the GIIS (gLite: BDII) is working, and publishing coherent values, namely:  
 
#Check that the GIIS (gLite: BDII) is working, and publishing coherent values, namely:  
 
#*the correct NGI is being published in GlueSiteOtherInfo (see manual MAN01 [[MAN1 How to publish Site Information|How to Publish Site Information]]).  
 
#*the correct NGI is being published in GlueSiteOtherInfo (see manual MAN01 [[MAN1 How to publish Site Information|How to Publish Site Information]]).  
#*all services are registered in GOCDB according to the requirements of the [https://documents.egi.eu/document/31 Resource Centre OLA], these are published and ALSO that services published in the GOCDB are valid.  
+
#all services are registered in GOCDB according to the requirements of the [https://documents.egi.eu/document/31 Resource Centre OLA], these are published and ALSO that services published in the GOCDB are valid.  
#*the [[OPS vo|OPS VO]] (monitoring) and the [[Dteam vo|DTEAM VO]] (troubleshooting) are configured and supported by the Resource Centre.  
+
#the [[OPS vo|OPS VO]] (monitoring) and the [[Dteam vo|DTEAM VO]] (troubleshooting) are configured and supported by the Resource Centre.  
#*regional VOs are configured and supported as needed by the Operations Centre.  
+
#regional VOs are configured and supported as needed by the Operations Centre.  
#*the Resource Centre is integrated in any regional tool as needed (for example, the regional accounting infrastructure if present).
+
#the Resource Centre is integrated in any regional tool as needed (for example, the regional accounting infrastructure if present).
  
 
There are detailed examples for how to do this in [[Operations/HOWTO03|GIIS/BDII check]].  
 
There are detailed examples for how to do this in [[Operations/HOWTO03|GIIS/BDII check]].  
Line 372: Line 372:
 
= Revision History  =
 
= Revision History  =
  
*7/09/2012: (editorial, M.&nbsp;Krakowian) typos and adding links where necessary<br>
+
*7/09/2012: (editorial, M.&nbsp;Krakowian) typos and adding links where necessary<br>  
 
*25/10/2011: (editorial, T. Ferrari) Replacement of RIP with "RP" standing for Resource infrastructure Provider
 
*25/10/2011: (editorial, T. Ferrari) Replacement of RIP with "RP" standing for Resource infrastructure Provider
  

Revision as of 14:46, 7 September 2012

Main EGI.eu operations services Support Documentation Tools Activities Performance Technology Catch-all Services Resource Allocation Security


 


Title Resource Centre Registration and Certification Procedure
Document link https://wiki.egi.eu/wiki/PROC09
Version - last modified 1.0 - 17 May 2011
Policy Group Acronym OMB
Policy Group Name Operations Management Board
Contact Person operational-documentation@mailman.egi.eu
Document Status APPROVED
Approved Date 17 May 2011
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).

Resource Centre Registration and Certification Procedure

Certification is a prerequisite for a Resource Centre (aka site) to become part of a Resource Infrastructure such as a National Grid Initiative (NGI), an EIRO, or a multi-country Resource Infrastructure.

This document describes the steps required

  1. to register and certify a new Resource Centre,
  2. to re-certify a Resource Centre which has been suspended.

Note: A separate document provides the process for decommissioning a Resource Centre.

Through its parent Resource Infrastructure, a certified Resource Centre becomes a member of the EGI Resource Infrastructure to make resources available to international user communities.

The main difference between a certified Resource Centre and an uncertified or test Resource Centre is that a certified Resource Centre provides and guarantees a minimum quality of service of the resources (currently expressed in terms of monthly availability and reliability): the certified Resource Centre must ensure problems are handled in a timely fashion and the certified Resource Centre must understand and adhere to a common set of policies and procedures. All the requirements can be found in the Resource Centre OLA.

Definitions

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 certification process by applying for membership to a Resource Infrastructure.
  • Resource Infrastructure Operations Manager: person who is responsible for approving the integration of a new Resource Centre into the respective Infrastructure.
  • Operations Centre: entity which is technically responsible for carrying out the Resource Centre certification part of the procedure, once the membership is approved.

The Resource Infrastructure Operations Manager can determine with the Resource Centre 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 web site
  • A list of EGI Operations Centres with their respective contact information is available from the GOCDB
  • EGI CSIRT: egi-csirt-team (at) mailman.egi.eu

Actions and responsibilities

Resource Centre Operations Manager

  1. A Resource infrastructure Provider is responsible for all Resource Centres within its respective jurisdiction (for example, an NGI is responsible for all Resource Centres in its country). For this reason, the Resource Centre Operations Manager of a new Resource Centre is REQUIRED
    • to contact the respective NGI if the Resource Centre is located in Europe,
    • to contact the respective Resource infrastructure Provider active in a relevant geographical area if the Resource Centre is outside Europe, about the intention of the Resource Centre to join the EGI infrastructure. If needed, EGI Operations can assist the Resource Centre Operations Manager to get in contact with the relevant partners (see the Contact information section).
  2. The Resource Centre Operations Manager is REQUIRED to provide the necessary Resource Centre information needed to complete the registration process, and he/she is responsible for its accuracy and maintenance.
  3. In order to be certified, the Resource Centre 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:

Resource Infrastructure Operations Manager

  1. A Resource infrastructure Provider is REQUIRED to be responsible for all Resource Centres within its respective jurisdiction. For example, an NGI is responsible for all Resource Centres in its respective country.
  2. The Resource Infrastructure Operations Managers MUST attend Resource Centre certification applications and MUST provide feedback to the requesting partners in a timely manner to accept or reject the requests received.
  3. If the Resource Centre needs to be certified, s/he MUST provide information to the Resource Centre Operations Manager about the Resource Centre OLA, and is responsible for keeping records of the Resource Centre Operations Manager agreement, as deemed suitable by the Resource infrastructure Provider (for example, through a signed e-mail agreement, a collection of signatories on a paper copy of the OLA, or other means).
  4. For the case where a request is accepted, the Resource Infrastructure Operations Manager MUST contact the relevant Operations Centre to start the Resource Centre registration as a candidate for the certification procedure. Registration is only needed for the case of new Resource Centres.

Operations Centre

  1. The Operations Centre is responsible for registering (if applicable) and for certifying the Resource Centre.
  2. The Operations Centre is responsible for registering an accepted Resource Centre in the EGI configuration repository GOCDB.
  3. The Operations Centre MUST collect the mandatory information specified by the Resource Centre registration procedure, and MUST accurately input the data supplied into the GOCDB.
  4. The Operations Centre MUST integrate Resource Centre information in all operations tools as needed, such as the local NAGIOS server for monitoring of certified Resource Centres, the local helpdesk (if available) for the registration of the Resource Centre support staff, etc.
  5. In the case of an existing Resource Centre that is resuming certification after suspension for 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.
    • For other suspension cases, the Operations Center MUST ensure that the issue that caused the suspension has been resolved.
  6. The Operations Centre is responsible for verifying that all tests during the 3 calendar day certification process are successfully passed. The Operations Centre SHOULD only proceed with changing the Resource Centre status in the GOCDB to certified if this condition is met.

Workflow

The various steps required by both the Resource Infrastructure Operations Manager and the Resource Centre Operations Manager are explained in the tables below. The first part for a new Resource Centre is the registration process. The actual certification process, in the second table, is applicable to both new and suspended Resource Centres.

The general status flow that a Resource Centre is allowed to follow is illustrated by the following diagram. Information on Resource Centre status and on how to manipulate it is available from GOCDB Documentation.

SiteStatusFlow.png


A Resource Centre cannot be in

  • Candidate state for more than two months
  • Suspended state for more than four months

After this period the Resource Centre SHOULD be closed.

Resource Centre registration

Requirements

  1. A Resource Centre MUST be part of a Resource Infrastructure and gets operational services offered by a Operations Centre. If a provider is not yet available for your country, then an alternative existing Operations Centre can be contacted. A procedure exists for this, and it is documented in the Operations Centre creation procedure.
  2. To satisfy Grid security requirements during the registration procedure the following information must be collected. The comprehensive list of required information is available (here).
    • The full name of the Resource Centre.
    • An abbreviated name for the Resource Centre, which must be unique within the Grid, and preferably globally unique.
    • The name, email address and telephone number of the Resource Centre Operations Manager and Resource Centre Security Contact in accordance with the requirements of the Resource Centre Operations Policy.
    • The email address of a managed list for contact with Resource Centre Administrators at the Resource Centre.
    • The email address of a managed list for contact with the Resource Centre security incident response team.

Notes:

  1. If a Resource Centre wishes to leave the Grid or the Grid decides to remove the Resource Centre, 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 Resource Centre Operations Manager and Security Contact of the Resource Centre leaving the Grid MUST NOT be retained for longer than one year.
  2. It is RECOMMENDED that email contacts for the Resource Centre Administrators and Security Officer(s) are mailing lists, and not individuals.The contacts information SHOULD be available at the moment of the Resource Centre registration in GOCDB.


Steps

The following steps are only applicable if the Resource Centre is not already registered in GOCDB. They describe the steps for a Resource Centre Operations Manager that is requesting the respective Resource Centre to join the EGI infrastructure.

  • Actions tagged RC are the responsibility of the Resource Centre Operations Manager.
  • Actions tagged RP are the responsibility of the Resource Infrastructure Operations Manager.
  • Actions tagged OC are the responsibility of the Operations Centre
# Responsible Action
0 RC
  1. Contact your Resource Infrastructure Operations Manager (contact information is available at http://www.egi.eu/community/resource-providers/).
  2. Provide your Resource Infrastructure Operations Manager the required information according to the template available in the Required information page.
1 RP
  1. Parse the Resource Centre registration request, decide to accept or reject it, and communicate this result back to applicant.
  2. If the Resource Centre is accepted, notify the relevant Operations Centre, handle the Resource Centre information received, and put the Operations Centre in contact with the Resource Centre Operations Manager.
2 OC
  1. The following actions can be done in parallel:
    • Forward all necessary and required documentation to install and configure the Resource Centre services to the Resource Centre Operations Manager.
    • Communicate with the Operations Manager to clarify any doubts or questions. Include the Operations Centre ROD, CSIRT,  or help-desk teams in the step if necessary.
3 OC
  1. Add the Resource Centre to the GOCDB and flag it as "Candidate". Note that all users with a GOCDB role at regional level can add a Resource Centre in scope (this includes Operations Manager, deputy and regional staff). Currently, GOCDB applies the same permissions to all of the "regional level roles".
  2. Notify the Resource Centre Operations Manager that they should request for grid certificate, register in Dteam VO, register themself in the GOCDB and request the Resource Centre Administrator role. Approve it when done.
4 RC
  1. Complete any missing information for the Resource Centre's entry in the GOCDB, including services that are to be integrated into the infrastructure.
  2. Request in the GOCDB (or ask the relevant Resource Centre security staff to request) the mandatory Resource Centre Security Officer role. A security expert is the most appropriate actor for this role. See the GOCDB Input System User Documentation for more information on roles.
  3. Accept or deny all the requested roles under the Resource Centre scope. Note: If the Resource Centre Operations Manager can not approve roles, they should request the Operations Centre to do so. This is a current flaw in GOCDB.
  4. Notify the Operations Centre that the Resource Centre information update is concluded.
5 RC or OC
  1. Check whether the Resource Centre appears in the "Notified Site" field in https://ggus.eu/ws/ticket_search.php
  2. Note that this step should happen automatically when the Resource Centre is correctly entered into the GOCDB. If this is still not visible 2 days after the GOCDB entries have been created, the Operations Centre should be informed and should then contact GGUS administrators through GGUS.
  3. A new Resource Centre Administrator should register in GGUS (https://ggus.eu/admin/get_account.php?accounttype=support) but not specify any role, unless directed to by the Operations Centre.
6 OC
  1. Check that the Resource Centre's information is correct (Resource Centre (site) roles and any other additional information.)
  2. Check that contacts receive email (if they are mailing lists, check that outside EGI members are allowed to post there). Site administrator MUST reply to the test email.
  3. Check that the required services for a Resource Centre are properly registered. Note that for Resource Centre adopting APEL, by registering a new glite-APEL node in GOCDB as gLite-APEL service including the correct DN, the APEL broker Access Control List gets automatically updated and Resource Centres can start publishing usage records in about two hours (for more information see the gLite-APEL documentation).
  4. Check domain names and forward and reverse DNS.
7 OC
  1. Any other Operations Centre-specific requirements (e.g. join a certain VO and/or mailing list, etc.)
8 OC
  1. If all previous actions have been completed with success, notify the Resource Centre Operations Manager that the Registration is completed, and contact the Resource Infrastructure Operations Manager to notify that a new candidate Resource Centre exists and is ready to be certified.

After the successful completion of all these steps, the registration phase is completed and the Resource Centre is ready for the start of the certification phase.

Resource Centre certification

Requirements

  1. The Resource Centre Certification procedure is only applicable for both Resource Centres in "Candidate" or "Suspended" status state.
  2. The following procedure is only applicable if the Resource Centre is already registered in GOCDB.
  3. In order to enter certification the Resource Centre Operations Managers SHALL accept the Resource Centre OLA.
  4. A Resource Centre 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 Resource Centre.

  • Actions tagged RC are the responsibility of the Resource Centre Operations Manager.
  • Actions tagged RP are the responsibility of the Resource Infrastructure Operations Manager.
  • Actions tagged OC are the responsibility of the Operations Centre
# Responsible Action
0 RP
  1. The Resource Infrastructure Operations Manager contacts the Resource Centre Operations Manager to request the subscription of the Resource Centre OLA.
1 RC
  1. The Resource Centre Operations Manager notifies the Resource Infrastructure Operations Manager that the Resource Centre OLA is accepted (if the Resource Centre is has not already endorsed it before for example in case of a suspended Resource Centre), and the Resource Centre is ready to start certification.
2 RP
  1. The Resource Infrastructure Operations Manager contacts the Operations Centre asking to start the certification process.
3 OC
  1. If the Resource Centre is in the "Candidate" or "Suspended" state, then flag the Resource Centre as "Uncertified". If it was in the "Suspended" state then check that the reason for suspension has been cleared. If the suspension cause is a security issue, then the EGI CSIRT needs to be contacted to verify that all requested repair operations were successully applied by the Resource Centre Administrators to fix the issue that caused suspension. See instructions on how to monitor uncertified RCs.
4 OC
  1. Add Resource Centre contact information to any regional mailing list and provide access to regional tools as required
5 OC
  1. Check that the GIIS (gLite: BDII) is working, and publishing coherent values, namely:
  2. all services are registered in GOCDB according to the requirements of the Resource Centre OLA, these are published and ALSO that services published in the GOCDB are valid.
  3. the OPS VO (monitoring) and the DTEAM VO (troubleshooting) are configured and supported by the Resource Centre.
  4. regional VOs are configured and supported as needed by the Operations Centre.
  5. the Resource Centre is integrated in any regional tool as needed (for example, the regional accounting infrastructure if present).

There are detailed examples for how to do this in GIIS/BDII check.

6 OC
  1. Check that the registered services are fully functional by performing manual tests. e.g. from the UI or the Operations Centre monitoring infrastructure for uncertified Resource Centres. Note that monitoring of uncertified Resource Centres through the NGI Nagios production service is possible (instructions). Contact the Resource Centre admins if there are problems, and ensure that they fix them. Include the ROD, CSIRT and help-desk teams if necessary. Iterate this step with the Resource Centre admins until tests pass successfully. The prime tests to check are:
    • network connectivity.
    • CE job submission.
    • SE data transfer

Details for submitting manual tests can be found at Grid manual tests.

7 OC
  1. If all preliminary tests are passed for 3 consecutive calendar days, declare an initial maintenance downtime and switch the Resource Centre status to Certified. This ensures that Resource Centre will appear in NAGIOS and GSTAT.
8 OC
  1. The downtime should not be closed until the Resource Centre appears in all operational tools and accounting data is properly published. The major tools that are relevant are:
    • Regional NAGIOS (NAGIOS)
      • And all Nagios tests are passed
    • Operations Dashboard (Dashboard-Siteview)
    • GridView
    • GSTAT
      • GSTAT is not in an error state. Note: There may be some problems with this tool and ARC Resource Centres.
    • MyEGI

If there are problems with a specific tool, open GGUS tickets to the relevant Support Units. Wait at least two days after the switch to the Certified status to open the ticket, the propagation of the new status to the operational tools or the publication of accounting data may take one or two days.

9 OC
  1. Notify the Resource Centre Operations Manager that the Resource Centre is certified
10 OC
  1. The NGI can broadcast that a new Resource Centre is now part of the EGI infrastructure. This step is OPTIONAL.

After the successful completion of these steps, the Resource Centre is considered as "Certified".

Revision History

  • 7/09/2012: (editorial, M. Krakowian) typos and adding links where necessary
  • 25/10/2011: (editorial, T. Ferrari) Replacement of RIP with "RP" standing for Resource infrastructure Provider

Template:Creative commons