1 / 6

Actions list from third ops meeting

Actions list from third ops meeting. 1 – Ops model. •AR: T1 - T1 links: investigate cost model and then highlight contractual responsibilities to be used. •GCX: Put link name on hidden link, we will manage them as “pure” LHCOPN link.

barid
Download Presentation

Actions list from third ops meeting

An Image/Link below is provided (as is) to download presentation Download Policy: Content on the Website is provided to you AS IS for your information and personal use and may not be sold / licensed / shared on other websites without getting consent from its author. Content is provided to you AS IS for your information and personal use only. Download presentation by click this link. While downloading, if for some reason you are not able to download a presentation, the publisher may have deleted the file from their server. During download, if you can't get a presentation, the file might be deleted by the publisher.

E N D

Presentation Transcript

  1. Actions list from third ops meeting GCX

  2. 1 – Ops model •AR: T1 - T1 links: investigate cost model and then highlight contractual responsibilities to be used. •GCX: Put link name on hidden link, we will manage them as “pure” LHCOPN link. •GCX: Improve Ops model on the twiki , send link to twiki and slides with overview of agreement and ask to come to next meeting with an agreement – to everybody •GCX: Provide some real life examples of Ops model implementation • GB: Test scheduled maintenance •GCX: Ask to the MDM feedback group a manager's view of the LHCOPN like ASPDrawer with only green/red lights. •GB: Check scheduled downtimes policy with WLCG MoU. GCX

  3. 2 – Information repositories •GCX+EM: Reorganise twiki to fit operational model •GCX: Investigate quick regular automated mirroring of some twiki pages •GCX: Exchange with GGUS around improvement requested - prioritised list: 1 - Notification + mail patterns •GCX: Study the calendar with requirements •EM: Provide a LHCOPN logo to be put everywhere + LHCOPN vs LCGOPN? •GCX: Ask by mail to LHCOPN ML concerns about privacy of some information. If no answer silently agreed. GCX

  4. 3 - Implementation • EM: Enforce backup tests before August • ?: Ops model to be tested • Test tickets + test write access to twiki - delayed • GCX: Compute some statistics from ASPDrawer • Make computation “public” • Provide scheduled downtime in SQL/CSV/XML • Give GGUS-id link to people to see troubles are followed • GCX: Prepare a demo of ops model + twiki summary • GCX: Next ops meeting • Who (more people), where, when - with EVO capabilities – After next ops meeting • Successor of David: Responsible forquality assessment • We should provide all data required • Scheduled downtime should be managed GCX

  5. Ops model roadmap LHCOPN meeting @ Copenhagen Ops model v2 proposed Beta release of LHCOPN GGUS TTS LHCOPN meeting @ Berlin LHCOPN meeting Assessment of the model LHC startup LHCOPN meeting 8 9 10 11 12 1 2 3 4 5 6 7 9 10 11 8 Production version Model compulsory 2009 Trial version Model optional Public release of GGUS TTS GCX

  6. Next LHCOPN meeting – 2008-01 • Short reminder of the model • Show reorganised twiki • Answer to feedbacks • Mail for those not attending • Demo • Roadmap • Discussion on agreement • How to disseminate the ops model • Target 12 router operators GCX

More Related