Difference between revisions of "WI02 Operations centre creation"

From EGIWiki
Jump to: navigation, search
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" 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>&lt;span lang="en" class="short_text" /&gt;<br>  
+
#&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>&lt;span lang="en" class="short_text" /&gt;<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>
Line 92: Line 92:
  
 
Please create branch for NGI_XX
 
Please create branch for NGI_XX
This ticket was created according to procedures: [[Image:]][[../../../../../wiki/PROC02|https://wiki.egi.eu/wiki/PROC02]] in order to track process.
+
This ticket was created according to procedures: https://wiki.egi.eu/wiki/PROC02 in order to track process.
 
The related master ticket is XXXX.
 
The related master ticket is XXXX.
  
Line 116: Line 116:
 
Could you please include your Nagios instance host in GOC&nbsp;DB as 'National-Nagios' service?
 
Could you please include your Nagios instance host in GOC&nbsp;DB as 'National-Nagios' service?
  
This ticket was created according to procedures: [[Image:]][[../../../../../wiki/PROC02|https://wiki.egi.eu/wiki/PROC02]] in order to track process.
+
This ticket was created according to procedures: https://wiki.egi.eu/wiki/PROC02 in order to track process.
 
The related master ticket is XXX.</pre>
 
The related master ticket is XXX.</pre>
 
|-
 
|-
Line 132: Line 132:
 
Could you please configure your Nagios instance so that it will test also sites from NGI_XXXX??
 
Could you please configure your Nagios instance so that it will test also sites from NGI_XXXX??
  
This ticket was created according to procedures: [[Image:]][[../../../../../wiki/PROC02|https://wiki.egi.eu/wiki/PROC02]] in order to track process.
+
This ticket was created according to procedures: https://wiki.egi.eu/wiki/PROC02 in order to track process.
 
The related master ticket is XXX.</pre>
 
The related master ticket is XXX.</pre>
 
|-
 
|-
Line 146: Line 146:
 
Could you please confirm you are ready to take responsibility for your sites and start operations??  
 
Could you please confirm you are ready to take responsibility for your sites and start operations??  
  
This ticket was created according to procedures: [[Image:]][[../../../../../wiki/PROC02|https://wiki.egi.eu/wiki/PROC02]] in order to track process.
+
This ticket was created according to procedures: https://wiki.egi.eu/wiki/PROC02 in order to track process.
 
The related master ticket is XXX.</pre>
 
The related master ticket is XXX.</pre>
 
|-
 
|-

Revision as of 12:28, 16 August 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 lang="en" class="short_text" />
  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.



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 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/PROC02 in 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.

Subject: NGI creation child ticket for Dteam: NGI_XX

Dear Dteam Vo manager,

Please create branch 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.

Dteam VO representative for NGI_XX will be

Operations Centre Group owner:

Operations Centre Group manager:

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)

Subject: NGI creation child ticket for NGI_XX: NGI_XX

Dear NGI_XXX,

Could you please include your Nagios instance host in GOC DB as 'National-Nagios' service?

This ticket was created according to procedures: https://wiki.egi.eu/wiki/PROC02 in order to track process.
The related master ticket is XXX.
5
[If the Operations Centre was part of a ROC]

IPC

Configure the Operations Centre in the ROC Nagios instance

Subject: NGI creation child ticket for ROC_XX: NGI_XXX

Dear ROC_XXX,

Could you please configure your Nagios instance so that it will test also sites from NGI_XXXX??

This ticket was created according to procedures: https://wiki.egi.eu/wiki/PROC02 in order to track process.
The related master ticket is XXX.
6
The newly created Operations Centre

Final confirmation that the new Operations Centre can start the operations

Subject: NGI creation child ticket for NGI_XX: NGI_XX

Dear NGI_XXX,

Could you please confirm you are ready to take responsibility for your sites and start operations?? 

This ticket was created according to procedures: https://wiki.egi.eu/wiki/PROC02 in order to track process.
The related master ticket is XXX.
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,