MANDATE:
- Move from central COD model to regional COD model; goal: central COD as we understand it today does not exist at the end of EGEE III; all rocs running a regional cod by the end of egee III
- Define what a “thin central COD layer” would do, and if needed introduce it in the new COD model
- Coordination between regional CODs and central thin layer COD (if needed)
- Communication and share of expertise between regional CODs
- Update and maintain common operational procedures
MAIN CONCERNS (extracted from Helene's presentation at the transition meeting):
- Follow-up on the requirements on each of the monitoring tools for COD daily work and tools integration purposes
- Process failover of all operational tools needed for COD work
- Assessment of the operational tools availability
- Need to define the interface with OAT, ROCs
- Make the COD structure evolve to gather and coordinate manpower to improve and enhance COD service now and in transition phase to regional model
- COD mandate need to be officially agreed on, for federations to foresee the manpower at the same time as the OAT
- Community building for the two following purposes:
- 1rst line support generalization and consequences on tools and procedures including set-up of a knowledge base
- Experimentation on what the operations model of the next COD generation in EGI could be
- Need of interface to OAT in terms of requirements follow-up : Monitoring tools, failover, integration tool (The OAT handles development and availability of monitoring tools. CODs (r-CODs, c-COD), as users of those tools, are clients of the OAT. They assess their reliability.)
- Need of interface to ROC via internal committees : ROC-Forum for setting-up failover mechanisms for m/w core services
Speaker:
Helene Cordier
(CNRS/IN2P3)