Difference between revisions of "WI01 ROD certification ticket handling"

From EGIWiki
Jump to: navigation, search
Line 22: Line 22:
 
  e-mail should confirm the following:
 
  e-mail should confirm the following:
 
   
 
   
  a) she/he represents the XXX ROD team (this can be done by any member
+
  a) she/he represents the XXX ROD team (this can be done by any member of the ROD team)
of the ROD team)
+
  b) that the ROD team knows the duties and is familiar with EGI Operational Procedures, in particular the ROD part:
  b) that the ROD team knows the duties and is familiar with EGI Operational  
 
Procedures, in particular the ROD part:
 
 
     https://documents.egi.eu/public/ShowDocument?docid=15
 
     https://documents.egi.eu/public/ShowDocument?docid=15
 
  (Note: there is also a version currently available at
 
  (Note: there is also a version currently available at
Line 31: Line 29:
 
  EGEE-III-SA1-840932-OperationalProceduresforROD-v2.0)
 
  EGEE-III-SA1-840932-OperationalProceduresforROD-v2.0)
 
   
 
   
  Once you have confirmed the above, the XXX ROD e-mail address will be added
+
  Once you have confirmed the above, the XXX ROD e-mail address will be added to the EGI Operational Documentation and subscribed to the
to the EGI Operational Documentation and subscribed to the
 
 
     all-operator-on-duty@mailman.egi.eu
 
     all-operator-on-duty@mailman.egi.eu
  mailing list, which is an official communication channel for all certified
+
  mailing list, which is an official communication channel for all certified ROD teams.
ROD teams.
 
 
   
 
   
 
  On behalf of Operations and e-Infrastructure Oversight
 
  On behalf of Operations and e-Infrastructure Oversight
  andthe Central Operator on Duty (COD),
+
  and the Central Operator on Duty (COD),
 
  XXX XXX
 
  XXX XXX

Revision as of 08:11, 7 May 2010

  1. Get the e-mail address (mailing list) for the new ROD from the parent ticket. If it is not on the parent ticket then re-assign the ticket to the parent ROC asking them to complete the data.
  2. Set "operational-documentation-ngi-manuals@egi.eu" as involved in the ticket. This is an instruction for OD management to include the RODmailing list in the documentation.
  3. Send an e-mail to the new ROD highlighting the following:
    1. That this is the new ROD team certification procedure
    2. That they should confirm they are aware of their duties as described in the Operations Manual - ROD section
    3. Inform them that their e-mail address will be subscribed to the all-operator-on-duty mailing list
  4. Set the e-mail "reply-to" to manager-central-operator-on-duty@mailman.egi.eu
  5. Wait for the reply and Copy-paste the reply to the GGUS ticket (do not wait for the new ROD SU in GGUS to be created - wastes time)
  6. Register the new ROD team to the all-operator-on-duty mailing list
  7. Wait for confirmation from Vera (if not already in the ticket)
  8. OD: put an acknowledgement that you'll update the Ops. Man. in the ticket.
  9. Close the GGUS ticket

Below is an e-mail template which should be sent from COD to ROD:


Dear XXX ROD team,

Your XXX NGI is currently being established and one of the steps is
the certification of the new Regional Operator on Duty (ROD) team.
In order to get your ROD team certified the person replying to this
e-mail should confirm the following:

a) she/he represents the XXX ROD team (this can be done by any member of the ROD team)
b) that the ROD team knows the duties and is familiar with EGI Operational Procedures, in particular the ROD part:
    https://documents.egi.eu/public/ShowDocument?docid=15
(Note: there is also a version currently available at
    https://edms.cern.ch/document/840932
EGEE-III-SA1-840932-OperationalProceduresforROD-v2.0)

Once you have confirmed the above, the XXX ROD e-mail address will be added to the EGI Operational Documentation and subscribed to the
    all-operator-on-duty@mailman.egi.eu
mailing list, which is an official communication channel for all certified ROD teams.

On behalf of Operations and e-Infrastructure Oversight
and the Central Operator on Duty (COD),
XXX XXX