Difference between revisions of "EGI-InSPIRE:SA1.6-QR12"
Jump to navigation
Jump to search
(4 intermediate revisions by 3 users not shown) | |||
Line 1: | Line 1: | ||
{{Template: | {{Template:EGI-Inspire menubar}} | ||
{{Template:Inspire_reports_menubar}} | {{Template:Inspire_reports_menubar}} | ||
{{TOC_right}} | {{TOC_right}} | ||
= 1. Task Meetings = <!-- | = 1. Task Meetings = <!-- | ||
Notes. Report here all task-specific meetings held. This includes (a) face-to-face meetings and (b) phone meetings. Make sure that for all task meetings participants are ALWAYS recorded either on indico from the registrants’ list, or in the minutes. | Notes. Report here all task-specific meetings held. This includes (a) face-to-face meetings and (b) phone meetings. Make sure that for all task meetings participants are ALWAYS recorded either on indico from the registrants’ list, or in the minutes. | ||
Line 69: | Line 69: | ||
== GGUS web portal == | == GGUS web portal == | ||
* | * New "Did you knows?" about the following topics: | ||
- Info about team and alarm members/tickets | |||
- Ticket relation in GGUS | |||
- Brief instruction how to process GGUS tickets | |||
* Decommission of the software release dashboard | |||
* Implementation of an ticket monitoring dashboard (only visible for authorised staff) | |||
* New info pages for TEAMers and ALARMers | |||
== GGUS system == | == GGUS system == | ||
Line 104: | Line 110: | ||
= 4. Plans for the next period = <!-- provide your text below. PLEASE PROVIDE TEXT IN A GOOD EDITED FORM (NO BULLET LISTS OF SHORT ITEMS THAT REQUIRE EXPANSION WHEN INSERTED IN A REPORT) --> | = 4. Plans for the next period = <!-- provide your text below. PLEASE PROVIDE TEXT IN A GOOD EDITED FORM (NO BULLET LISTS OF SHORT ITEMS THAT REQUIRE EXPANSION WHEN INSERTED IN A REPORT) --> | ||
== GGUS report generator == | |||
Implement some minor requirements that came up lately. | |||
== GGUS structure == | |||
* Integration of Operations Portal in GGUS. This action is postponed as requested by Operations Portal admins.<br> | |||
* Implement a SAML/Shibboleth based access to GGUS. | |||
* Fully integrate CMS VO in GGUS and retire interface to Savannah. | |||
* Migrate GGUS shopping list from Savannah to JIRA. | |||
== Interfaces with other ticketing systems == | |||
* Implement interface to PRACE RT system. | |||
* Implement interface to DANTE ticketing system. |
Latest revision as of 19:07, 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 | 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 went online with the Feb release. However some minor changes are still to be done: RT 4750 RT 4752
GGUS structure
Support units
Decommissioned support units
- "gLite Release Pages and Repository"
- "NGI_ZA"
New support units
- "UI WN Tarball"
VOs
Decommissioned VO
- "ict.vo.ibergrid.eu"
- "demo.vo.edges-grid.eu"
- "vo.sixt.cern.ch"
- "vo.gear.cern.ch"
- "israelvo.isragrid.org.il"
Introduced new VO
- "ops.ndgf.org"
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
- New "Did you knows?" about the following topics:
- Info about team and alarm members/tickets - Ticket relation in GGUS - Brief instruction how to process GGUS tickets
- Decommission of the software release dashboard
- Implementation of an ticket monitoring dashboard (only visible for authorised staff)
- New info pages for TEAMers and ALARMers
GGUS system
- Finished migration of GGUS mail boxes to new KIT mail infrastructure.
- Clarified meaning of status "waiting for reply".
- Review of VOs providing support via GGUS.
Interfaces with other ticketing systems
- Fixed bugs in interface to CERN SNOW.
- Implementation of interface for IBERGRID RT ticketing system.
- Updated interface with NGI_CZ RT due to system migration of RT.
- Updated GGUS host certificate.
Alarm tests after GGUS releases
- Executed the alarm and interface tests after GGUS releases.
High availability
- Skipped auto-switching approach. Switching to the backup machines will be done using a management script that can be run by GGUS admins or the KIT on-call service at any time.
3. Issues and Mitigation
Issue Description | Mitigation Description |
---|---|
Collaboration of GGUS with CSIRT | CSIRT decided not using GGUS. |
Collaboration of GGUS and PRACE | This action is postponed as it has only low priority for PRACE at the moment. |
4. Plans for the next period
GGUS report generator
Implement some minor requirements that came up lately.
GGUS structure
- Integration of Operations Portal in GGUS. This action is postponed as requested by Operations Portal admins.
- Implement a SAML/Shibboleth based access to GGUS.
- Fully integrate CMS VO in GGUS and retire interface to Savannah.
- Migrate GGUS shopping list from Savannah to JIRA.
Interfaces with other ticketing systems
- Implement interface to PRACE RT system.
- Implement interface to DANTE ticketing system.