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.
PROC02 Operations Centre creation
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 |
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. *******The child tickets should be created in the order given.
Requirements for new NGI
- NGI should provide in NGI creation GGUs ticket following information:
- Management mailing list
- NGI manager contact data
- NGI security officer contact data
- NGI security mailing list
- ROD team mailing list
- NGI nagios monitoring system details
- Mailing list for GGUS tickets if using GGUS directly or an interface for interaction of GGUS with a local ticketing system
- 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
- 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.
- 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