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-QR3"

From EGIWiki
Jump to navigation Jump to search
 
(4 intermediate revisions by 2 users not shown)
Line 1: Line 1:
__NOTOC__
{{Template:EGI-Inspire menubar}}
 
{{Template:Inspire_reports_menubar}}
{{TOC_right}}
= 1. Task Meetings =
= 1. Task Meetings =
<!--
<!--
Line 52: Line 55:
= 4. Plans for the next period =
= 4. Plans for the next period =
<!-- provide your text below -->
<!-- provide your text below -->
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.

Latest revision as of 18:08, 6 January 2015

EGI Inspire Main page


Inspire reports menu: Home SA1 weekly Reports SA1 Task QR Reports NGI QR Reports NGI QR User support Reports



1. Task Meetings

Date (dd/mm/yyyy) Url Indico Agenda Title Outcome
weekly (phone): Participants Maria Dimou, Helmut Dres, Guenter Grein no INDICO URL "shopping list" meeting traceable at: https://savannah.cern.ch/projects/esc/
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. The difficulty concerning these workflows is that they need to span various infrastructure and projects, as the third line support for products used in EGI lies with the technology providers issuing the products. To secure a proper inter-project workflow it was decided to restrict assignment of tickets to support units run by the technology providers to the DMSU. Technically this was realised through a sperate technology instance of GGUS. As soon as a ticket is assigned to the DMSU it will appear read-only in GGUS. Modification is only possible in the technology helpdesk, access to which is restricted to DMSU and TP support staff.

In parallel the decomissioning of ROCs and creation of NGIs continued, leading to various new NGI suppoprt units in GGUS during the last quarter (Albania, Georgia, Israel, Moldova, Montenegro) and to the closing of the support units for ROC_SW and ROC_North.

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.