PTB meeting, 10:06-11:14, 19 June 2012 via skype
Present: Jon, Cristina, Patrick, John, Laurence
Not showed up: Marco,
I) 2nd EMI project review outcome and its consequences
Balazs, Jon and Patrick informed the PTB about the 2nd year review:
- The review went well
- Technical work was well received
- Security area was seen as a problematic one due to missed milestone and late STS work.
- The reviewers might have developed a wrong ide that EMI had no security (architrecture) and it treats security as a last priority.
Possible corrective actions:
- quickly finish the milestone
- prepare a "white paper" on EMI security
- really (re-)allocate efforts to STS even on the cost of sacrificing the maintenance of some other products (ARGUS vs STS)
II) PTB decision on gLite Job management Product Team split to CREAM and WMS PTs
In absence of Marco Cristina presented the proposed spilt:
The two new PTs:
-WMS: to be lead by Marco
-CREAM: to be lead by L. Zangrando
PTB unanimously approved the split.
III) PTB decision on the proposed new EMI product: AMGA manager
Balazs presented the AMGA request to introduce a new product, the AMGA gui called Amga Manager to the EMI software portfolio..
Cristina sees no problem from release management of point of view
Patrick sees no problem from data area point of view
AMGA manager was unanomously approved as a new EMI product with the following conditions:
- it will be a new product with its own release and certification cycle.
- The work on the amga manager should be done on the existing budget/effort, no new resources to be allocated to the AMGA PT.
- No major new development is planned for the product, the main activity will be under SA1 (maintenance, proactive support)
IV) PTB approval of EMI agreements/specs
PTB has accumulated a growing list of tech documents that are waiting for PTB "stamp". Some of them:
-- CAR
-- Common parallel execution framework:?
-- Compute Client consolidation plan
-- EMI datalib
-- EMI Delegation
It is the area leader's primary responsibility to review, follow the preparation and check the final documents. The other PTB members are responsible to check if the agreement does not violate overall EMI view.
As a corrective action to progress on the agreements it was decided that from now the affected area leaders should cast a real vote while the others are also requested to explicitly state if they think a document does not affect their area.
A new round of voting will start soon. The goal is to finish with all the agreements by the ed of the summer.
V) Dev tracker update with Y3 workplan
Balazs and Jon updated and populated the dev tracker with all the Y3 objectives. Next step is to add/create the product team level dev tasks. Area leaders were asked to provide task list for their areas AND for the relevant cross-area objectives in the format:
- task title, involved PT, short description, due date, related objective id
While discussing the dev tracker items some area leaders expressed their view on the usage of the tracker as "it is a massive overhead" or "only four month left, why to bother with tracking tasks?"
Balazs tried to explain that the dev tracker actually did work out as a useful tool in Y2 and now with Y3 nothing new introduced, only the new tasks are to be added. And these new PT tasks are supposed to be already defined as part of the area workplans.
Balazs and Jon aims at finishing the tracker update by the end of June, as it was promised at the Hamburg all-hands.
VI) AOB
- summer operation of the PTB
due to different vacation plans the PTB will operate in a limited mood during the summer. We try to run one meeting in July and August, if possible. next meeting: 17 July (tentatively)
vacation plans:
Patrick: till 7th July, 16.7 - 20.7 in Dubna
Balazs: 22 July - 14 August
Jon: September
John: july 27 to august 23
Cristina: August 13-27,
Laurence: no planned longer vacations, long weekends here and there
ACTIONS
-------
- Marco: create new product teams in the wiki and provide all the necessary info (in the twiki
https://twiki.cern.ch/twiki/bin/view/EMI/EmiProductTeams)
-Cristina: to schedule the new AMGA manager to be released with a coming EMI 2 update.
-Area leaders to send the product team task list: next week Tuesday, 26th June