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 "NGI GRNET:RT GGUS Integration"

From EGIWiki
Jump to navigation Jump to search
(Created page with '=== Scope === The main scope of this task is the implementation of the automatic communication between the GGUS and HellasGrid Request Tracker (RT) systems via the exchange of …')
 
 
(6 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 15: Line 19:
For the needs of the implementation the following queues was implemented at the HellasGrid RT:
For the needs of the implementation the following queues was implemented at the HellasGrid RT:


    * A queue with name NGI_GRNET. For every ticket assigned to the NGI_GRNET support unit at the GGUS, a new ticket is created at the NGI_GRNET queue.
* A queue with name NGI_GRNET. For every ticket assigned to the NGI_GRNET support unit at the GGUS, a new ticket is created at the NGI_GRNET queue.
    * A queue for every site under the scope of the NGI_GRNET. For every ticket assigned to a site in the scope of NGI_GRNET support unit at the GGUS, a new ticket is created at the corresponding site’s queue at the HellasGrid RT.
* A queue for every site under the scope of the NGI_GRNET. For every ticket assigned to a site in the scope of NGI_GRNET support unit at the GGUS, a new ticket is created at the corresponding site’s queue at the HellasGrid RT.
    * A queue with name GGUS. For every ticket assigned to the GGUS queue at the HelalsGrid RT, a new ticket is created at the GGUS which is initially un-assigned.  
* A queue with name GGUS. For every ticket assigned to the GGUS queue at the HelalsGrid RT, a new ticket is created at the GGUS which is initially un-assigned.  


The implementation was done with the use of the Perl programming language, in order to reuse the HellasGrid RT code for the access and the administration of the tickets stored at the HellasGrid RT database. For the web services implementation, the Perl module SOAP::Lite (http://www.soaplite.com/) was used. The code of the web service implemented is in the file ticket.cgi located at the path /usr/lib/cgi. It is a cgi script which provides 3 call functions for a ticket creation, a ticket update, and for sending an attachment within a ticket.
The implementation was done with the use of the Perl programming language, in order to reuse the HellasGrid RT code for the access and the administration of the tickets stored at the HellasGrid RT database. For the web services implementation, the Perl module SOAP::Lite (http://www.soaplite.com/) was used. The code of the web service implemented is in the file ticket.cgi located at the path /usr/lib/cgi. It is a cgi script which provides 3 call functions for a ticket creation, a ticket update, and for sending an attachment within a ticket.
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

Retrieved from "https://wiki.egi.eu/w/index.php?title=NGI_GRNET:RT_GGUS_Integration&oldid=101340"