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 "EGI-InSPIRE:SA1.6-QR4"

From EGIWiki
Jump to navigation Jump to search
Line 39: Line 39:
During the last quarter one of the main areas of work for GGUS was the definition and implementation of technology related workflows. Work on the technology support workflow continued aqnd resulted in a few refinements and modifications of the technology helpdesk. The main effort was spend in defining and implementing the the software provisioning workflow. Through this workflow the TPs annouce releases by submitting a ticket which is then routed to the EGI-SA2 activity through an interface to the EGI-RT system. Feedbeack concerning the release is also be handled through this ticket which is assigned back to the TP with an "accept" or "reject".
During the last quarter one of the main areas of work for GGUS was the definition and implementation of technology related workflows. Work on the technology support workflow continued aqnd resulted in a few refinements and modifications of the technology helpdesk. The main effort was spend in defining and implementing the the software provisioning workflow. Through this workflow the TPs annouce releases by submitting a ticket which is then routed to the EGI-SA2 activity through an interface to the EGI-RT system. Feedbeack concerning the release is also be handled through this ticket which is assigned back to the TP with an "accept" or "reject".


In parallel the decomissioning of ROCs and creation of NGIs continued. NGI-IT has been created as a support unit in GGUS.
In parallel the decomissioning of ROCs and creation of NGIs continued. NGI_IT and NGI_FI have been created as support units in GGUS.


A requirements queue for GGUS has been set up in RT to collect input from all parties involved. It is currently in the testing phase. The major difficulty is the required SSO account, as not all customers of GGUS have one.
A requirements queue for GGUS has been set up in RT to collect input from all parties involved. It is currently in the testing phase. The major difficulty is the required SSO account, as not all customers of GGUS have one.

Revision as of 09:05, 29 April 2011

1. Task Meetings

Date (dd/mm/yyyy) Url Indico Agenda Title Outcome
weekly (phone): Participants Maria Dimou, Helmut Dres, Guenter Grein https://www.egi.eu/indico/categoryDisplay.py?categId=27 "shopping list" meeting traceable at: https://savannah.cern.ch/projects/esc/
14/03/2011 https://www.egi.eu/indico/conferenceDisplay.py?confId=416 Joint OTAG-USAG-EMI-IGE Meeting to define a common workflow for GGUS requirements set-up of a GGUS requirements queue in RT, currently in the testing phase
need driven no INDICO URL one on one meetings with NGI interface developers testing the interfaces, resolving interface issues
need driven no INDICO URL meetings with EGI-SA2 /EMI /IGE definition of the technology support workflows and their implementation

2. Main Achievements

During the last quarter one of the main areas of work for GGUS was the definition and implementation of technology related workflows. Work on the technology support workflow continued aqnd resulted in a few refinements and modifications of the technology helpdesk. The main effort was spend in defining and implementing the the software provisioning workflow. Through this workflow the TPs annouce releases by submitting a ticket which is then routed to the EGI-SA2 activity through an interface to the EGI-RT system. Feedbeack concerning the release is also be handled through this ticket which is assigned back to the TP with an "accept" or "reject".

In parallel the decomissioning of ROCs and creation of NGIs continued. NGI_IT and NGI_FI have been created as support units in GGUS.

A requirements queue for GGUS has been set up in RT to collect input from all parties involved. It is currently in the testing phase. The major difficulty is the required SSO account, as not all customers of GGUS have one.

3. Issues and Mitigation

Issue Description Mitigation Description
Issue description Issue mitigation
GGUS receives requirements from various sources, e.g. USAG, OTAG, technology providers, WLCG Dedicated OTAG meeting with participation from all parties to streamline the process will be held end of February or beginning of March

4. Plans for the next period

The next quarter will see the extension of the technology helpdesk to also cover the release workflow. The TPs will then annouce releases by submitting a ticket which will then be routed to the EGI-SA2 activity through an interface to the EGI-RT system. Feedbeack concerning the release will then also be handled through this ticket which will be assigned back to the TP with an "accept" or "reject".

Other areas of work in the quarter include the redesign of the GGUS report generator to make it more flexible, the review of the support units to get rid of unused legacy support units and to bring the documentation up-to-date. The integration of NGIs, which is not yet completed will also continue.