TMB minutes 14.10.2009 taken by JT
present : Francesco G, John White White, Oliver, Maite, the
Traylenator, Templon, Patricia M.L., Markus
minutes of previous meeting : Francesco has a correction, to be
discussed later (?)
Tasks:
SAM for MPI - tests adapted according to TF, now in validation, TF
needs to check results, half of sites are failing.
Autopublish space reservation : TMB decides to close task,
successfully handled.
#8953 - closed, comment by Christoph
Subclusters - can be published by CREAM CE with no problems. Need
comment from Francesco on #37911 (not clear if this is a task or bug
number)
-------------------------
middleware packaging proposal : See the Traylenator's slides.
- questions raised about motivation for proposal plus answers
- JT : need to make sure tarball still works (Traylen - it will)
- Jan Just comments : strongly against moving to /usr
- Steve T - main point is that all files are owned by a package.
- FG asks questions about how easy it is to move packages at config
time : A: it's work, but not difficult
- FG proposes to start some actions now, like using rpmlint
- discussion about /usr vs /opt/glite
move to OS packages (UMD) will REQUIRE /usr so strange to forbid it
now
FG suggests : file ownership and /etc/ files now (glite 4),
postpone hard decision on /usr vs /opt/glite for UMD
TMB agrees
glite 4 decisions discussion:
poll group present for input.
question : should we be able to upgrade (rpm -U) from glite 3.2 ->
4.0?? providing such an upgrade path requires more work.
- need to poll sites on this point (JT : can we ask Daniele C to do
a broadcast about it?)
- possible service by service decision.
eg DPM has an upgrade path but CE needs to be installed from
scratch ...
release process : TBD at later meeting.
[JT leaves, John White takes over]
OK: What does the date due in the workplan mean now?
FG: Right now it's "to certification"
ie. The date that we put the component or node INTO certification.
JW: At the last TMB... this date discussed.
OK: Now it should be either "to production" or "to PPS"
FG: Right now it cannot be done as the certification time is
not know yet... For now, we stay with original plan
. ie. The date reflects the date it will enter certification.
OK/FG: Once we have PTs (established) then these
dates are "post-certification"
OK: Comment: If we take this (?) at face value then we have eight
releases on Oct 31st. Then need to negotiate these dates with
JRA1/SA3.
FG: 1. These dates are not realistic.
2. The WP was done in order to tell central team what to
expect.
3. Not everyone understands this is the way to work.
FG: Changing the way of working is not quick.
OK: For the scheduling of releases... a two week warning is needed to get in
contact with partners for assignment of effort?
OK: Anything else on the "status of PTs"?
ACTION: JRA1: Review these dates on the Work Plan.
FG/JW: OK. We will do this over our usual channels.
AOB:
Vangelis Floros: (From the telephone): What about gLite 3.1
after the release of 4.0?
OK: We should follow the usual procedure as before that after a
service is released (no problems in production)
on the next platform, we should discontinue the support
(modulo security updates) for the previous after two months.
OK: Any other AOB?
(NO). Early finish for the GDB.
There are minutes attached to this event.
Show them.