Download presentation
Presentation is loading. Please wait.
Published byAmberly Parrish Modified over 8 years ago
1
www.egi.eu EGI-InSPIRE RI-261323 EGI-InSPIRE www.egi.eu EGI-InSPIRE RI-261323 GGUS Report Generator Günter Grein, KIT Helmut Dres, KIT Torsten Antoni, KIT Carsten Rogge, KIT 1
2
www.egi.eu EGI-InSPIRE RI-261323 History Requirements Timescale Current status Outlook Outline 2
3
www.egi.eu EGI-InSPIRE RI-261323 Reports done by GGUS team –https://ggus.eu/pages/metrics/download_escala tion_reports.phphttps://ggus.eu/pages/metrics/download_escala tion_reports.php –https://ggus.eu/pages/metrics/download_metric s_reports.phphttps://ggus.eu/pages/metrics/download_metric s_reports.php Reports done in self-service –GGUS search engine: https://ggus.eu/ws/ticket_search.php https://ggus.eu/ws/ticket_search.php –GGUS report generator: https://ggus.eu/stat/stat.php https://ggus.eu/stat/stat.php History
4
www.egi.eu EGI-InSPIRE RI-261323 Collected on a f2f meeting at KIT 2011-10- 26/27 –https://www.egi.eu/indico/conferenceDisplay.py ?confId=655https://www.egi.eu/indico/conferenceDisplay.py ?confId=655 –Representatives from EGI, EMI, WLCG, GGUS team Requirements
5
www.egi.eu EGI-InSPIRE RI-261323 Requirements Prio [1=highest] #Request 14 output aggregation: weeks, months, days,... 15 response time: status other than "assigned" and SU is kept or status assigned kept and SU changes 16 solution time (SU's view): assigning a ticket to an SU to ticket solving 110 pre-computed reports (EGI): frequency monthly, quarterly, yearly; based on calender and not project!! 111 ROC/NGI and site level 113 SLA reporting for EMI, IGE, SAGA TPs 28 SU topology (1st, 2nd, 3rd)-> differentiate between 3rd software, 3rd service,.... 29 output xls, csv 32 status values selectable 33 priority values selectable 319 exclude waiting for reply state as option DMSU) 320 EMI: notifications for tickets soon violating SLA if 75% of time is over 321 Priority history for DMSU 414 ticket tags: introduce a separate field "keyword"??? 415 ticket type: USER, TEAM, ALARM 416 possibility to aggregate values by criteria like status, priority, etc. 51 drilldown (-> ticket IDs) 57 ticket lifetime (user's view): creation date to ticket closing -> close (verify) all tickets after 2 weeks if user doesn't object 517 save queries -> my queries 518 automatic reports: select report template, select execution times, receive email notification -> related to #10 522 Reports by site and VO for WLCG
6
www.egi.eu EGI-InSPIRE RI-261323 First prototype available for the CF in Munich First version online by end of June –Requests of priority 1 - 2 Final version by end of 2012 Timescale
7
www.egi.eu EGI-InSPIRE RI-261323 Live-Demo https://report.ggus.eu/report/report_view.ph phttps://report.ggus.eu/report/report_view.ph p System is under construction. Don‘t use it for official reports! Current status
8
www.egi.eu EGI-InSPIRE RI-261323 Current status – home page
9
www.egi.eu EGI-InSPIRE RI-261323 Current status - reports
10
www.egi.eu EGI-InSPIRE RI-261323 Current status – data aggregation
11
www.egi.eu EGI-InSPIRE RI-261323 Current status – responisble units
12
www.egi.eu EGI-InSPIRE RI-261323 Current status - results list
13
www.egi.eu EGI-InSPIRE RI-261323 Current status - results list details
14
www.egi.eu EGI-InSPIRE RI-261323 Implement more features according to requirements list (slide #5) –Report by topology (2nd level, 3rd level) –Report by ticket type, e.g. ALARM, TEAM –Ticket lifetime from user‘s point of view –Configuration -> saving queries –Automated reports –Reports by sites and VOs Outlook
15
www.egi.eu EGI-InSPIRE RI-261323 Bug fixing Go life with a first version in time for EGI- Inspire review end of June Implement missing features if any Improving GUI Go life with final version by end of 2012 Outlook
Similar presentations
© 2025 SlidePlayer.com. Inc.
All rights reserved.