Review of WLCG operations and support

Structure of the document

• Scope of this document
• Introduction [TEG mandate]
• Work areas
  • Monitoring and metrics
    • Site and service monitoring
    • Experiment activity monitoring
    • Monitoring data analysis
    • Alerting systems
  • Support tools
    • Ticketing tools [including interoperability]
    • Accounting tools
    • Request trackers
    • Administration tools [GOCDB, CIC]
  • Underlying services
    • Messaging services
    • Information services
  • Application software management
  • Middleware operational requirements
  • Service and middleware configuration
  • Service and middleware deployment
  • Middleware distribution
  • WLCG operations and procedures
• Conclusions

Work organisation

Subgroup -> area mapping:

• WG1: Monitoring and metrics
• WG2: Support tools, underlying services, WLCG operations and procedures
• WG3: Application software management
• WG4: Middleware operational requirements
• WG5: Service and middleware configuration, Service and middleware deployment, Middleware distribution

Content

Each work area section should contain a summary table with a row for each subtopic and a column for:

• Works well
• Needs to improve [sorted by importance, the first 3 items will be the top 3 problems]

A short description should be in the table, while the section text should go in more detail and also describe, for each subtopic:

• the existing operational procedures (when relevant)
• what takes the most effort from experiments, sites and infrastructure providers
• strengths and weaknesses
• important areas which are not covered
• what is provided but not used

The full document should not be longer than X pages and the length of each area section should not deviate more than +- 50% of Y pages (unless motivated).

-- AndreaSciaba - 25-Oct-2011