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

From EGIWiki
Jump to navigation Jump to search
Line 1: Line 1:
[[Category:SA1 Task QR Reports]]
[[Category:SA1 Task QR Reports]]
= 1. Task Meetings = <!--
__NOTOC__
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.
= 1. Task Meetings =
OMB meeting will be reported under task TSA1.1 only. Monday Operations meetings need to be reported under task TSA1.3 only. Training events will be recorded in the training event registry and need not be mentioned here.
{| border="1" cellspacing="0" cellpadding="5" align="center"
-->
! style="width: 15%" | Date (dd/mm/yyyy)
 
! style="width: 15%" | Url Indico Agenda
{| align="center" cellspacing="0" cellpadding="5" border="1"
! style="width: 10%" | Title
! style="width: 20%" | 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
|-
|-
! style="width: 10%" | Date (dd/mm/yyyy)
| need driven
! style="width: 20%" | Url Indico Agenda
| no INDICO URL
! style="width: 20%" | Title
| one on one meetings with NGI interface developers
! style="width: 50%" | Outcome
| 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 = <!--
Note. This is a detailed account of progress over the previous quarter of activities within  the  task.
PLEASE PROVIDE TEXT IN A GOOD EDITED FORM (AVOID BULLET LISTS OF SHORT ITEMS THAT REQUIRE EXPANSION WHEN INSERTED IN AN OVERALL REPORT)
-->


= 3. Issues and Mitigation = <!-- fill the table below
= 2. Main Achievements =
PLEASE PROVIDE TEXT IN A GOOD EDITED FORM (AVOID BULLET LISTS OF SHORT ITEMS THAT REQUIRE EXPANSION WHEN INSERTED IN AN OVERALL REPORT)-->  
== Report Generator ==
There was a life demo of the report generator on TF in Prague.
 
== GGUS structure  ==
=== Support units  ===
A couple of new support units have been introduced during the last quarter. They are<br>
* 2nd level software support unit -- QosCosGrid<br>
Decommissioned support units<br>
* "ARC Deploy"
* "NGI_AT"
* "OTAG"
 
=== VOs  ===
VOs "t2k.org", "comet.j-parc.jp" and "neurogrid.incf.org" were added to the list of VOs which provide support via GGUS.<br>
 
== GGUS web portal ==
*  <br>
* Updated the info section with new "did you knows?" <br>
 
== GGUS system  ==
* <br>
* <br>


{| cellspacing="0" cellpadding="2" border="1"
== Interfaces with other ticketing systems ==
* Brought online interface for new NGI_FRANCE ticketing system OTRS.
* Started implementation of interface for IBERGRID RT ticketing system.
 
==== GGUS - SNOW interface ====
* Implemented distinction between incidents and change requests
 
== xGUS ==
ntr
 
== High availability ==
* Auto-switching for the Remedy server still not implemented.
 
= 3. Issues and Mitigation = 
 
{| border="1" cellspacing="0" cellpadding="2"
|-
|-
! scope="col" | Issue Description  
!scope="col"| Issue Description
! scope="col" | Mitigation Description
!scope="col"| Mitigation Description
|-
|-
|  
|Collaboration of GGUS with CSIRT
|  
|Assessment of adaption of GGUS access model to meet the needs of CSIRT. This discussion is still ongoing.
|-
|Collaboration of GGUS and PRACE
|Defining work flows for routing tickets between GGUS and PRACE RT. This discussion is still ongoing.
|-
|-
|
|
|}
|}


= 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 -->
== GGUS report generator ==
Implement missing features and bug fixing. The final version will be available by end of 2012.
 
== GGUS structure  ==
Integration of Operations Portal in GGUS.
 
=== Support units  ===
 
=== VOs  ===
Add new VO ""
 
== GGUS web portal ==
 
== GGUS system  ==
 
== Interfaces with other ticketing systems ==
* Implement interface to PRACE RT system.
 
== xGUS ==
ntr
== High availability ==
ntr

Revision as of 16:10, 16 October 2012


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

There was a life demo of the report generator on TF in Prague.

GGUS structure

Support units

A couple of new support units have been introduced during the last quarter. They are

  • 2nd level software support unit -- QosCosGrid

Decommissioned support units

  • "ARC Deploy"
  • "NGI_AT"
  • "OTAG"

VOs

VOs "t2k.org", "comet.j-parc.jp" and "neurogrid.incf.org" were added to the list of VOs which provide support via GGUS.

GGUS web portal


  • Updated the info section with new "did you knows?"

GGUS system



Interfaces with other ticketing systems

  • Brought online interface for new NGI_FRANCE ticketing system OTRS.
  • Started implementation of interface for IBERGRID RT ticketing system.

GGUS - SNOW interface

  • Implemented distinction between incidents and change requests

xGUS

ntr

High availability

  • Auto-switching for the Remedy server still not implemented.

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. This discussion is still ongoing.
Collaboration of GGUS and PRACE Defining work flows for routing tickets between GGUS and PRACE RT. This discussion is still ongoing.

4. Plans for the next period

GGUS report generator

Implement missing features and bug fixing. The final version will be available by end of 2012.

GGUS structure

Integration of Operations Portal in GGUS.

Support units

VOs

Add new VO ""

GGUS web portal

GGUS system

Interfaces with other ticketing systems

  • Implement interface to PRACE RT system.

xGUS

ntr

High availability

ntr