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.

PROC18 Temporary Cloud Resource Centre Registration and Certification

From EGIWiki
Revision as of 14:34, 5 August 2013 by Krakow (talk | contribs) (Created page with "{{Template:Op menubar}} {{Template:Doc_menubar}} {{TOC_right}} {{Ops_procedures |Doc_title = Cloud Resource Centre Registration and Certification |Doc_link = [[PROC09|https://w...")
(diff) ← Older revision | Latest revision (diff) | Newer revision → (diff)
Jump to navigation Jump to search
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 Cloud Resource Centre Registration and Certification
Document link https://wiki.egi.eu/wiki/PROC18
Last modified
Policy Group Acronym OMB
Policy Group Name Operations Management Board
Contact Group operations at mailman.egi.eu
Document Status
Approved Date
Procedure Statement A procedure for the steps involved to both register and certify new Cloud Resource Centres (sites) in the EGI infrastructure. The certification step can also be used to re-certify suspended Cloud Resource Centres (sites).
Owner Owner of procedure



Overview

Certification is a verification process for a Cloud 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 to

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

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

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

The main difference between a certified Cloud Resource Centre and an uncertified or test Cloud Resource Centre is that a certified Cloud Resource Centre provides and guarantees a minimum quality of service of the resources (currently expressed in terms of monthly availability and reliability). 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.

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.

Entities involved in the procedure

Following entities are involved in the process described in the procedure:


Resource Centre Operations Manager
A person who is responsible for initiating the certification process by applying for membership to a Resource Infrastructure. e.g site administrator
Resource Infrastructure Operations Manager
A person who is responsible for approving the integration of a new Resource Centre into the respective Infrastructure. e.g. NGI manager.
EGI Resource infrastructure Providers are listed on the EGI web site
Operations Centre (Resource Infrastructure)
An entity which is technically responsible for carrying out the Resource Centre certification part of the procedure, once the membership is approved.
A list of EGI Operations Centres with their respective contact information is available from the GOCDB (access restricted - grid certificate needed)
Response Team
EGI entity which is technically responsible for carrying out the security certification.
contact: egi-csirt-team (at) mailman.egi.eu


The Resource Infrastructure Operations Manager can determine with the Resource Centre Operations Manager the level of involvement of other actors.

Prerequisites and responsibilities

Resource Centre Operations Manager

Resource Center Operations Manager is:

  1. responsible for all Resource Centres within its respective jurisdiction. For this reason, the Resource Centre Operations Manager is REQUIRED to
    • contact the respective Operations Center if the Resource Centre is located in Europe,
    • contact the respective Resource infrastructure Provider active in a relevant geographical area if the Resource Centre is outside Europe.
      • If needed, EGI Operations can assist the Resource Centre Operations Manager to get in contact with the relevant partner.
  2. 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. responsible for reading, understanding and accepting:

Resource Infrastructure Operations Manager

Resource Infrastructure Operations Manager:

  1. is REQUIRED to be responsible for all Resource Centres within its respective jurisdiction.
  2. 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. is responsible for keeping records of the Resource Centre Operations Manager OLA 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.

Operations Centre

The Operations Center:

  1. is responsible for registering (if applicable) and certifying the Resource Centre.
  2. (In the case of re-certification)MUST ensure that the issue that caused the suspension has been resolved
    • (After suspension for security reason)MUST contact the EGI CSIRT to verify that all requested repair operations have been successfully applied to fix the issue.


Resource Center status Workflow

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


Timelines

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

A Resource Centre MUST

  1. find a rescpective Resource Infrastructure which will provide operational services to the Resource Center. If a provider is not yet available for your country, then an alternative existing Operations Centre can be contacted. 
  2. provide required information: HOWTO01 Site Certification Required Information.


Notes: 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.

Steps

The following steps are only applicable if the Resource Centre is not already registered in GOCDB.

  • 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

Contact your Resource Infrastructure Operations Manager (contact information is available at EGI web site).

  • Provide the required information according to the template available in the Required information page.
1 RP

Accept or reject registration request and communicate this result back to applicant.

  • 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. Forward all documentation:
  2. 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 GOCDBand flag it as "Candidate".
  2. Notify the Resource Centre Operations Manager that he/she should Join operations
    • In the GOCDB he/she should request the 'Resource Centre Operations Manager' role. Approve it when done.
  3. Notify the Resource Centre Operations Manager that person responsible for security should Join operations
    • In the GOCDB he/she should request the 'Resource Centre Security Officer' role. Approve it when done.
4 RC
  1. Complete any missing information for the Resource Centre's entry in the GOCDB
    • It includs services that are to be integrated into the infrastructure.
  2. Notify the Operations Centre that the Resource Centre information update is concluded.
  3. Note: If the external RC is considering buying host certs, please make sure they source them from an EGI recognised authority. The local national CA (usually for free or at flat rate) is likely the best source of their SSL certificates.
5 RC or OC
  1. Check GGUS if the Resource Centre appears in the "Notified Site" field - GGUS search
    • 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.
  2. A new Resource Centre Administrator should register in GGUS but not specify any role, unless directed to by the Operations Centre.
6 OC

Check GOC DB that the Resource Centre's information is correct.

  • Resource Centre (site) roles and any other additional information.
  • 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.
  • 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).
  • Check domain names and forward and reverse DNS.
7 OC

Any other Operations Centre-specific requirements (e.g. join a certain VO and/or mailing list, etc.)

8 OC

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 in GOC DB.
  2. 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 "Candidate"/"Suspended" 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
  • Actions tagged CSIRT are the responsibility of the Computer Security Incident Response Team
# Responsible Action
0 RP

The Resource Infrastructure Operations Manager contacts the Resource Centre Operations Manager to request the subscription of the Resource Centre OLA.

1 RC

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

The Resource Infrastructure Operations Manager contacts the Operations Centre asking to start the certification process.

3 OC

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 successfully applied by the Resource Centre Administrators to fix the issue that caused suspension. See instructions on how to monitor uncertified RCs.
4 OC

Add Resource Centre contact information to any regional mailing list and provide access to regional tools as required.

5 OC

Check:

GOC DB: All services are registered in GOCDBaccording to the requirements of the Resource Centre OLA, these are published and ALSO that services published in the GOCDB are valid.

  1. Information system: Check thatthe GIIS (gLite, Globus: BDII) is working, and publishing coherent values
  2. Monitoring and troubleshooting should be possible:
    • Glite, ARC: the OPS VO (monitoring) and the DTEAM VO (troubleshooting) are configured and supported by the Resource Centre.
    • UNICORE: all certificates used by monitoring users must have the 'user' role assigned using any attribute source supported by the Resource Centre and must be mapped to a local account with the same permissions as assigned to an ordinary infrastructure user.
    • Globus:
    1. The OPS VO and DTEAM VO are configured and supported for those resource centres supporting the VO concept (via the lcas lcmaps adaptors for Globus)
    2. Robot certificates from the RP should be entered in the gridmap files to enable these checks. Please contact your RP for more information about this.
    • QCG:
    1. All certificates used by monitoring users must be mapped to a local account with the same permissions as assigned to an ordinary infrastructure user.
    2. The certificate of the regional instance of QCG-Broker must be authorized.
  3. OPS, Dteam and regional VOs are configured and supported as needed.
  4. Site is integrated in any regional tool as needed (for example, the regional accounting infrastructure if present).
6 OC

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.
    • job submission.
    • data transfer

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

7 CSIRT

Checks that the Resource Centre passes the basic security assessment tests, consisting of a suite of nagios security probes and the patch status monitoring tool (eg. Pakiti). Especially the Resource Centre MUST NOT reveal critical vulnerabilities as defined from SVG/CSIRT

  • The security assessment is performed by the NGI security officers using the tools provided by, and with assistance of the EGI CSIRT.
  • NGI security officer should contact CSIRT via abuse@egi.eu
8 OC

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.
  • The target 'Infrastructure' value should be set to 'Production'.
9 OC

The downtime should not be closed until the Resource Centre

  • appears in all operational tools
  • accounting data is properly published.


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.

10 OC Notify the Resource Centre Operations Manager that the Resource Centre is certified

11 OC

The Operation Center 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

Version Authors Date Comments

Malgorzata 18.03 RC Certification steps: Step 5 added part concerning QCG