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.

Difference between revisions of "PROC19"

From EGIWiki
Jump to navigation Jump to search
(Created page with "{{Template:Op menubar}} {{Template:Doc_menubar}} {{TOC_right}} {{Ops_procedures |Doc_title = Temporary Cloud Resource Centre Registration and Certification |Doc_link = [[PROC09...")
 
Line 2: Line 2:


{{Ops_procedures
{{Ops_procedures
|Doc_title = Temporary Cloud Resource Centre Registration and Certification
|Doc_title = Introducing new stacks and middleware in EGI Production Infrastructure
|Doc_link = [[PROC09|https://wiki.egi.eu/wiki/PROC18]]
|Doc_link = [[PROC09|https://wiki.egi.eu/wiki/PROC19]]
|Version =  
|Version =  
|Policy_acronym = OMB
|Policy_acronym = OMB
Line 10: Line 10:
|Doc_status =  
|Doc_status =  
|Approval_date =  
|Approval_date =  
|Procedure_statement = A temporary 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).
|Procedure_statement = A procedure for the steps to introduce new stack (Cloud platform) or middleware (HTC Platform) in EGi Production Infrastructure.
}}  
}}  


Line 274: Line 274:
|}
|}


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


= Revision History  =
= Revision History  =

Revision as of 11:13, 18 August 2014

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 Introducing new stacks and middleware in EGI Production Infrastructure
Document link https://wiki.egi.eu/wiki/PROC19
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 to introduce new stack (Cloud platform) or middleware (HTC Platform) in EGi Production Infrastructure.
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

  • Cloud Resource Centre refers to the Resource Center definition in the "Resource Centre OLA". In addition Resource Center is planing to provide Cloud production quality resources.
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

Please see PROC09#Entities_involved_in_the_procedure

Prerequisites and responsibilities

Please see PROC09#Prerequisites_and_responsibilities


Resource Center status Workflow

Please see PROC09#Resource_Center_status_Workflow

Resource Centre registration

Requirements

Please see PROC09#Requirements

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. See instruction
  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 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.
  • Check domain names and forward and reverse DNS.
6 OC

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

7 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

Check:

  1. GOC DB: 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.
  2. Information system: Check that the eu.egi.cloud.information.bdii is working, and publishing coherent values* Propose to remove it *
    • Proposal to eliminate this step since the information system is not production level, yet (Peter S. 12 February 2014)
  3. Accounting
    • Host Certificate DN should be send to APEL-ADMINS@stfc.ac.uk
  4. Monitoring and troubleshooting should be possible:
    • the OPS VO (monitoring) and the DTEAM VO (troubleshooting) are configured and supported by the Resource Centre.
  5. OPS, Dteam and regional VOs are configured and supported as needed.
  6. Site is integrated in any regional tool as needed (for example, the regional accounting infrastructure if present).
5 RC

Fill the security survey (placeholder, survey not available yet) and forward the required information to the CSIRT.

  • The purpose of the survey is to assess that the technology used to provide cloud services fulfills the EGI security policies and procedures.
  • This is an additional step, not yet approved by OMB. Please, ignore until the survey is available (Peter S. 12 Feb 2014)
6 CSIRT

Checks that the Resource Centre passes the basic security assessment tests

This step also apples to certified Resource Centers which introduce cloud resources for the first time.

7 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. * Propose to remove it *
    • Proposal to eliminate this step since the information system is not production level, yet (Peter S. 12 February 2014)
  • The target 'Infrastructure' value should be set to 'Production'.
8 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.

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

10 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