PROC02 Operations Centre creation
|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||Operations Centre creation|
|Last modified||19 August 2014|
|Policy Group Acronym||OMB|
|Policy Group Name||Operations Management Board|
|Procedure Statement||The purpose of this document is to clearly describe the actions and the relative steps to be undertaken for integrating a Operations Centre into the EGI operational structure.|
The purpose of this document is to clearly describe actions and relative steps to be undertaken for integrating an Operations Centre into the EGI operational structure.
The Integration Process Coordinator (IPC) is the entity responsible for integrating a new Operations Centre within EGI.
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.
First step for validating an Operations Centre is to be politically approved as formed from an official partner of the EGI infrastructure.
After this step, the Operations Centre needs to be technically validated. The Operations team is responsible for performing this validation.
CASE 1. If an Operations Centre is already represented within the EGI Council we recommend that the Operations Centre political representative within the EGI Council notifies the EGI Chief Operations Officer that the respective Operations Centre is entering its validation cycle. At this point, technical validation can start.
CASE 2. If an Operations Centre is not represented within the EGI Council, and it is willing to be represented there, the Operations Centre needs to submit a request for admission to the Council. After the Operations Centre has been accepted by the Council, CASE 1 applies.
CASE 3. If a new Operations Centre is not represented within the EGI Council and is not interested in being part of it, but would still like to be a consumer of the EGI Global Services, then an MoU must be established with EGI. Once an MoU is in place technical validation can start.
- The Operations Centre Operations manager(s) sends an email to the Chief Operations Officer (COO) that the Council was informed about the creation of a new Operations Centre, and (if applicable) also that the Council has approved it. The Operations Centre Operations manager(s) should also indicate the IPC responsible for the validation in the email.
- The Chief Operations Officer opens a GGUS ticket to the IPC to start the validation process.
Start of the integration
- The integration of a new Operations Centre starts when the COO opens an Operations Centre validation ticket to the IPC (via GGUS).
- Once the COO ticket is filed, the IPC can start the validation process. In order to trigger the actions described in this document the IPC creates a set of new child tickets that are assigned to the individual partners that are responsible for the various validation steps. Thereby, the integration process should be as transparent as possible to all parties involved. The required actions are described below.
An example/template for the Operations Centre creation ticket is provided here:
Subject: Creation of <Operations Centre name> Required information for the creation of the Operations Centre: Management mailing list : firstname.lastname@example.org Operations Centre Operations manager contact data : Person Surname (email) +phone contact, Deputy: Person Surname (email) +phone contact, Operations Centre security officer contact data : Person Surname (email) +phone contact, Operations Centre security mailing list : email@example.com ROD team mailing list : firstname.lastname@example.org Operations Centre nagios monitoring system details : https://mon-ngi.xxx.org/nagios Mailing list for GGUS tickets if using GGUS directly : email@example.com The FAQ document for the Operations Centre provided by the GGUS team as described in [[GGUS:FAQ_Responsible_Units]]
Before opening an Operations Centre creation GGUS ticket, the Operations Centre should:
- Make sure your operational organization is able to fulfill RP OLA https://documents.egi.eu/secure/ShowDocument?docid=463
- Decide about the Operations Centre name. In case of national European Operations Centres, the name should start with "NGI_"
- Decide whether to use the Operations Centre's own help desk system or use GGUS directly. If the Operations Centre wants to set up their own system they need to provide an interface for interaction to GGUS with the local ticketing system and follow the recommendations available at https://ggus.eu/pages/ggus-docs/interfaces/docu_ggus_interfaces.php.
- Set the following contact points:
- Management mailing list
- Operations Centre operations manager contact data
- Operations Centre security officer contact data
- Operations Centre security mailing list
- ROD team mailing list (including people responsible for monitoring and supporting the Operations Centre infrastructure)
- Mailing list for GGUS tickets IF GGUS is used directly for the helpdesk system
- All certified Operations Centre sites need to be monitored by ARGO monitoring infrastructure operated centrally by EGI.
- Fill the FAQ document for the Operations Centre. The template is provided by the GGUS team: GGUS:FAQ_Responsible_Units
- Staff in the Operations Centre that should be granted a management role (manager, deputy manager, security officer) should first register a user account in the GOCDB. The user registration procedure is described in the GOCDB user documentation at https://twiki.cern.ch/twiki/bin/view/EMI/Glite-APELInstallation, section 4.1.1
- Staff in Operations Centre is familiar with Operational Procedures
- People who are responsible for operations should be subscribed to following mailing lists (unless differently specified):
- Operations Centre manager:
noc-managers [at] mailman.egi.eu - registration through https://mailman.egi.eu/mailman/listinfo
- ROD team:
All-operator-on-duty [at] mailman.egi.eu - list which integrate all Operations Centres ROD mailing list.
Mailing list is populated automatically from GOCDB. New Operations Centres should make sure to record accurate information in GOCDB.
- Regional Helpdesk administrator:
ggus-if-devs [at] cern.ch - mailing list designed for coordination of changes in the interface
To register please send a request (through for example GGUS system) to GGUS support staff.
- Security staff:
ngi-security-contacts [at] mailman.egi.eu, NGI or OC security officers subscribe to this mailing list
site-security-contacts [at] mailam.egi.eu, Site (only certified site) security officers subscribe to this mailing list
Both mailing lists are populated automatically from GOCDB. New Operations Centres should make sure to record accurate information in GOCDB.
- (Recommended) Site administrators:
LCG-ROLLOUT [at] jiscmail.ac.uk - list gathers all site admins and is designed for technical discussions - membership not mandatory but useful
Subscription is possible through https://www.jiscmail.ac.uk/cgi-bin/webadmin?SUBED1=LCG-ROLLOUT&A=1
- Operations Centre manager:
Some steps of the process can be done in parallel as they are independent, so all steps grouped within the same task number can be performed concurrently (several different child tickets will be created in order to speed up the process). The general idea is that these tickets must be closed before being able to move on to the next step.
|Step||Substep||Action on||Action||Required data||Notes|
||IPC||Verification of the validity of the request (were all needed data provided?)||
||To check is all needed information are provided to make the process quick|
||IPC||Create child tickets in the order given as follows:||
||1||GOCDB|| Creation of a new Operations Centre entry in the (with no site attached).
||To register new OC in official EGI database|
||2||Operations Portal||Enter the new Operations Centre in the Operations dashboard (also add ROD mailing list)||ROD email list||To allow new OC to use operations dashboard which is required to perform grid oversight activity/span>|
||3||GGUS|| Create a new support unit in GGUS
OC should fill in https://wiki.egi.eu/wiki/GGUS:NGI_XXX_FAQ or https://wiki.egi.eu/wiki/GGUS:XXX_FAQ
Instruction how to create GGUS wiki page GGUS:FAQ Responsible Units
|To make possible to ceate tickets in official EGI ticketing system to new OC|
||4||Operations||Certification of new ROD team||
Include in the GGUS ticket for :
|To verify if the future ROD team members are properly trained to perform their duties|
||The newly created Operations Centre||
Confirmation that Operations Centre read, accept and agree to fulfill the RP OLA
||Dteam VO manager|| Create a branch/group in Dteam VO for Operations Centre and assign DN of people who will be dteam VO representative for the Operations Centre, Operations Centre Group owner and Operations Centre Group manager.
Responsibilities and terminology
VO representative: A person that can approve or deny dteam VO membership requests. This person is selected by the applicant during the registration phase.
Group owner: A person that can approve or deny Group membership requests. In addition he can create subgroups within his Group.
Group manager: A person that can approve or deny Group membership requests.
These responsibilities can be assigned to the same person(s).
How to assign the child ticket: assign the ticket to "VO support" after the selection of "dteam" in the concerned VO field
This step is not blocking the process and can be done in parallel. It is required to finish this step before closing parent ticket.
| Following data about each responsible person:
To make possible to register operations staff from new OC to register in Dteam VO.
This VO gather all operations staff and allow them to access the grid.
||The newly created Operations Centre||Final confirmation that the new Operations Centre can start the operations||
||The confirmation means that OC will provide all services required in OLA|
GOCDB transfers related sites from the source ROC to the new Operations Centre structure.
||The sites moving across to the new OC in the ticket indicated in the ticket.|
|The newly created Operations Centre||
Newly created Operations Centre should insert at least one sites
||Nagios system need at least one site to be validated.|
||The newly created Operations Centre||
[If the Operations Centre was part of a OC] Transfer all open operational tickets to the new Operations Centre in GGUS.
||To ensure that non of the GGUS tickets were forgotten durign the process.|
||The newly created Operations Centre||Check that all the sites are visible in ARGO and that alarms show up in Operations portal||
||OPTIONAL||The newly created Operations Centre|| All sites should configured GIIS according to the instructions at:
GlueSiteOtherInfo: EGI_NGI=<Operations Centre name> GlueSiteOtherInfo: GRID=EGI
This step can be performed at any time from this point.
||To confirm that all sites publish proper data in information system about new NGI.|
||The newly created Operations Centre||
[If the Operations Centre was part of a OC]
Inform managers of regional VOs to change the VO scope of their VOs to the relevant Operations Centre (national). This action require only confirmation from Operations Centre manager that information was passed.
Information which should be pass to VO managers: "The Vo scope can be changes by creating a ticket to Operations portal SU in GGUS."
||To spread among Vo information|
||The newly created Operations Centre|| NGI_XX_SERVICES service group / XX_SERVICES service group
The newly created Operations Centre should create in GOC DB NGI_XX_SERVICES (if national entity) or XX_SERVICES (if international entity) service group and attached services listed on page: NGI services in GOCDB
||The newly created Operations Centre||Create a GGUS ticket to "Operations" SU with information about newly created service group and official OC Top-BDII, SAM, Argus instance. Ask to add OC manager to OC managers mailing list.||
||IPC||Final checks by the IPC.||
Were all steps taken and finished properly?
Final checks should be verified.
The information that the Operations Centre is ready should be sent in Monthly broadcast and announced during OMB by EGI Operations team.
(This broadcast should be sent to VO managers (except Ops and Dteam VO) and NOC/ROC managers)
See the template below for an indication of the message content.
Subject: <Operations Centre name> is operational Dear All, We would like to announce that <Operations Centre name> is now fully operational and that we have finished its integration procedure. All necessary operational teams and tools are established in our Operations Centre and we are ready for production. This Operations Centre is visible in all operational tools as <Operations Centre name> and is responsible for all <COUNTRY> sites. Best regards,
|2.11||Alessandro Paolini||2016-12-16||The monitoring is operated centrally, no more need of regional nagios servers. Procedure modified accordingly.|
|2.10||Alessandro Paolini||2016-06-08||made distinction between NGI (national entity) and Operations Centre (international entity, it could include also more NGIs). To check how to modify the step 14. To check how to modify the related wiki in step 16 (https://wiki.egi.eu/wiki/NGI_services_in_GOCDB).|
|2.09||Alessandro Paolini||2016-06-07||"EGI Operations Support" was decommissioned, changed all the references to "Operations"|
|2.08||Malgorzata Krakowian||2014-10-06||step 17 - providing information to Operations about NGI core services|
|| Malgorzata Krakowian
|| Reordered to have all Nagios related steps as close as possible. Added new column with explanation why the step should be taken.|
|2.06||Malgorzata Krakowian||2011-11-02||Step for RP OLA acceptance added; New point to prerequisites about RP OLA added|
|2.05||Malgorzata Krakowian||2011-09-28||Cleaning; GGUS require wiki page not a faq document etc.|
|2.04||Malgorzata Krakowian||2011-04-1||Step concerning SAMAP tool was removed due to tool decommission|
|2.03||Gonçalo Borges||2011-03-31||Operations Centre creation process visualization|
|2.02||T. Ferrari||2011-03-17||Assignment of procedure number, update of title "Operations Centre creation coordination procedure" to "Operations Centre Creation", small editorial improvements|
|2.02||Małgorzata Krakowian||2011-01-27||Name change from NGI to Operations Centre|
|2.01||Dimitris Zilaskos||2010-12-06||Clarification concerning dteam VO branch creation step|
|2.00||Małgorzata Krakowian, M. Radecki||2010-10-26||Approved by OMB|
|M. Krakowian||19 August 2014||Change contact group -> Operations support|