Difference between revisions of "GGUS:Catch-All Services FAQ"
Jump to navigation
Jump to search
Line 12: | Line 12: | ||
|assigned by= A ticket is usually assigned to the EGI Catch-all Services SU by TPM. | |assigned by= A ticket is usually assigned to the EGI Catch-all Services SU by TPM. | ||
|documentation= | |documentation= | ||
|sortname= | |sortname=Catchallservices | ||
}} | }} |
Latest revision as of 14:20, 29 November 2019
GGUS wiki / GGUS FAQ / GGUS Documentation / GGUS Helpdesk
FAQ FOR Catch-All Services SUPPORT UNIT
- Responsible Unit
- Catch-All Services
- Helpdesk
- GGUS (Operations Helpdesk by TPM)
What is the purpose of the Catch-All Services Support?
To support the EGI Catch-all Services
For which components does Catch-All Services provide support?
The EGI Catch-all Services SU will deal with problems concerning these issues:
- EGI Catch All CA;
- DTEAM VO;
- VO Services for testing and production activities of new VOs
Which quality of service (QoS) will you provide?
Basic
Who will assign tickets to Catch-All Services Support?
A ticket is usually assigned to the EGI Catch-all Services SU by TPM.
Are tickets typically solved in Catch-All Services Support or reassigned elsewhere?
The EGI Catch-all Services supporters either resolve the matter and solve the ticket or they assign the ticket to another support unit.
Who is responsible for Catch-All Services Support?
Members of the EGI Catch-all Support team
What documentation is available on Catch-All Services Support?
What is the usual "Type of Issue" for the tickets of Catch-All Services?
Other
Comments
No comments.
What if I have questions which are not dealt with by this FAQ?
Open a GGUS ticket indicating that it should be directed at the Catch-All Services team.
Search
- Please use this link to search inside the GGUS FAQ