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 "FAQ GGUS-Alarm-Tickets"
| Line 2: | Line 2: | ||
== What is the purpose of alarm tickets? == | == What is the purpose of alarm tickets? == | ||
The purpose of ALARM tickets is to notify | The purpose of ALARM tickets is to notify WLCG Tier-0 and Tier-1 administrators about serious problems of the | ||
site at any time, independent from usual office hours. | site at any time, independent from usual office hours. | ||
| Line 13: | Line 13: | ||
== Which sites are involved in the alarm tickets process? == | == Which sites are involved in the alarm tickets process? == | ||
Only | Only the Tier-0 & Tier-1 sites are involved in the alarm tickets process. | ||
The | The WLCG Tier-0/Tier-1 site names can be used as well as the relevant GOC DB site names. | ||
== Which VOs are participating? == | == Which VOs are participating? == | ||
| Line 24: | Line 24: | ||
== How are alarm tickets being processed? == | == How are alarm tickets being processed? == | ||
Alarm tickets are routed to the NGI/ROC the tier | Alarm tickets are routed to the NGI/ROC the tier site belongs to automatically. They do not | ||
need a routing by the TPM. The NGI/ROC is notified about the ticket in the usual way. | need a routing by the TPM. The NGI/ROC is notified about the ticket in the usual way. | ||
In parallel the | In parallel the site receives an alarm email signed with a GGUS certificate. This alarm email is processed at the Tier-0/Tier-1 and notifies the relevant people at any time. | ||
Detailed information is available in the [[FAQ_GGUS-Alarm-Ticket-Process | GGUS FAQs]]. | Detailed information is available in the [[FAQ_GGUS-Alarm-Ticket-Process | GGUS FAQs]]. | ||
| Line 33: | Line 33: | ||
team email. | team email. | ||
== Where can I find out the contact persons of the VOs and the | == Where can I find out the contact persons of the VOs and the eligible (Tier-0/Tier-1 sites? == | ||
Alarm mail addresses are taken from GOC DB for EGI sites and from OIM for OSG sites. | Alarm mail addresses are taken from GOC DB for EGI sites and from OIM for OSG sites. | ||
VOMS is used by GGUS as the information source for authorised alarmers. | VOMS is used by GGUS as the information source for authorised alarmers. | ||
Revision as of 15:52, 15 June 2015
GGUS wiki / GGUS Documentation
GGUS-Alarm-Tickets
What is the purpose of alarm tickets?
The purpose of ALARM tickets is to notify WLCG Tier-0 and Tier-1 administrators about serious problems of the site at any time, independent from usual office hours.
Who can submit alarm tickets?
Only experts, nominated by the WLCG VOs are allowed to submit alarm tickets. They need to have the appropriate permissions in GGUS user database.
How can alarm tickets be submitted?
Alarm tickets can be submitted using the GGUS web portal.
Which sites are involved in the alarm tickets process?
Only the Tier-0 & Tier-1 sites are involved in the alarm tickets process. The WLCG Tier-0/Tier-1 site names can be used as well as the relevant GOC DB site names.
Which VOs are participating?
Participating VOs are:
- Alice,
- Atlas,
- Cms,
- Lhcb.
How are alarm tickets being processed?
Alarm tickets are routed to the NGI/ROC the tier site belongs to automatically. They do not need a routing by the TPM. The NGI/ROC is notified about the ticket in the usual way. In parallel the site receives an alarm email signed with a GGUS certificate. This alarm email is processed at the Tier-0/Tier-1 and notifies the relevant people at any time. Detailed information is available in the GGUS FAQs.
How do I resolve alarm tickets?
For resolving team tickets please use the GGUS portal. A reference link is provided in the team email.
Where can I find out the contact persons of the VOs and the eligible (Tier-0/Tier-1 sites?
Alarm mail addresses are taken from GOC DB for EGI sites and from OIM for OSG sites.
VOMS is used by GGUS as the information source for authorised alarmers.
Authorised alarmers in the VO are stored in VOMS. To obtain a list of their names/DNs use a
vomrs client following instructions on:
https://twiki.cern.ch/twiki/bin/view/LCG/OperationsAlarmsPage or contact your VO Admin via:
- project-lcg-vo-atlas-admin@cern.ch
- project-lcg-vo-alice-admin@cern.ch
- project-lcg-vo-cms-admin@cern.ch
- project-lcg-vo-lhcb-admin@cern.ch
What documentation is available on team tickets?
- FAQ GGUS-Alarm-Ticket-Process
- File:GGUS Graph ALARM Ticket Process.pdf
- FAQ GGUS-Alarmer-Registration
What if I have questions which are not dealt with by this FAQ?
Please submit a GGUS ticket.