Alert.png 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 "Regionalized GGUS use cases"

From EGIWiki
Jump to navigation Jump to search
(Created page with '{{Template:Op menubar}} ==Current status of regionalization== <!-- Copy the block below to add a use case --> <!-- use case block --> ==Use cases== ===Use case #1=== ====Use …')
 
Line 2: Line 2:
==Current status of regionalization==
==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.




<!-- Copy the block below to add a use case -->
<!-- Copy the block below to add a use case -->
<!-- use case block -->
<!-- use case block -->
==Use cases==
==Use cases==
===Use case #1===
===Use case #1===

Revision as of 12:11, 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.


Use cases

Use case #1

Use case description

Dependencies with other regionalized tools