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 "NGI GRNET:RT GGUS Integration"
Jump to navigation
Jump to search
| (5 intermediate revisions by 2 users not shown) | |||
| Line 1: | Line 1: | ||
[[Category:NGI]] | |||
'''INTERFACE DECOMMISSIONED''' | |||
<!-- | |||
=== Scope === | === Scope === | ||
| Line 5: | Line 9: | ||
There are three possible scenarios implemented: | There are three possible scenarios implemented: | ||
* Scenario 1: A ticket is created at the GGUS, where the ticket submitter or the TPM on duty team assigns the ticket at the NGI_GRNET support unit, using the “Assign to ROC/NGI” field of the “Submit ticket” form of the GGUS. In this scenario, a corresponding ticket must be created at the appropriate queue of the HellasGrid RT. | * '''Scenario 1''': A ticket is created at the GGUS, where the ticket submitter or the TPM on duty team assigns the ticket at the NGI_GRNET support unit, using the “Assign to ROC/NGI” field of the “Submit ticket” form of the GGUS. In this scenario, a corresponding ticket must be created at the appropriate queue of the HellasGrid RT. | ||
* Scenario 2: A ticket is created at the GGUS, where the ticket submitter or the TPM on duty team assigns the ticket at a site in the scope of the NGI_GRNET, using the “Notify SITE” field of the “Submit ticket” form of the GGUS. In this scenario, a corresponding ticket must be created at the appropriate queue of the HellasGrid RT. | * '''Scenario 2''': A ticket is created at the GGUS, where the ticket submitter or the TPM on duty team assigns the ticket at a site in the scope of the NGI_GRNET, using the “Notify SITE” field of the “Submit ticket” form of the GGUS. In this scenario, a corresponding ticket must be created at the appropriate queue of the HellasGrid RT. | ||
* Scenario 3: A ticket is created at the HellasGrid RT, where the ticket submitter assigns the ticket at the GGUS support unit. In this scenario, a corresponding ticket must be created at the GGUS. | * '''Scenario 3''': A ticket is created at the HellasGrid RT, where the ticket submitter assigns the ticket at the GGUS support unit. In this scenario, a corresponding ticket must be created at the GGUS. | ||
At all the scenarios, when a ticket is resolved/re-opened at the HellasGrid RT (GGUS) then the corresponding ticket must been by resolved/re-opened at the GGUS (HellasGrid RT) system. | At all the scenarios, when a ticket is resolved/re-opened at the HellasGrid RT (GGUS) then the corresponding ticket must been by resolved/re-opened at the GGUS (HellasGrid RT) system. | ||
| Line 36: | Line 40: | ||
The wsdl file which completely describes the provisioned web services is located at the url http://rt-ws.hellasgrid.gr/rt.wsdl. The web services are also listen to this hostname. Also, the rt-ws.hellasgrid.gr is alias to rt.hellasgrid.gr. It was chosen a different hostname, in order to restrict the web services to be called only by the IP address of the GGUS system. | The wsdl file which completely describes the provisioned web services is located at the url http://rt-ws.hellasgrid.gr/rt.wsdl. The web services are also listen to this hostname. Also, the rt-ws.hellasgrid.gr is alias to rt.hellasgrid.gr. It was chosen a different hostname, in order to restrict the web services to be called only by the IP address of the GGUS system. | ||
--> | |||
Latest revision as of 16:36, 25 March 2019
INTERFACE DECOMMISSIONED