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"
Jump to navigation
Jump to search
| Line 1: | Line 1: | ||
Steps: | |||
{| border="1" cellspacing="0" cellpadding="5" align="center" | |||
! Step | |||
! Action | |||
|-v | |||
| 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-manuals@mailman.egi.eu" as involved''' in the ticket. OD management should include the ROD mailing list in the documentation. | |||
|- | |||
| 3 | |||
| '''Send an e-mail to the new ROD''' | |||
* Set the e-mail '''"CC and reply-to" to central-operator-on-duty@mailman.egi.eu''' | |||
<pre> | |||
Subject: XXX ROD team certification | |||
Dear XXX ROD team, | Dear XXX ROD team, | ||
| Line 34: | Line 36: | ||
and the Central Operator on Duty (COD), | and the Central Operator on Duty (COD), | ||
XXX XXX | XXX XXX | ||
</pre> | |||
Put an information into the ticket that mail was send. | |||
|- | |||
| 4 | |||
| '''When reply received Copy-paste the reply''' to the GGUS ticket | |||
|- | |||
| 5 | |||
| '''Register''' the new ROD team '''to the all-operator-on-duty mailing list''' https://mailman.egi.eu/mailman/admin/all-operator-on-duty | |||
Put an information into the ticket that ROD mailing list was ad to all-operators maillig list. | |||
|- | |||
| 6 | |||
| '''Wait for confirmation from OD''' (if not already in the ticket) | |||
If there is no replay from OD put information that the ticket is waiting for an action from OD team. | |||
|- | |||
| 7 | |||
| If all steps completed: '''Close''' the GGUS ticket | |||
|- | |||
|} | |||
Revision as of 16:44, 6 December 2010
Steps:
| Step | Action |
|---|---|
| 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-manuals@mailman.egi.eu" as involved in the ticket. OD management should include the ROD mailing list in the documentation. |
| 3 | Send an e-mail to the new ROD
Subject: XXX ROD team certification
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
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
Put an information into the ticket that mail was send. |
| 4 | When reply received Copy-paste the reply to the GGUS ticket |
| 5 | Register the new ROD team to the all-operator-on-duty mailing list https://mailman.egi.eu/mailman/admin/all-operator-on-duty
Put an information into the ticket that ROD mailing list was ad to all-operators maillig list. |
| 6 | Wait for confirmation from OD (if not already in the ticket)
If there is no replay from OD put information that the ticket is waiting for an action from OD team. |
| 7 | If all steps completed: Close the GGUS ticket |