Choose timezone
Your profile timezone:
PTB Meeting
→
Europe/Zurich
Teleconference
Teleconference
Description
PTB meeting, 14:00-16:00, 8 March, 2011
Calling details: skype test conferencing service in Lund (call mailmagnes in skype)
Proposed agenda:
----------------
- Approval of previous meeting notes, follow up on actions
- Report from area leaders
- EMI-2 workplan preparation: timeplan
- Task forces
-- longer term plans for service monitoring and remote management
-- mandate review of cloud task force
-- AoB
------------------------------------------------------------
Regular PTB meeting, 14:10-16:07, 8 March 2011
Present: Morris, Patrick, Laurence, John (joined 14:20), Marco, Balazs (notes)
I) Approval of previous meeting notes.
The meeting notes from the 15/02/2011 regular PTB meeting got approved.
II) Actions follow up
* Balazs: schedule the Cloud task force mandate and the longer term service monitoring and remote management plans for discussion at the next PTB
done
* Morris: to populate the service monitoring TF with "nagios contacts" of the EMI product teams.
partially done, ongoing.
* Area leaders: feedback on the EGI Quality Criteria documents: 23 February
done.
III) Report from area leaders
-Compute: no news, middle/longer term activities are progressing according to schedule
Data: no real news, middle/longer term activities are progressing according to schedule. Balazs asked about delegation working group, Patrick will check it later.
Security: the agreement on SAML/XACM profiles are out in few weeks, unfortunately without concrete data and compute attributes. AAI use-cases are got reduced. The common auth library is basically "there".
Infrastructure: medium-term plans that will affect EMI-2 are:
Infosys client harmonization, resource level info service harmonization, EMI Registry as a new service, the EMI messaging product (broker network)
III) EMI-2 workplan preparation: initial time plan discussion
The facts:
----------
- DNA1.3.2 - Technical Development Plan, officially due March
- DJRA1.[1-4].2- Compute/Data/Security/Infra Area Work Plan and Status Report, officially due April
- DJRA1.[5-6].2 Standardization/Integration Work Plan and Status Report, officially due April
- Development plan: unclear if such a separate document will be needed for EMI-2
- the project management has said that two month of delay would be tolerated, due to EMI-1 overlaps.
- HARD DEADLINE: The workpan must be ready by the Project Review, that is latest by 10 June.
Work to be done:
----------------
- agree upon the scope of different documents and the their structure
- process requirements
- review existing high level objectives
- define new high level objectives
- review component table
- review product teams
- prepare consolidation plans including drastic component phase out (!)
- approve consolidation plans
- draw EMI "architecture"
- define area workplans AND break it down to PT level
main working tool: EMI trackers (requirements and devel)
Timing:
------
March: templates, structure of the documents, identify reviewers
April: real work starts here, requirements, high level objectives, area harmonization plans
May: put everything together, work out the low-level task details, write the deliverables
June: quick internal project review of the deliverables
Rather intensive work is expected in April/May. Specific time slots will be reserved on the next PTB meeting.
Balazs reminded area leaders that THIS is the time when real converence/harmonization/simplification can be planned. EMI-2 is our only possibility for real changes.
Balazs asked if anybody would object: answer was "not yet" :)
III) Task forces
- longer term plans for service monitoring and remote management
postponed for next meeting
- mandate review of cloud task force
https://twiki.cern.ch/twiki/bin/view/EMI/EmiJra1T5TaskForceCloudandVirtualization
The wiki page of the task force got updated. The cvloud/virtualization team s expected to deliver a report, the EMI cloud position/architecture soon (A draft document exists, read by Laurence and Morris)
VIII) AoB
- next meetings
The next PTB meeting will be on 29th March.
-There will be no F2F PTB in Vilnius.
- EMI all-hands
While trying to bootstrap the program preparation for the 2d EMI all-hands, it turned out many people find the selected date very bad. Balazs will immediately forward this message to project office.
- During the workplan topic, there was a discussion about deputies. It is up to the area leader to go for a deputy or not to go for it.
ACTIONS
--------
* Balazs reports the all-hand date problem to PO
Regular PTB meeting, 14:10-16:07, 8 March 2011
Present: Morris, Patrick, Laurence, John (joined 14:20), Marco, Balazs (notes)
I) Approval of previous meeting notes.
The meeting notes from the 15/02/2011 regular PTB meeting got approved.
II) Actions follow up
* Balazs: schedule the Cloud task force mandate and the longer term service monitoring and remote management plans for discussion at the next PTB
done
* Morris: to populate the service monitoring TF with "nagios contacts" of the EMI product teams.
partially done, ongoing.
* Area leaders: feedback on the EGI Quality Criteria documents: 23 February
done.
III) Report from area leaders
-Compute: no news, middle/longer term activities are progressing according to schedule
Data: no real news, middle/longer term activities are progressing according to schedule. Balazs asked about delegation working group, Patrick will check it later.
Security: the agreement on SAML/XACM profiles are out in few weeks, unfortunately without concrete data and compute attributes. AAI use-cases are got reduced. The common auth library is basically "there".
Infrastructure: medium-term plans that will affect EMI-2 are:
Infosys client harmonization, resource level info service harmonization, EMI Registry as a new service, the EMI messaging product (broker network)
III) EMI-2 workplan preparation: initial time plan discussion
The facts:
----------
- DNA1.3.2 - Technical Development Plan, officially due March
- DJRA1.[1-4].2- Compute/Data/Security/Infra Area Work Plan and Status Report, officially due April
- DJRA1.[5-6].2 Standardization/Integration Work Plan and Status Report, officially due April
- Development plan: unclear if such a separate document will be needed for EMI-2
- the project management has said that two month of delay would be tolerated, due to EMI-1 overlaps.
- HARD DEADLINE: The workpan must be ready by the Project Review, that is latest by 10 June.
Work to be done:
----------------
- agree upon the scope of different documents and the their structure
- process requirements
- review existing high level objectives
- define new high level objectives
- review component table
- review product teams
- prepare consolidation plans including drastic component phase out (!)
- approve consolidation plans
- draw EMI "architecture"
- define area workplans AND break it down to PT level
main working tool: EMI trackers (requirements and devel)
Timing:
------
March: templates, structure of the documents, identify reviewers
April: real work starts here, requirements, high level objectives, area harmonization plans
May: put everything together, work out the low-level task details, write the deliverables
June: quick internal project review of the deliverables
Rather intensive work is expected in April/May. Specific time slots will be reserved on the next PTB meeting.
Balazs reminded area leaders that THIS is the time when real converence/harmonization/simplification can be planned. EMI-2 is our only possibility for real changes.
Balazs asked if anybody would object: answer was "not yet" :)
III) Task forces
- longer term plans for service monitoring and remote management
postponed for next meeting
- mandate review of cloud task force
https://twiki.cern.ch/twiki/bin/view/EMI/EmiJra1T5TaskForceCloudandVirtualization
The wiki page of the task force got updated. The cvloud/virtualization team s expected to deliver a report, the EMI cloud position/architecture soon (A draft document exists, read by Laurence and Morris)
VIII) AoB
- next meetings
The next PTB meeting will be on 29th March.
-There will be no F2F PTB in Vilnius.
- EMI all-hands
While trying to bootstrap the program preparation for the 2d EMI all-hands, it turned out many people find the selected date very bad. Balazs will immediately forward this message to project office.
- During the workplan topic, there was a discussion about deputies. It is up to the area leader to go for a deputy or not to go for it.
ACTIONS
--------
* Balazs reports the all-hand date problem to PO
There are minutes attached to this event.
Show them.
The agenda of this meeting is empty