Responsible Unit: NGI_TR

Helpdesk: GGUS (Operations Helpdesk by TPM)

What is the purpose of the NGI_TR Support?

The aim of NGI_TR Operation Centre is to deal with all kind of issues related to operations of grid sites in Turkey. The operational tickets raised with the use of tools like Operations Dashboard as well as users' tickets related to site operations in Turkey should be addressed to NGI_TR Operation Centre. From May 2012 to April 2013 the Turkish NGI accepted to provide temporary operational support to Azerbaijan sites.

For which components does NGI_TR provide support?

NGI_TR Operation Centre is managing many central services for grid infrastructure: top-BDII, LFC, AMGA, FRONTIER, MyProxy, WMS, VOMS and UIs. All of these central services support is given by the Operation Centre.

Which quality of service (QoS) will you provide?


Who will assign tickets to NGI_TR Support?

Ticket handling for NGI_TR is currently done using the GGUS system directly. EGI user communities and EGI bodies (TPM, COD, …) can assign tickets to NGI_TR through GGUS.

Are tickets typically solved in NGI_TR Support or reassigned elsewhere?

Tickets are solved by NGI_TR Operation Centre.

Who is responsible for NGI_TR Support?

NGI_TR Operation Centre is responsible for NGI_TR support.

What documentation is available on NGI_TR Support?

Since, all TR-Grid sites are managed centrally by NGI_TR Operation Centre, there is no operation documentation in a web page. But there are internal documentations in Turkish language for NGI_TR Operation Centre. The support documentations for national users are available at http://wiki.grid.org.tr/ in Turkish. The documentation for operation of NGI_TR Support unit is being created in wiki page for user support.

What is the usual "Type of Issue" for the tickets of NGI_TR?



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 NGI_TR team.