Information Systems
 from an operational perspective
         James Casey, CERN
    EGEE’09 Conference, Barcelona
• 4 observations from an operations guy
 • Bootstrapping
 • We’re not all islands
 • Structure matters
 • Provenance
Bootstrapping
GOCDB has a site list ...

     ... which feeds a top level BDII ...

   ... which is used to configure SAM ...

      ... ...
How we configure our grids
How can we make this simpler ?
We’re not all islands
Inconsistencies kill
    operations
Roles and responsibilities
Structure matters
• Attributes are very important for
  middleware

  • “Exactly what do you do and how are
    you doing now”

• Relationsh...
Everyone’s relationships
     are different
Infrastructures ‘own’
      resources
VOs ‘name’ resources
Aggregate topology provider
More connections are better
Provenance
Who really published this data and should
they have ?


  Canonical Example: Single LFC for a VO,
        but anyone can p...
How do we allow anyone to publish but
allow the act of publication to be ‘signed off’
by another entity?
What is at the Grid ?
What should be on the
       grid ?
Proposal :
What should be on the
       grid ?
Summary :
• Structure and relationships
• Consistency
• Single (traceable) source of information
• Allow VO/Projects/ops t...
Make your grumpy ops guy happy
Thank you.
http://www.flickr.com/photos/jurvetson/916142/

http://www.flickr.com/photos/spyderracer393/474935005/in/
pool-661546@N22

h...
Grid Information systems from an Operations Perspective
Grid Information systems from an Operations Perspective
Grid Information systems from an Operations Perspective
Upcoming SlideShare
Loading in …5
×

Grid Information systems from an Operations Perspective

1,005 views

Published on

A presentation decribing issues and future ideas for grid information systems in the EGEE project

Published in: Technology, Business, Education
  • Be the first to comment

  • Be the first to like this

Grid Information systems from an Operations Perspective

  1. 1. Information Systems from an operational perspective James Casey, CERN EGEE’09 Conference, Barcelona
  2. 2. • 4 observations from an operations guy • Bootstrapping • We’re not all islands • Structure matters • Provenance
  3. 3. Bootstrapping
  4. 4. GOCDB has a site list ... ... which feeds a top level BDII ... ... which is used to configure SAM ... ... which is used to test sites ... ... from which Gridview calculates status ... ... from which FCR removes sites from VO BDIIs !
  5. 5. How we configure our grids
  6. 6. How can we make this simpler ?
  7. 7. We’re not all islands
  8. 8. Inconsistencies kill operations
  9. 9. Roles and responsibilities
  10. 10. Structure matters
  11. 11. • Attributes are very important for middleware • “Exactly what do you do and how are you doing now” • Relationships are very important for operations • “Who are you related to. What groups do you belong to”
  12. 12. Everyone’s relationships are different
  13. 13. Infrastructures ‘own’ resources VOs ‘name’ resources
  14. 14. Aggregate topology provider
  15. 15. More connections are better
  16. 16. Provenance
  17. 17. Who really published this data and should they have ? Canonical Example: Single LFC for a VO, but anyone can publish one ==> Operational problems ;(
  18. 18. How do we allow anyone to publish but allow the act of publication to be ‘signed off’ by another entity?
  19. 19. What is at the Grid ?
  20. 20. What should be on the grid ?
  21. 21. Proposal : What should be on the grid ?
  22. 22. Summary : • Structure and relationships • Consistency • Single (traceable) source of information • Allow VO/Projects/ops to annotate • Provenance • Things we can write tests against
  23. 23. Make your grumpy ops guy happy
  24. 24. Thank you.
  25. 25. http://www.flickr.com/photos/jurvetson/916142/ http://www.flickr.com/photos/spyderracer393/474935005/in/ pool-661546@N22 http://www.flickr.com/photos/that_james/496767790/ http://www.flickr.com/photos/bigdogwoody2000/2389109926/

×