Notes COD_EGI meeting	21/11/2011

*) Development of a nagios probe for automation of underperformance followup
. no product team in JRA1 is responsible of nagios probes. This activity is not a formal responsibility of partners (with the exception of middleware probes) and it has to be provided as community effort
. a global service partner may take the ownership of this development, but a re-arrangement of a global task will be needed (this is under discussion)
. until a partner volounteers for this development, the nagios probe is maintained on hold

ARmenia: lack of responsiveness of ROD team, bad Nagios performance --> suspension?
Macedonia: medium responsiveness of ROD, monitoring results affected by the UNKOWN problem, Nagios instable
Montenegro: Nagios instability, poor ROD performance

possible solutions:
- suspension
- operational responsibility of sites transferred to another Operations Centre
- Nagios setup fixed

ACTION on tiziana to followup this up

*) certification of new NGIs?
Possible mechanisms:
- testing of core NGI services before they start production (in parallel with the integration procedure)
- ad hoc training (remote training?) and certification of ROD team
- pb to solve: who delivers the training? can COD take this task?
- what is the level of existing training material?

ACTION on COD: assess status of documentation and propose how to structure NGI certification

SAGrid was not very responsive

*) monthly meetings: 1 COD meeting at 10:00 the Monday before the OMB
Skype room: all COD managers have to be connected daily