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 "WI02 Operations centre creation"

From EGIWiki
Jump to navigation Jump to search
(Created page with '= Internal procedure for COD = This page describes steps which should be taken by COD shifter to follow Operations Centre creation procedure. <br> When GGUS ticket is assigne…')
 
Line 5: Line 5:
<br> When GGUS ticket is assigned to COD:  
<br> When GGUS ticket is assigned to COD:  


#&nbsp;Check if all the required information were provided: https://wiki.egi.eu/wiki/PROC02#Start_of_the_integration <span lang="en" class="short_text" id="result_box"><span class="hps" title="Kliknij, aby wyświetlić alternatywne tłumaczenia">If not</span><span title="Kliknij, aby wyświetlić alternatywne tłumaczenia">, ask </span>new OC <span class="hps" title="Kliknij, aby wyświetlić alternatywne tłumaczenia">to supplement the</span> <span class="hps" title="Kliknij, aby wyświetlić alternatywne tłumaczenia">data.</span></span><span lang="en" class="short_text"><span class="hps" title="Kliknij, aby wyświetlić alternatywne tłumaczenia" /></span><br>
#&nbsp;Check if all the required information were provided: https://wiki.egi.eu/wiki/PROC02#Start_of_the_integration <span lang="en" id="result_box" class="short_text"><span title="Kliknij, aby wyświetlić alternatywne tłumaczenia" class="hps">If not</span><span title="Kliknij, aby wyświetlić alternatywne tłumaczenia">, ask </span>new OC <span title="Kliknij, aby wyświetlić alternatywne tłumaczenia" class="hps">to supplement the</span> <span title="Kliknij, aby wyświetlić alternatywne tłumaczenia" class="hps">data.</span></span><span lang="en" class="short_text">&lt;span class="hps" title="Kliknij, aby wyświetlić alternatywne tłumaczenia" /&gt;</span><br>  
#If all information are provided create tickets according following steps as new ti. Add tickets should be assign as child tickets to the parent one.<br>
#If all information are provided create tickets according following steps as new ti. Add tickets should be assign as child tickets to the parent one.<br>  
#'''Do not split parent ticket to create new tickets.''' It is important to keep everyting clear. Child tickets should have proper content and it should be clear from parent ticket which step when was taken.<br>
#'''Do not split parent ticket to create new tickets.''' It is important to keep everyting clear. Child tickets should have proper content and it should be clear from parent ticket which step when was taken.<br>


<span lang="en" class="short_text"><span class="hps" title="Kliknij, aby wyświetlić alternatywne tłumaczenia" /></span><br>
<span lang="en" class="short_text">&lt;span class="hps" title="Kliknij, aby wyświetlić alternatywne tłumaczenia" /&gt;</span><br>  


<br>
<br>  


{| cellspacing="0" cellpadding="4" border="1" align="left"
{| cellspacing="0" cellpadding="4" border="1" align="left"
Line 24: Line 24:
| IPC  
| IPC  
|  
|  
Put an information that request was validated:<br>
Put an information that request was validated:<br>  
<pre>The request was validated and the creation procedure will start.  
<pre>The request was validated and the creation procedure will start.  
</pre>
</pre>
Line 61: Line 61:
| 3  
| 3  
| GGUS  
| GGUS  
| Create a new support unit in [[GGUS]]&nbsp;: &lt;Operations Centre name&gt;
|  
NOTE: ''(attach the FAQ document for the Operations Centre to this ticket.)''
Create a new support unit in [[GGUS]]&nbsp;: <br>
<pre>Subject: NGI creation child ticket for GGUS: NGI_XXX
 
Please create entries in GGUS for NGI_XXX. This ticket was created according to procedures: https://wiki.egi.eu/wiki/PROC02[https://edms.cern.ch/document/1071800/1 ]in order to track process.
The related master ticket is XXXX.</pre>
NOTE: ''(attach the FAQ document for the Operations Centre to this ticket.)<br>


|-
|-
Line 68: Line 73:
| 4  
| 4  
| COD  
| COD  
| Certification of new ROD team –  
| Certification of new ROD team – <pre>Subject: NGI creation child ticket for COD: NGI_XXX
[[Grid operations oversight/WI01|Procedure_to_handle_new_ROD_certification_GGUS_tickets]]
 
Include in the GGUS ticket for Operational Documentation:  
 
*Country
*Operations Centre acronym
*ROD email list


Please certify NGI_XXX ROD team (ROD&nbsp;mailing list). This ticket was created according to procedures: https://wiki.egi.eu/wiki/PROC02in order to track process.
The related master ticket is XXXX.
</pre>
|-
|-
| 3  
| 3  

Revision as of 10:01, 20 July 2011

Internal procedure for COD

This page describes steps which should be taken by COD shifter to follow Operations Centre creation procedure.


When GGUS ticket is assigned to COD:

  1.  Check if all the required information were provided: https://wiki.egi.eu/wiki/PROC02#Start_of_the_integration If not, ask new OC to supplement the data.<span class="hps" title="Kliknij, aby wyświetlić alternatywne tłumaczenia" />
  2. If all information are provided create tickets according following steps as new ti. Add tickets should be assign as child tickets to the parent one.
  3. Do not split parent ticket to create new tickets. It is important to keep everyting clear. Child tickets should have proper content and it should be clear from parent ticket which step when was taken.

<span class="hps" title="Kliknij, aby wyświetlić alternatywne tłumaczenia" />


Step Substep Action on Action
1
IPC

Put an information that request was validated:

The request was validated and the creation procedure will start. 
2
IPC Create child tickets in the order given as follows:

1 GOCDB Creation of a new Operations Centre entry in the GOCDB (with no site attached).

Include the following into the GOCDB ticket:

subject: NGI creation child ticket for GOCDB: NGI_XX

Please create entries in GOCDB for NGI_XX. This ticket was created according to procedures: https://wiki.egi.eu/wiki/PROC02 in order to track process. 
The related master ticket is XXXX. 	

Operations Centre name: <Operations Centre name>

Operations Centre management mailing list: foo@bar.org

Operations Centre security mailing list:

Operations Centre Operations manager:

Operations Centre security officer: 

2 Operations Portal Enter the new Operations Centre in the Operations dashboard (also add ROD mailing list)

3 GGUS

Create a new support unit in GGUS :

Subject: NGI creation child ticket for GGUS: NGI_XXX

Please create entries in GGUS for NGI_XXX. This ticket was created according to procedures: https://wiki.egi.eu/wiki/PROC02[https://edms.cern.ch/document/1071800/1 ]in order to track process.
The related master ticket is XXXX.

NOTE: (attach the FAQ document for the Operations Centre to this ticket.)


4 COD Certification of new ROD team –
Subject: NGI creation child ticket for COD: NGI_XXX

Please certify NGI_XXX ROD team (ROD mailing list). This ticket was created according to procedures: https://wiki.egi.eu/wiki/PROC02in order to track process.
The related master ticket is XXXX.
3
Dteam VO manager Create a branch/group 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.


Following data about each responsible person:

  • Name and Surname
  • DN
  • email

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.

4
The newly created Operations Centre Include the NAGIOS host in the GOCDB as a 'National-Nagios' service.

(This step only applies to Operations Centres running an Operations Centre Nagios instance)

5
[If the Operations Centre was part of a ROC]

IPC

Configure the Operations Centre in the ROC Nagios instance
6
The newly created Operations Centre Final confirmation that the new Operations Centre can start the operations
7
GOCDB
  • [If the Operations Centre was part of a ROC]

GOCDB transfers related sites from the source ROC to the new Operations Centre structure.

NOTE: please indicate the sites moving across to the new NGI in the ticket.

The newly created Operations Centre
  • [If the Operations Centre wasn't part of a ROC]

Newly created Operations Centre can insert new sites

8
The newly created Operations Centre Inform managers of regional VOs to change the VO scope of their VOs from ROC (regional) 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 CIC portal SU in GGUS."

9 OPTIONAL The newly created Operations Centre All sites should be reconfigured according to the instructions at:

https://wiki.egi.eu/wiki/MAN1_How_to_publish_Site_Information

change the old information from:

 GlueSiteOtherInfo: EGEE_ROC=XXX
 GlueSiteOtherInfo: GRID=EGEE

to:

 GlueSiteOtherInfo: EGI_NGI=<Operations Centre name>
 GlueSiteOtherInfo: GRID=EGI

This step can be performed at any time from this point.

10
The newly created Operations Centre Transfer all open operational tickets to the new Operations Centre in GGUS.
11
Nagios team Include the Operations Centre level Nagios in the central ops-monitor Nagios instance.

(This step only applies to Operations Centres running an Operations Centre Nagios instance)

12
IPC Validation process of the new Operations Centre Nagios, as described at the step 5.3 of:

https://twiki.cern.ch/twiki/bin/view/EGEE/ValidateROCNagios#Validation_Process.

(This step only applies to Operations Centres running an Operations Centre Nagios instance)

13
Nagios team Validation that sites/Operations Centre shown up correctly in Central DBs
14
[If the Operations Centre was part of a ROC]

Nagios team

Migrating alerts from ROC to Operations Centre Nagios instance.

(This step only applies to Operations Centres running an Operations Centre Nagios instance)

15
IPC Final checks by the IPC.

(Were all steps taken and finished properly? Close the parent ticket.)

16
The newly created Operations Centre Final checks should be verified and then the information that the Operations Centre is ready is broadcast by Operations Centre officials.

(This broadcast should be sent to VO managers 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,