EGI-InSPIRE:SA1.6-QR11

From EGIWiki
(Redirected from SA1.6-QR11)
Jump to: navigation, search
EGI Inspire Main page


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


Contents


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/ and https://rt.egi.eu/rt/Dashboards/2636/GGUS-Requirements
monthly (web conf): Representatives from EMI, EGI, IGE, NGIs, GGUS team, WLCG https://indico.egi.eu/indico/categoryDisplay.py?categId=78 GGUS Advisory board meeting Further development of GGUS system
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

Report Generator

Most features of the Report Generator will be implemented by end of January 2013. However some minor changes are still to be done.

GGUS structure

Support units

Decommissioned support units

VOs

Decommissioned VO

Introduced new VO

Review of VOs with low number of tickets or without any tickets in GGUS and checking the members of the VO mailing lists.

GGUS web portal

GGUS system

Interfaces with other ticketing systems

High availability

3. Issues and Mitigation

Issue Description Mitigation Description
Collaboration of GGUS with CSIRT Assessment of adaption of GGUS access model to meet the needs of CSIRT. Still waiting for clear requirements by CSIRT. This discussion is ongoing.
Collaboration of GGUS and PRACE Defining work flows for routing tickets between GGUS and PRACE RT. Waiting for PRACE setting up an RT ticketing system. Provided contact with M.Liska for assisting in setting up an RT instance.

4. Plans for the next period

GGUS report generator

Implement some minor requirements that came up lately.

GGUS structure

Interfaces with other ticketing systems

Personal tools
Namespaces
Variants
Actions
Navigation
Toolbox
Print/export