TMB Meeting
Description
Dial-in numbers: +41227676000 (English, Main)
Access codes: 0173115 (Leader) 0183088 (Participant)
Leader site: https://audioconf.cern.ch/call/0173115
Participant site: https://audioconf.cern.ch/call/0183088
Task List: https://savannah.cern.ch/task/?group=tcg
TMB Minutes 11/11/09
James (JC), Oliver (OK, chair), Patricia (PM), Vangelis (VF), Nick (NT)
JC:
Explained the three stage lifecycle for the OAT projects - 'development
complete', 'test complete' and 'deployment complete', each of which
represents a milestone.
test complete = ready to deploy
deployment complete = done (not expected before the end of the project
in some cases).
Sometime plans are affected by certification timescales, eg APEL.
In many cases, we have 'public' testing, still sometimes rough in
packaging etc but we can check functionality.
Have asked for test plans before the testing phase - still have no test
plans. These can be very simple!
Haven't yet defined the next development cycle, ie post production
experience.
NT - just trying to get basic functionality out to begin with
JC - has been hard to get the information on dependencies across tools,
eg dashboard need nagios notifications, even at the dev stage. Thus some
of this isn't in the diagram
And what are prerequisites for retiring things? Eg until we replace SAM,
we can't replace gstat. May have to start turning things off just to
discover the dependencies.
Have found it difficult to extract information from the CIC portal team.
Lots of mail exchange. Unwillingness to provide timescales until they
have all necessary information. They are not the only ones not meeting
their milestones, but now they won't supply milestones.
So try to get 'relative' timescale (3 weeks after X)...
Other problem - arrival of unrequested functionality (without the
relevant 3 plans, ie not following any OAT procedures). 'new central
dashboard in production'. This work could be slowing down more important
work towards established goals.
OK - where in plan do you see something working end to end?
JC - they think they will provide the regional package, deployed by rocs,
by December. But what was asked for was a central package that would
work with Nagios.
JC - sometimes CIC portal team are not coming to the OAT meetings (not
present at last two). Maybe they think they know what needs to be done?
NT - very difficult with dependencies, suddenly we get them.
OK - what's your confidence in the dependencies now
JC - most problems i expect in the deprecation dependencies.
NT - still a concern with the CIC portal, is that they are last in the
chain and so they suffer from other delays. this is why we really need
to know their dependencies so we can see the effect on them of the delay
in other components. For OPS dashboard, info is low confidence.
JC - I think in 2 weeks we'll have a lot better idea on the testing
duration of various components. For some, deployment will be quite fast,
because of existing deployments (just upgrade nagios) or because the
things are central. Only one ROC (Russia) doesn't have a regional nagios
installation, but they are working on it.
There are minutes attached to this event.
Show them.