Weekly Operations' Meeting Action List
Status as of 08 January 2007
Due Date colour key:
|
Red: action is overdue |
|
Yellow: action is due at or before next meeting |
|
White: action is due some time after the next meeting |
Open Action Items
|
Number |
Description |
Assigned To |
Status |
Due date |
|
67 |
Timescale for move to Torque2? Progress on 2006-10-30: In progress. Progress on 2006-11-01: Expected to be in certification within 2-3 weeks. Progress on 2006-11-20: The counter was restarted last Friday, so it will go to PPS in 2-3 weeks from now. Estimated timeline: in PPS by ~15th Dec Progress on 2006-12-18: it was released to PPS on Monday, and removed on Tuesday due to a critical problem found. |
OCC |
In progress |
15/12/06 |
|
70 |
Conclude on "Policy for security updates of third party software". The gLite integration team policy is: the external packages are not guaranteed to be maintained. They are provided for convenience. They are maintained by their providers. The reality is that they will be maintained on best effort. To be clarified with the security team. Progress on 2006-11-27: being discussed with OSCT and SA3 Progress on 2006-12-04: This item was discussed during the meeting. Waiting for SA3 to create the final list of external packages which need to be maintained. |
OCC |
In progress |
15/01/07 |
|
75 |
Provide DPM to ATLAS for testing purposes in PPS service. Progress on 2007-01-08: 2 DPM nodes are now intalled at CERN PPS site. In progress |
Nick |
In progress |
15/01/07 |
|
76 |
VOs to update their mailing lists of grid users so that grid operational messages are communicated to all users when necessary. Progress on 2007-01-08: The affected VOs have been contacted and the mailing lists updated. The action can be closed. |
OCC / VOs |
In progress |
15/01/07 |
|
1 |
Document VO expiration procedure and associated error message when it happens. |
OCC |
New |
15/01/07 |
Closed Action Items
|
Number |
Description |
Assigned To |
Due date |
Date closed |
|
71 |
ATLAS to check if they know of any conflicts between SL kernel version 2.6 and either the application software or the middleware. Progress on 2006-12-11: Atlas was not present at the meeting, we’ll check offline Progress on 2006-12-18: Alessandro DeSalvo says in respect of the ATLAS application there is no problem. The only issue might raise (but not sure at all) from the Oracle client in the production system (which anyway has only 4 instances in the all Grid) and the Data Management Clients in the VOBOXES. So as long as this discussion does not refer to VOBOXes, this is OK. The VOBOXes (only 10 nodes for atlas, one at each T1) will need to be considered some time soon. I will get in touch with Miguel for this. The action can be closed. |
Simone |
11/12/06 |
18/12/06 |