Agenda:
Małgorzata Krakowian is replacing Richard McLennan as a GGUS AB chair person.
List of actions: http://go.egi.eu/GGUS_AB_RT
#4989: workflow to handle tickets with no response from submitter/supporter
Nothing will change for users with certificates. There is a pilot action to integrate EGI SSO group 'GGUS users' with GGUS through shibboleth. At this point the group will be managed manually by Peter Solagna. It is not suspected to become high workload. Other identity providers will be able to integrate with GGUS through shibboleth as well.
Should be ready in second semester of 2013.
We need more concrete plans from product teams in terms of support through GGUS.
@A EGI.eu: collect support contact points for each product team
@A EGI.eu: survey - discuses different service levels (with concrete scenarios) with PT
* questionnaire send to GGUS AB, EMI and IGE for comments till mid March
* questionnaire send to PT by mid March
* time for response - first week of April to have responses by CF2013
suggestions from Mathilde:
- you should mention about MOU/SLA in the questionnaire
- For EMI the channel to contact PT will be Cristina or Andrea (need to be ask first)
suggestions from Steve:
- For IGE the channel to contact PT will be Helmut (need to be ask first)
suggestions from Gunter:
- keep technical processes a much simple as possible (questionnaire should be with proposed solutions)
* Some of support units will not response so we will need to try solve as much issues as possible before they reach those SU. We should also remove SU rather then keep "dead" ones.
* Best effort is not "do what you want" but a minimum of support response (eg two weeks)
* Gunter: we can have in GGUS icons which will indicate the level of support
Workflow doesn't take into account priority to not make it less clear. We can think about different timeliness for each priority. Less priority tickets should not reach TP but is such situation TP will not get information about the problem.
@A EGI.eu: schedule a meeting for next week about workflow discussion.
This is high priority activity for EGI.
This proposal should be discuses with Maria Dimou. Feedback should be provided by next AB where we will approve the proposal.
Plans not decided yet
* Interaction with security team
The CSIRT team was discussing whether they can/will use GGUS for submitting tickets in case of security issues. The last discussion took place in Munich on the CF 2012. The outcome of the Munich discussion was that CSIRT team could not agree on a work flow and needed further internal discussions. Since this we never heard anything from CSIRT concerning this issue. Gunter: last feedback from security is that they will like to discuses it internally
@A Dave Kelsey: finding out whether CSIRT has still plans using GGUS or not.
* Interaction with Prace
For Prace this is not a priority so the activity is on hold.
Actions and open tickets:
@A EGI.eu: collect support contact points for each product team
@A EGI.eu: survey - discuses different service levels (with concrete scenarios) with PT
* questionnaire send to GGUS AB, EMI and IGE for comments till mid March
* questionnaire send to PT by mid March
* time for response - first week of April to have responses by CF2013
@A EGI.eu: schedule a meeting for next week about workflow discussion.
@A Dave Kelsey: finding out whether CSIRT has still plans using GGUS or not.
#4989: workflow to handle tickets with no response from submitter/supporter
- proposal will be presented during the meeting
#4990: DMSU wiki pages to be updated
- will be done asap by Ales
#4991: Notification of failures of operational tools through GGUS
- Tiziana will look through the proposal and contact Helmut to ask additional questions
Next meeting:
* 8.04.2013 at Community Forum 11:00-12:30