1 / 9

LHCOPN Meeting March 2008

LHCOPN Meeting March 2008. Thanks to RedIRIS for the hospitality!! Thanks to everyone for attending!! Please Upload All Talks!!. Introducing. Xavier Jeannin Guillaume Cessieux A quick round table. We have made progress. Operations Handbook. Some agreements and some disagreements.

helmut
Download Presentation

LHCOPN Meeting March 2008

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. LHCOPN MeetingMarch 2008 Thanks to RedIRIS for the hospitality!! Thanks to everyone for attending!! Please Upload All Talks!!

  2. Introducing • Xavier Jeannin • Guillaume Cessieux • A quick round table.

  3. We have made progress • Operations Handbook. • Some agreements and some disagreements. • But perhaps more agreement now? • How do we maintain and evolve agreements? • Operations Portal (Twiki)? • We agree on some centralised functions • But we need to detail these and find a home for them • IPCU • Where can/should this live after EGEE-III (but we have 2 years to consider this)

  4. Operations – Yes, it IS hard! • Where are we? • We have a working infrastructure, but is it manageable, sustainable? • Are we organised to respond to problems? changes? • Can we deliver a service that is predictable? • Have we solved communicating with the applications community? • Have we identified the functional units? • Are responsibilities clear?

  5. This is a “points of view” meeting • The “network manager” view (Me) • The “user” view (“Readiness” expectations) • The “distributed” view (E2ECU, IPCU, GGUS etc) • The “grass roots” view (Site engineers) • The “centralised” view (Dante) • Each has its own opinion, needs and approach. We need to find the most appropriate, common solutions.

  6. What Does The Network Manager Want? • To be able to respond to the “high level” complaints • “The network is slow” • “There are always problems” • “You never fix the problems in time” • “You don’t inform us what is happening” • “No-one knows what to do” • To be able to plan the evolution • How are resources being used? • What can we foresee in terms of growth? • Are we fulfilling the requirements? (normally measured by the lack of unstructured complaints)

  7. What Does The Network Manager Need? • A global view • Information about the network usage • Information about problem tracking • Structured process implementation • To know what should happen in each situation • Incident management • Problem management • Change management • Clear definition of responsibilities and accountability

  8. Objectives • Operations: Need to converge on some concrete work items (if possible). • And decide who will do them. • Monitoring: Need to decide if the current strategy (appliance) is workable • And if not, how to move forward.

  9. This is a “points of view” meeting • The “network manager” view (Me) • The “user” view (“Readiness” expectations) • The “distributed” view (E2ECU, IPCU, GGUS etc) • The “grass roots” view (Site engineers) • The “centralised” view (Dante)

More Related