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: | ||
# Get e-mail address | # 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. | ||
# Set operational-documentation-ngi-manuals@egi.eu as involved in the ticket. This is for OD management. | # 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. | ||
# Send an e-mail to new ROD highlighting the following: | # Send an e-mail to the new ROD highlighting the following: | ||
## this is new ROD team certification procedure | ## That this is the new ROD team certification procedure | ||
## they should confirm they are aware of their duties | ## That they should confirm they are aware of their duties as described in the Operations Manual - ROD section | ||
## | ## Inform them that their e-mail address will be subscribed to the 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 | ||
# Wait for reply and Copy-paste reply to GGUS ticket (do not wait for new ROD SU in GGUS - | # 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) | ||
# Register new ROD team to all-operator-on-duty mailing list | # Register the new ROD team to the all-operator-on-duty mailing list | ||
# Wait for confirmation from Vera (if not already in the ticket) | # Wait for confirmation from Vera (if not already in the ticket) | ||
# OD: put an acknowledgement that you'll update Ops. Man. in ticket. | # OD: put an acknowledgement that you'll update the Ops. Man. in the ticket. | ||
# Close the GGUS ticket | # Close the GGUS ticket | ||
Revision as of 08:00, 7 May 2010
- 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.
- 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.
- Send an e-mail to the new ROD highlighting the following:
- That this is the new ROD team certification procedure
- That they should confirm they are aware of their duties as described in the Operations Manual - ROD section
- Inform them that their e-mail address will be subscribed to the all-operator-on-duty mailing list
- Set the e-mail "reply-to" to manager-central-operator-on-duty@mailman.egi.eu
- 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)
- Register the new ROD team to the all-operator-on-duty mailing list
- Wait for confirmation from Vera (if not already in the ticket)
- OD: put an acknowledgement that you'll update the Ops. Man. in the ticket.
- 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
andthe Central Operator on Duty (COD),
XXX XXX