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 "WI01 ROD certification ticket handling"

From EGIWiki
Jump to navigation Jump to search
(Created page with ' 1. Get e-mail address to new ROD from Parent ticket if not there then re-assign the ticket to parent ROC asking for completing the data... 2. Set operational-documentation-ngi…')
 
Line 1: Line 1:
  1. Get e-mail address to new ROD from Parent ticket if not there then re-assign the ticket to parent ROC asking for completing the data...
  * Get e-mail address to new ROD from Parent ticket if not there then re-assign the ticket to parent ROC asking for completing the data...


  2. Set operational-documentation-ngi-manuals@egi.eu as involved in the ticket (this is for Vera)
  * Set operational-documentation-ngi-manuals@egi.eu as involved in the ticket


  3. Send an e-mail to new ROD highlighting the following:
  * Send an e-mail to new ROD highlighting the following:
a) this is new ROD team certification procedure ;-)
    * this is new ROD team certification procedure
b) they should confirm they are aware of their duties which are described in Operations Manual - ROD section (link)
    * they should confirm they are aware of their duties which are described in Operations Manual - ROD section (link)
c) inform their e-mail address will be subscribed to all-operator-on-duty mailing list
    * inform their e-mail address will be subscribed to all-operator-on-duty mailing list


Set the e-mail "reply-to" to manager-central-operator-on-duty@mailman.egi.eu
* Set the e-mail "reply-to" to manager-central-operator-on-duty@mailman.egi.eu


4. Wait for reply and Copy-paste reply to GGUS ticket (do not wait for new ROD SU in GGUS - wasting time)
* Wait for reply and Copy-paste reply to GGUS ticket (do not wait for new ROD SU in GGUS - wasting time)


5. Register new ROD team to all-operator-on-duty mailing list (give more people rights to manage the mailing list - e.g. Malgorzata, Ron?, Luuk?)
* Register new ROD team to all-operator-on-duty mailing list


6. Wait for confirmation from Vera (if not already in the ticket)
* Wait for confirmation from Vera (if not already in the ticket)
Vera: is putting an acknowledgement that you'll update Ops. Man. in ticket OK for you?
Vera: is putting an acknowledgement that you'll update Ops. Man. in ticket OK for you?


7. Close the GGUS ticket
* Close the GGUS ticket

Revision as of 15:48, 6 May 2010

* Get e-mail address to new ROD from Parent ticket if not there then re-assign the ticket to parent ROC asking for completing the data...
* Set operational-documentation-ngi-manuals@egi.eu as involved in the ticket
* Send an e-mail to new ROD highlighting the following:
   * this is new ROD team certification procedure
   * they should confirm they are aware of their duties which are described in Operations Manual - ROD section (link)
   * inform their e-mail address will be subscribed to all-operator-on-duty mailing list
* Set the e-mail "reply-to" to manager-central-operator-on-duty@mailman.egi.eu
* Wait for reply and Copy-paste reply to GGUS ticket (do not wait for new ROD SU in GGUS - wasting time)
* Register new ROD team to all-operator-on-duty mailing list
* Wait for confirmation from Vera (if not already in the ticket)

Vera: is putting an acknowledgement that you'll update Ops. Man. in ticket OK for you?

* Close the GGUS ticket