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 "PROC02 Operations Centre creation"

From EGIWiki
Jump to navigation Jump to search
Line 119: Line 119:




Parent ROC/OCC creating child tickets toThe child tickets should be created in the order given as follows:
Parent ROC/OCC creating child tickets in the order given as follows:


3 - GOCDB to perform: Creation of a new NGI entry in GOCDB (with no site attached). (Wait until done.)
3 - GOCDB to perform: Creation of a new NGI entry in GOCDB (with no site attached). (Wait until done.)

Revision as of 13:51, 16 June 2010

The purpose of this document is to describe clearly the steps to be done and actions to be taken for integrating a NGI (or a group of NGIs) into the EGI operations structures. We call a “group of NGIs” a structure that contains more than one NGI but which are operated by one single operational structure (support, tickets assignment, etc.). In the rest of the document, both simple NGIs and NGI groups will be referred to using the word “NGI”. If you are an NGI operating inside a group of NGIs, this document is not relevant.

Revision history

Version Authors Date Comments
0.11 Marcin Radecki, Małgorzata Krakowian, David Collados 2010-06-15 Nagios Box validation.
0.10 Marcin Radecki, Małgorzata Krakowian 2010-06-11 Update item 99953 and 99954
0.9 Marcin Radecki, Małgorzata Krakowian 2010-05-19 Update item 99953 and 99954
0.8 Marcin Radecki, Małgorzata Krakowian 2010-05-13 Update item 99953 and 99954 – Configuration NGI in Nagios
0.7 Marcin Radecki, Małgorzata Krakowian 2010-04-27 Update item 99953 and 99954
0.6 Guenter Grein 2010-04-26 Update item 99953
0.5 Marcin Radecki, Małgorzata Krakowian 2010-04-23 Adding step to inform ROC managers about new NGI creation and step which concerns ROD team creation
0.4 Marcin Radecki 2010-04-06 Changes related to NGI nagios box validation (not necessary yet) and renumbering of steps.
0.3 Marcin Radecki 2010-03-05 Proposed changes according to experience with creating NGI_PL
0.2 ROD Pole 3 2010-01-27 Refined procedure taking technical requirements in consideration
0.1 Guenter Grein 2010-01-12 First draft


Political validation

CASE1. If a new NGI is already represented within the EGI Council, the EGI Council should be notified that the NGI is ready for validation. At this point, the technical validation can start.

CASE2. If a new NGI is _not_ represented within the EGI Council, and is willing to be represented there, the NGI needs to submit a request for admission to the Council before being technically validated. After this step, CASE1 applies.

CASE3. if a new NGI is _not_ represented within the EGI Council, it is _not_ interested in being part of it, but still would like to be a consumer of the EGI global services, then a request has to be submitted to the council and a MoU [to be defined] needs to be signed. When the MoU is signed, the technical validation can start.


Technical validation

The NOC managers and COD mailing lists are notified by the NGI manager that the NGI is ready for technical validation.

CASE 1. If the NGI belonged to a EGEE ROC that is still operated in EGI, the NGI is validated by the respective ROC manager.

CASE 2. IF the NGI didn't belong to an EGEE ROC, the COD is responsible of the NGI validation.


How to start integration process for NGI (or NGI group)

For integrating a new NGI the NGI representative should submit a GGUS ticket (https://gus.fzk.de/pages/home.php). The ticket should be assigned to a ROC parent to the NGI or OCC. In order to trigger the actions described in this document the parent ROC will create a child tickets on the responsible partners. Hence the integration process will be as transparent as possible to all parties involved and possibility to get stuck is avoided. The required actions are described in following section of this document.

Requirements for new NGI

  1. NGI should provide in NGI creation GGUs ticket following information:
    1. Management mailing list
    2. NGI manager contact data
    3. NGI security officer contact data
    4. NGI security mailing list
    5. ROD team mailing list
    6. NGI nagios monitoring system details
    7. Mailing list for GGUS tickets if using GGUS directly or an interface for interaction of GGUS with a local ticketing system
  2. Attach to the creation ticket filled the FAQ document for the NGI. The template is provided by GGUS team: https://gus.fzk.de/pages/ggus-docs/DOC/1800_FAQ_for_TEMPLATE.doc
  3. Decide whether to use an own help desk system or GGUS directly. If you want to set up your own system please follow the recommendations available at https://gus.fzk.de/pages/ggus-docs/interfaces/docu_ggus_interfaces.php.
  4. Anyone that should be granted a management role on a new NGI (manager, deputy manager, security officer) should first register a user account in GOCDB. The user registration procedure is described in GOCDB user documentation at http://goc.grid.sinica.edu.tw/gocwiki/GOCDB_User_Documentation, section 3.1.1

NGI creation process steps

Some steps of the process can be done in parallel as they are independent, so all steps starting with the same number can be performed at the same time - several different child tickets created in order to speed up the process. The general idea is that these tickets must be closed before going for next main step.

Validation steps:

1 - Parent ROC/OCC to perform: Verification of the validity of the request by the parent ROC (in case of a country belonging to some ROC)

2 - Parent ROC/OCC to perform: Broadcast of the information that new request was validated


Parent ROC/OCC creating child tickets in the order given as follows:

3 - GOCDB to perform: Creation of a new NGI entry in GOCDB (with no site attached). (Wait until done.)

  • NGI name: NGI_XXX (or NGI_GROUP_XXX)
  • NGI management mailing list: foo@bar.org
  • NGI security mailing list:
  • NGI manager:
  • NGI security officer:

4.1 - CE ROC to perform: Configuration of the new entry in SAMAP

4.2 - CIC Portal to perform: Configuration of the new entry in CIC dashboard

4.3 - GGUS to perform: Creation of a new support unit in GGUS : NGI_XXX

4.4 - COD to perform: Certification of new ROD team – https://wiki.egi.eu/wiki/Procedure_to_handle_new_ROD_certification_GGUS_tickets

5 - The newly created NGI_XXX to perform: Deploy an NGI Nagios instance and include the host in GOCDB as a 'National-Nagios' service. (This step only applies to NGIs running an NGI Nagios instance) (Wait until done.)

6 - Nagios team to perform: Include the NGI level Nagios in the central ops-monitor Nagios instance.

7 - Parent ROC/OCC to perform: Configuration of the NGI in the ROC Nagios instance (Note: only if NGI was part of a ROC)

8 - The newly created NGI_XXX to perform: Final confirmation that the new NGI can start the operations

9 - GOCDB to perform: Transfer of related sites from their ROC to the new NGI structure in GOCDB (Note: if the new NGI was not part of a ROC in EGEE this is not a transfer but a simple insertion)

10 - Newly created NGI_XXX to perform: Transfer all open operational tickets to new NGI in GGUS.

11 - Parent ROC/OCC to perform: Validation process of the new NGI Nagios, as described at the step 5.3 of: https://twiki.cern.ch/twiki/bin/view/EGEE/ValidateROCNagios#Validation_Process (This step only applies if 5 is done)

12 - Nagios team to perform: Validation that sites/NGI shown up correctly in Central DBs

13 - Nagios team to perform: Migrating alerts from ROC to NGI Nagios instance. (This step only applies if 5 is done)

14 - Parent ROC/OCC to perform: Final checks by the parent ROC. (Close a parent ticket.)

15 - Newly created NGI_XXX to perform: final checks and broadcast of the information by NGI officials.