Extended PTB Meeting

Tuesday 14 Sept 2010, 09:00 → 11:00 Europe/Zurich

room Derkindern (Amsterdam EGI-TF)

Extended PTB meeting

Duration: 9-11am Tuesday 14 September

Calling details:  skype test conferencing service (call mailmagnes in skype)

 

Proposed agenda:
----------------

a) clarification of the organization of the EMI technical management:  technical areas, area leadership, product teams, TD, workplans, PTB vs. JRA1, JRA1 vs. SA1,2, procedures, rules, important deadlines related to technical workplans and releases

b) bootstrap the "architecture roadmap" work.

Extended PTB meeting at the EGI-TF Amsterdam, 9-12:45 Tuesday 14 September, present: Morris, Laurence, Patrick, Massimo (on skype), Balazs (notes) invited external participants: Alberto, Florida (joins later) away: John I) clarification of the organization of the EMI technical management: technical areas, area leadership, product teams, TD, workplans, PTB vs. JRA1, JRA1 vs. SA1,2, procedures, rules a) important clarifications in the deliverable procedures: *technical documents need PTB approval before internal release *first round of reviewers should come within the project *followed by an optional external review *reviewers are proposed by WP leaders and need to be approved by PEB *running deliverables, if possible, should be reviewed internally as well b) area leaders: *they are involved in mid/longer term strategic planning done in PTB *they are engaged with coordination and execution of the workplan via JRA1 *Area leaders should be aware of all PTs in their area, including those that only active in SA1. Area leaders coordinate the PTs in the execution of the workplan. c) Workplan documents: * Technical development plan (DNA1.3.1) **content: tech objectives (there), "high level view, presentation of the objectives, including a time chart (to be added), EMI architecture (will not be part of the first release of DNA1.3.1) delivery date: end of September for internal review * Area workplans (DJRA1.x.x) (compute, data, infra, security) **content: these cover only year one. **delivery date, status: *** compute: under external review, needs internal, ***data: under external, missing internal, ***security: no review started yet ***infra: no final doc yet, not yet released for internal review *Area development plans **content: detailed development plan for all the PTs that describe the development tasks per PT AND component part of EMI-1 release **it is a more detailed and updated version of DJRA1.x.x. **format wise it is not a deliverable, it can be a wiki page too. **status: wiki version exists for data and compute, unclear security and infra **these documents are needed for JRA1 and controlled by JRA1. These are not a PTB documents. **due date: must be finalized by end of October. * Release plan **content: a schedule (freeze date, testing slot, rc1, rc2, rc3) and also list of components (e.g. voms-1.4.3) **functionality of a release is decided in the PTB **SA1 is responsible for the release plan but they need input from PTB (for the content) *Architecture roadmap **content: current (EMI-0) architecture (relation and interaction of components), how the architecture will evolve by the end of EMI **the architecture and its planned evolution is NOT a release plan **format: it will be a separate document, some part of it will be added to the next release of the DNA1.3.1 (due month 11) **creation of EMI architecture is postponed till November. **the architecture discussion does not affect the EMI-I release, most of the convergence, cross-area work is expected in year two, for EMI-2 **decision to run a 2 days meting in Cern in November. All area leaders must participate. II) bootstrap the "architecture roadmap" work. There was no time for that. A "architecture" F2F two-day-meeting with the area leaders, TD, deputy TD (that is the PTB) will be organized in November. Date must be fixed within a week. Location: cern