Home Feedback Site map English Ukrainian
 
About us
Join the Grid sites
Certification Grid - users
VO Registration
UNG documents
UNG resources
International cooperation
Training
Grid in questions and answers
News
Grid achieve
Contacts
Main  / Join the Grid sites  /  The procedure for registration of Grid sites

The procedure for registration of Grid sites

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 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 theResource 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.
  3. 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.
  4. 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
#ResponsibleAction
0 RC
  1. Contact your Resource Infrastructure Operations Manager (contact information is available at http://www.egi.eu/infrastructure/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 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 register them self 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. Caveat: 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://gus.fzk.de/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.
  3. A new Resource Centre Administrator should register in GGUS (https://gus.fzk.de/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 and for suspended Resource Centres.
  2. In order to enter certification the Resource Centre Operations Managers SHALL accept the Resource Centre OLA.
  3. 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
#ResponsibleAction
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 operationswere successully applied by the Resource Centre Administrators to fix the issue that caused suspension.
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:
    • the correct NGI is being published in GlueSiteOtherInfo (see manual MAN01 How to Publish Site Information).
    • 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.
    • the OPS VO (monitoring) and the DTEAM VO (troubleshooting) are configured and supported by the Resource 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).

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 Natios production service is possible (instructions). Contact the Resource Centre admins if there are problems, and ensure that they fix them. Include the ROD 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. CAVEAT: 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". 
© 2011-2012, Bogolyubov Institute for Theorethical Physics Site Information Developed in MCG