GGUS Advisory Board - 'after EMI/IGE'

Wednesday 13 Mar 2013, 11:00 → 16:00 Europe/Amsterdam

Malgorzata Krakowian (EGI.EU)

This meeting was complementary to 3rd GGUS AB meeting. It was mainly focused on what will change after EMI/IGE.

----------------------------------------------------------
Room link: http://connect.ct.infn.it/egi-inspire-sa1/
Please provide you Name and Affiliation as Guest Name.
In left top corner you will find "Meeting->Audio Setup Wizard" Button which will help you to configure your audio.
You can test Your Computer with this link http://connect.ct.infn.it/common/help/en/support/meeting_test.htm
Adobe Connect tutorials: http://tv.adobe.com/show/learn-adobe-connect-8/
----------------------------------------------------------

Participants:

• Malgorzata Krakowian (EGI.eu)
• Ales Krenek (NGI_CZ)
• Tiziana Ferrari (EGI.eu)
• Guenter Grein (GGUS)

Processing middleware tickets after EMI/IGE

Legacy tickets slide
What will happen to tickets submitted before April 30th?
We should discuss tickets only for Technology Providers (TPs) that want to stop the support in GGUS.
List of those TPs will be created base on survey.

@A on EGI.eu: Create a survey until 22nd of March
@A on Guenter: Contact Mathilde for TP support contacts
@A on Ales (in May): identify tickets that are out of scope of the TP. Identify orphaned tickets.

Technology helpdesk slide
There are problems with access rights to the tech helpdesk. Proposal to close Technical Helpdesk and move to GGUS. It will be more user friendly and GGUS will not have to maintain it.

Migration issues:
. specific fields supported in TH specific fields - In TH are fields like Component, Component version to keep track of the version of component affected. Not used so much so far but in favor to make it mandatory in every ticket routed to TP.  It is possible from the technical point of view to move fields to GGUS.
. No problems is rolling to a general GGUS policy. This allows parent/children, master/slave.
. ETA for all tickets regardless of their priority

Monitoring and reporting slide

. Monitoring and reporting is necsessary.
. Motivation is to enforce process for support
. We don't want to have another meeting. A simple dashboard for TPs where can be checked the status (e.g. if they are breaking MoU). Solution from EMI should be checked.
. High priority issues: UMD coordination meeting

@A on Guenter: discuses TP dashboard solution with Helmut and present the proposal in Manchester.

Ticket routing slide
Postpone discussion after survey

DMSU slide
Tickets should be routed to TPs to notify about issues (no blocking of lower priority tickets)

Best effort support slide
Proposal is reasonable.

@A on Ales: send the proposal to DMSU and ask for feedback until 21.03
@A on Guenter: prepare a presentation about process for handling tickets waiting for input from middleware providers during next OMB

Survey:
We need to include question about:
. do they continue support in GGUS
. about support level. Define also policies
. which SU will be used in the future? New? Existing ones?
. are they willing to move from Technology Helpdesk to GGUS?

AOB
@A on Ales: provide figures for annual EGI report

Actions and open tickets:
@A on EGI.eu: Create a survey until 22nd of March
@A on Guenter: Contact Mathilde for TP support contacts
@A on Ales (in May): identify tickets that are out of scope of the TPs. Identify orphaned tickets.
@A on Ales: send the 'process for handling tickets waiting for input from middleware providers' proposal to DMSU and ask for feedback until 21.03
@A on Guenter: prepare a presentation about 'process for handling tickets waiting for input from middleware providers' for next OMB
@A on Guenter: discuses TP dashboard solution with Helmut and present the proposal in Manchester.
@A on Ales: provide figures for annual EGI report

11:00 → 12:30 Processing middleware tickets after EMI/IGE

Questions and ideas on processing middleware tickets after the end of EMI/IGE April 2013

Convener: Guenter Grein (KIT-G)