Choose timezone
Your profile timezone:
PTB Meeting
→
Europe/Zurich
Teleconference
Teleconference
Description
PTB meeting, 10:00-12:00, 29 November, 2011
Calling details: direct skype conference call
Proposed agenda:
----------------
- Follow up
- RfC and release plan approval
- EMI-2 development status check
- Report from EGI-TCB
PTB meeting, 10:00-11:40, 29 November 2011
Calling details: skype direct call
Present: Marco, Jon, Balazs (notes), Cristina, Laurence, John
Excused: Patrick
0) Follow up
-Approval of the meeting notes from the previous PTB meetings (9.11.2011):
Notes are approved.
-Actions: checked, open ones are carried over, see below
1) RfCs and release plan: PTB approval
Cristina presented the minor and revision product updates scheduled for EMI Update 11, 15/12/2011 (attached to the indico)
PTB endorsed the plan.
Regarding release management Balazs asked how unchanged products going to be handled with EMI 2, are those going to be taken from EMI 1 and simply re-released as part of EMI 2?
answer: yes, those products will be re-released.
another question was about release tracker entry for such products: Cristina proposes to have a release tracker entry for everything.
2) EMI-2 development status check
Balazs briefly presented the not really bright EMI 2 status. Lots of dev tasks, even top priority ones, will not be finished by the code freeze.
big question: what to do with incomplete development?
Cristina: if the product is certified and not breaking anything, it may be ok to insert the product later to the EMI 2 during one of the release candidate cycles. Cristina thinks she can manage such process. New products can be provided in a later release candidate.
John: also thinks that accepting stuff later is the only reasonable way to go. supports PTs to be allowed to add products into later release candidates.
Marco: supports the more flexible code-freeze approach.
Laurence: OK.
3) Report from EGI-TCB
Balazs briefly presented the new requirements we received from EGI:
- handle full storage elements
- need to easily update files in the entire storage system
- IPV6 compliance
- be able to live together with strict restricted proxy lifetime of max 24 hours: This means, requires ability for automatic proxy renewal in all affected EMI services.
Balazs also informed PTB about the current state of the EGI federated Virtualization task force. The task force works openly, everything is here:
https://wiki.egi.eu/wiki/Fedcloud-tf:FederatedCloudsTaskForce
Their main outcome will be the Blueprint, that EMI should keep an eye on.
4) AOB
- Balazs brought up the github requirement, i.e. to have eery new EMI common development in github. Now the idea is accepted though it was noted by John that things will slow down and the transition will cost few weeks
- quick check on the user community forum contributions:
no interest for dedicated security sessions.
no info on security submissions
no information about compute submission
a STORM paper is planned, no other info from data area
no plans for submission from infra
- next PTB meeting 13 December: will be a long meeting with main agenda to decide upon EMI 2 RC0 content
ACTIONS
-------
- Laurence: come with a list of necessary standard compliance test suits for the area
- Balazs: enter security requirements (see 9.11.2011 PTB meeting) to the req. tracker
- Cristina: prepare a table that lists all the EMI 1 and EMI 2 products with their versions.
- Jon, Balazs, Cristina: Finalize release tracker for EMI-2. deadline: 9th December
Calling details: skype direct call
Present: Marco, Jon, Balazs (notes), Cristina, Laurence, John
Excused: Patrick
0) Follow up
-Approval of the meeting notes from the previous PTB meetings (9.11.2011):
Notes are approved.
-Actions: checked, open ones are carried over, see below
1) RfCs and release plan: PTB approval
Cristina presented the minor and revision product updates scheduled for EMI Update 11, 15/12/2011 (attached to the indico)
PTB endorsed the plan.
Regarding release management Balazs asked how unchanged products going to be handled with EMI 2, are those going to be taken from EMI 1 and simply re-released as part of EMI 2?
answer: yes, those products will be re-released.
another question was about release tracker entry for such products: Cristina proposes to have a release tracker entry for everything.
2) EMI-2 development status check
Balazs briefly presented the not really bright EMI 2 status. Lots of dev tasks, even top priority ones, will not be finished by the code freeze.
big question: what to do with incomplete development?
Cristina: if the product is certified and not breaking anything, it may be ok to insert the product later to the EMI 2 during one of the release candidate cycles. Cristina thinks she can manage such process. New products can be provided in a later release candidate.
John: also thinks that accepting stuff later is the only reasonable way to go. supports PTs to be allowed to add products into later release candidates.
Marco: supports the more flexible code-freeze approach.
Laurence: OK.
3) Report from EGI-TCB
Balazs briefly presented the new requirements we received from EGI:
- handle full storage elements
- need to easily update files in the entire storage system
- IPV6 compliance
- be able to live together with strict restricted proxy lifetime of max 24 hours: This means, requires ability for automatic proxy renewal in all affected EMI services.
Balazs also informed PTB about the current state of the EGI federated Virtualization task force. The task force works openly, everything is here:
https://wiki.egi.eu/wiki/Fedcloud-tf:FederatedCloudsTaskForce
Their main outcome will be the Blueprint, that EMI should keep an eye on.
4) AOB
- Balazs brought up the github requirement, i.e. to have eery new EMI common development in github. Now the idea is accepted though it was noted by John that things will slow down and the transition will cost few weeks
- quick check on the user community forum contributions:
no interest for dedicated security sessions.
no info on security submissions
no information about compute submission
a STORM paper is planned, no other info from data area
no plans for submission from infra
- next PTB meeting 13 December: will be a long meeting with main agenda to decide upon EMI 2 RC0 content
ACTIONS
-------
- Laurence: come with a list of necessary standard compliance test suits for the area
- Balazs: enter security requirements (see 9.11.2011 PTB meeting) to the req. tracker
- Cristina: prepare a table that lists all the EMI 1 and EMI 2 products with their versions.
- Jon, Balazs, Cristina: Finalize release tracker for EMI-2. deadline: 9th December
There are minutes attached to this event.
Show them.
The agenda of this meeting is empty