Choose timezone
Your profile timezone:
Description
Agenda
1. Previous meeting minutes accepted?
Was sent out, no comments so far.
See http://agenda.cern.ch/fullAgenda.php?ida=a045911
2. DJRA3.2 status
The deliverable was presented by David to the PEB on Thursday, 13th.
Accepted by PEB. SA1 got some more time to comment. And David got
input on Monday January 17 from Ignacio Blanquer. To be added to the
document by Tuesday 18.
3. MJRA3.5 phase 1 status
Original plan: Send to IanN on Monday, January 17.
Comment: not ready as it is for sending to IanN. To be discussed at
today's JRA3 Status meeting. In general: Jeremy needs more input
from Olle and David, and anyone else in the activity.
4. Planning ahead
Two things on the list:
- the already planned activity deliverables and milestones.
- security modules to be added to gLite.
4.1 Activity tasks: MJRA3.5 phase 2, MJRA3.6, MJRA3.7, DJRA3.3 added to Savannah
#1546 Deliver recommendations document regarding secure credential storage, MJRA3.5 phase 2
Deliver recommendations document regarding secure credential storage.
Responsible phase 1 (PM10): Jeremy Cook, phase 2 (PM15): David Groep. See
https://edms.cern.ch/document/523413/1
**To be done before February 28**
Define the following project data:
Document sent to: Internal review
Name of receiving part:
Date:
Document sent to: Moderator
Name of receiving part:
Date:
Document sent to: PEB
Name of receiving part:
Date:
task #1547 Deliver Framework for policy evaluation accepted in GridPMA policies and
determination of the CA service authorities for EGEE (document). MJRA3.7
David Groep.
**To be done before February 28**
Define the following project data:
Document sent to: Internal review
Name of receiving part:
Date:
Document sent to: Moderator
Name of receiving part:
Date:
Document sent to: PEB
Name of receiving part:
Date:
task #1548 Deliver Security operational procedures (document, first revision). MJRA3.6
Yuri Demchenko.
**To be done before February 28**
Define the following project data:
Document sent to: Internal review
Name of receiving part:
Date:
Document sent to: Moderator
Name of receiving part:
Date:
Document sent to: PEB
Name of receiving part:
Date:
task #1549 Deliver the Global security architecture (document, first revision) DJRA3.3
Olle Mulmo.
Note: this task has deadline June 10. Not end of July. Reason: summer vacations.
**To be done before March 28**
Define the following project data:
Document sent to: Internal review
Name of receiving part:
Date:
Document sent to: Moderator
Name of receiving part:
Date:
Document sent to: PEB
Name of receiving part:
Date:
4.2 Release planning as for today
task #849: Resource access control (PM9->?)
task #845: SOAP over HTTPS (PM5->PM8->?)
task #847: Delegation (PM6-PM8->?)
task #850: Mutual Authz (PM6->PM9->?)
task #851: VOMS java parser library (PM6->?)
task #852: Key mgmt for biomed, phase 1 - scope and plan (PM9->?)
task #853: Dynamic Connectivity Service (?)
task #1348: LCAS/LCMAPS documentation (PM8->PM9->?)
task #1441: Grid user name - from task #1434, project JRA1 Coordination (PM9->?)
task #1452: Helper easy-to-use library for applications to create (delegated) proxy certificates (PM9->?)
4.3 RC1 and beyond, the main subject for the next MWSG (Feb 23-24, CERN)
Follow up of previous meeting:
Old: Cleaning up the Savannah, aiming at getting consistent data (e.g. to get start
date, actual start date, end date and actual end date correct).
New: Has this been achieved?
Old: Ake flagged for a start of planning for beyond RC1.0, the topics at the next MWSG (Feb 23-24).
Aiming at having a JRA3 plan well before (3 weeks, Oscar's comment, i.e. first week of Feb) the
next MWSG. New release tasks will have to have detailed plans in place before accepted as work
items. Esp. there is a need for pre-releases, to get 'early warnings' of delays, and to get early
contact with JRA1 receiving parties. Basically, we need to make use of a \"lesson learned\"
from 2004.
New: DJRA3.1 and DJRA3.2 is leading the way. Olle to use DJRA3.1 to come up with a first list of
modules starting with a meeting on Tuesday with Thomas, Mehran. David to do the same exercise using
DJRA3.2. and people close by. These lists will be merged and used as a starting point within JRA3-Internal
for the first iteration, then MWSG mailing list. Goal: to have a decent list of suggestions, with
names on who to do it, and reason for doing it at least two weeks before the MWSG (Feb 23-24). To be
synchronized with the requirements lists, and JSPG as well. Decisions are made at the MWSG.
5. Old AOB
Old: Olle needs a replacement for the TERENA task force meeting in UK (Janu 27-28). Yuri or IanN,
Olle to follow up. The presentation is already prepared.
New: Has been resolved.
Old: Oscar presented the latest news on VOMS server. To be announced later today as in working state
on the integration mailing list. Patrick reported that there are still a number of problems to
be solved. Joni to find out when Karoly is back from vacation.
New: Status on this?
6. New AOB
6.1 How we work.
Ake still not satisfied with the level of detail in project planning. Might have to rethink regarding
resource planning. To be discussed.
7. Next meeting: Monday January 24, 14.00-15.00
8. Some dates concerning JRA3
8.1 EGEE related traveling, conferences
Jan 20 Ake at CERN, EU review preparation, PEB
Jan 26-27 Ake at CERN, EU review preparation (presenting), PEB
Feb 2-4, Ake at CERN, EU review preparation (presenting), PEB
Feb 9-11, Ake at CERN, EU review (presenting), David (Q&A)
Feb 23-24, Ake, (and who else?) at CERN, 5th MWSG
Apr 18-22, Ake (and who else?) in Athens, on the 3rd EGEE conference
8.2 Vacations, not working on EGEE
Mar 9-14, Ake on vacation