Download presentation
Presentation is loading. Please wait.
Published byAdele Ward Modified over 9 years ago
1
EGEE-III INFSO-RI-222667 Enabling Grids for E-sciencE www.eu-egee.org EGEE and gLite are registered trademarks Regional Dashboard Cyril L’Orphelin - CNRS/IN2P3 Abingdon, England
2
Enabling Grids for E-sciencE EGEE-III INFSO-RI-222667 One common view with 3 different group of roles. If you are registered with several roles into GOC DB, you can manage it in your preferences. Site administrator Role already defined into GOC DB ROC staff ( ROC deputy, ROC Manager, ROC staff, 1st Line Support ) Roles already defined into GOC DB these roles will be authorized to act as Regional Operator C-COD Operator new role added in GOC DB (this role is approved by C-COD Administrator ) The advantage to use roles from GOC DB, you have to update once your certificate.
3
Enabling Grids for E-sciencE EGEE-III INFSO-RI-222667 Preferences
4
Enabling Grids for E-sciencE EGEE-III INFSO-RI-222667 Site Name Alarms Ticket Downtime GOC DB link GStat Status Network trouble Dashboard aspect
5
Enabling Grids for E-sciencE EGEE-III INFSO-RI-222667
6
Enabling Grids for E-sciencE EGEE-III INFSO-RI-222667 workflow We have keep the mailing lists used in the classical model. When a ticket is created for a site : –A mail is sent to the corresponding roc ( ROC mail addresses defined in GGUS ) –A mail is sent directly to the site (except for UKI and DECH ) –A mail is sent to sa1-follow-up mailing list. => I think that some ROCS will disagree to use the same mailing list to follow up tickets.
7
Enabling Grids for E-sciencE EGEE-III INFSO-RI-222667 Additional features Code color based on the age of alarm: green if age < 24 h yellow if 24 h < age < 2 weeks red if age > 2 weeks Grid Web Search Engine (provided by ASCC, Taiwan ) added in the creation form of the ticket. Notepad of site present at the end of the ticket creation form. Inclusion of several alarms in the ticket. Handover log => You can report problems to your federation and to other federations or also to C-COD. You can also see the history of theses exchanges.
8
Enabling Grids for E-sciencE EGEE-III INFSO-RI-222667 Next steps In January we will start the tests in production with 4 federations. Add the possibility to open tickets against OPS tools Add the possibility to open tickets with alarms not coming from SAM, especially for network troubles. Add metrics linked with alarms During the month of January I encourage people to report bugs and recommendations to improve the dashboard. In February I will implement improvements and new features coming from the 1 st shifts After this we will work on a version of dashboard based on Nagios.
9
Enabling Grids for E-sciencE EGEE-III INFSO-RI-222667 Distributed model Central Dashboard Central Web Service Dashboard Instance + DB Web Service Instance Regional Helpdesk Dashboard Instance + DB Web service Instance GGUS Helpdesk Dashboard Regional View Regional Helpdesk REGION 1 REGION 2 CENTRAL LEVEL REGION 3
10
Enabling Grids for E-sciencE EGEE-III INFSO-RI-222667 Step 1 Central Level Dashboard 1 Dashboard 2 Dashboard 3 Dashboard 4 Web Service Central Lavoisier GGUS
11
Enabling Grids for E-sciencE EGEE-III INFSO-RI-222667 Step 2 Central Level Dashboard 1 Dashboard 2 Dashboard 3 Dashboard 4 GGUS Web Service Central Lavoisier Resource 1 Resource 2 Resource 3 Resource 4 Central Dashboard Central Resource
12
Enabling Grids for E-sciencE EGEE-III INFSO-RI-222667 Central Level Dashboard 1 Dashboard 2 Dashboard 3 Dashboard 4 GGUS REGIONAL HELPDESK 1 REGIONAL HELPDESK 2 REGIONAL HELPDESK 3 REGIONAL HELPDESK 4 Web Service 1 Resource 1 Web Service 2 Resource 2 Web Service 3 Resource 3 Web Service 4 Resource 4 Central Web service STEP 3 Step 3
Similar presentations
© 2024 SlidePlayer.com. Inc.
All rights reserved.