Difference between revisions of "Regionalized GGUS use cases"
Jump to navigation
Jump to search
Line 3: | Line 3: | ||
The regionalized implementation of GGUS is xGUS. xGUS currently is a ''custom service'' hosted ''centrally''. In xGUS the tickets can have a local or global scope, all answers to a global ticket are redirected to the central GGUS. | The regionalized implementation of GGUS is xGUS. xGUS currently is a ''custom service'' hosted ''centrally''. In xGUS the tickets can have a local or global scope, all answers to a global ticket are redirected to the central GGUS. | ||
Some NGIs are using ''RT'' as local ticketing system. There is a ''RT interface'' task force, and an interface for tickets synchronization GGUS <-> RT is currently used. | Some NGIs are using ''RT'' as local ticketing system. There is a ''RT interface'' task force, and an interface for tickets synchronization GGUS <-> RT is currently used. | ||
Revision as of 12:12, 17 March 2011
Main | EGI.eu operations services | Support | Documentation | Tools | Activities | Performance | Technology | Catch-all Services | Resource Allocation | Security |
Current status of regionalization
The regionalized implementation of GGUS is xGUS. xGUS currently is a custom service hosted centrally. In xGUS the tickets can have a local or global scope, all answers to a global ticket are redirected to the central GGUS.
Some NGIs are using RT as local ticketing system. There is a RT interface task force, and an interface for tickets synchronization GGUS <-> RT is currently used.