PTB meeting, 10:00-12:07, 19 July, 2011
Present: Cristina, Patrick, Laurence, John, Morris, Marco, Balazs (notes)
Excused: Jon (vacation)
1) News from the 1st Project review, reviewer recommendations
Balazs gave further details about the 1st Project Review. Official review recommendations are not yet received.
2) The new project structure and its effect on PTB operation
Short presentation of the streamlined JRA1/PTB management layer.
PTB is the main Technical Board, the technical decision taking body of EMI. Important decisions should be taken or at least endorsed by PTB.
PTB, at the same time, is also acting as a day-to-day management/execution body responsible for monitoring ongoing developments (Jon's main area)
Welcomed Cristina and Jon to the PTB.
The JRA1 management handover has been completed, since last week Jon and Balazs run the JRA1. The Q% is still prepared by Morris.
Lots of (administrative) details are not yet clear, more info is expected after next week PEB.
3) EMI development tracker and development roadmap
Balazs emphasized the central role of the dev tracker in the 2nd and third EMI year. The tracker to be filled with DNA1.3.2 objectives AND corresponding PT-level development tasks by 2nd week of August. Balazs and Jon will populate the tracker first week of August but they may need active contribution from area leaders as well (separate mails to be posted)
The dev tracker is to be managed by PTB. Everybody has write access.
Roadmap: based on the dev tracker entries, an "EMI Roadmap" will be prepared and kept up-yo-date by Balazs
4) RfCs and the PTB's role in approving emergency releases, RfCs
According to the official EMI policies (Change and release managemet) the PTB has a major role in approving RfCs and releases (minor, major, emergency). PTB can delegate tasks to release management.
Long discussion took place about policies (who creates those, so on..).
Then, going back to the original topic, the following distribution of responsibilities were agreed:
- RfCs are handled by Cristina. Only "critical/emergency" RfC need PTB endorsement. For those, Cristina will send email to PTB asking for approval.
Generally, an RfC should always be in line with the EMI dev plan and objectives.
- Minor releases are handled by Cristina. She will only post the (updates) of the release schedule to the PTB for approval.
- Major releases are taken care by PTB, PTB decides on a high lvel what goes into the next major EMI release
- Emergency releasas need PTB endorsement. A request for an emergency release are posted to PTB.
- PTB approval and endorsement is achieved if no veto/rejection is made. Cristina always specifies the deadline for such veto. Minimum one working day time slot is required.
5) EMI Emergency release for WMS
After the explanation of the reason for the emergency release the PTB endorsed the request.
The main reason for the emergency release is "political", so that the WMS can make into the UMD-1.1 release. The normal release cycle would not make it possible.
6) Feedback from Santander, IberGRid conference
Morris reported about the feedback. In particular the following two items:
- "Clients for many OS/platform versions"
- "different clients using the same SRM get different results (aka no standard!)"
The above two requests originates from EGEE era. Spanish (?) people feel that their request is not taken seriously.
Morris will take a pro-active role and ask them to submit a ticket on the SRM problem.
7) Task Forces
Discussion about the nature, role, need, purpose of task forces. Task force is a convenient and necessary "working unit" within EMI for cross-PT/area/wp activities. These are found useful and in the future more systematic approach will be taken to create/monitor/close down task forces.
Task Force info (for every task force, not only JRA1) is (will be) kept here:
https://twiki.cern.ch/twiki/bin/view/EMI/EmiTaskForces
Marco commented that he was concerned about the passivity of many of these task forces, as a sign of no-work. Balazs agreed.
Everybody was happy with a more controlled task force approach for the 2nd year.
7a) The MPI task force was created, PTB approved. Marco will provide the task force details.
7b) The compute accounting group (task force in the future) has a problem because of its chair resigned. Marco is looking for a new leader. Compute accounting agreement is a high priority "almost due" objective.
- Follow up and status of the EGI high priority requirements:
EMI req tracker: https://savannah.cern.ch/task/?group=emi-req
7c) Nagios probes
Everything seems to be settled by now. Emir (from EGI) is the TF leader, all PTs have delegated responsible people, mailing list is set up. Balazs will create dev tracker entry for every PT.
8) Infosys consolidation: ERIS
The Resource-level infosys consolidation needs to be bootstrapped. A task force was created with Laurence as the leader and Mattias Ellert, Shiraz, Paul Millar members. The ERIS TF will deliver technical proposal about an EMI Resource-level infosys service consolidation. Then, the PTB will decide on new PT/merge PT/?? option.
report due: end of August
-- Discuss (endorse/reject) the new set of EGI requirements
- Infosys consolidation: ERIS (?)
who will deliver the product?
ERIS task force: Laurence, Mattias Ellert, Shiraz, Paul Millar
due: 10-12am Tuesday, 30 August
9) EGI Requirements:
run out of time, therefore off-line work was agreed:
- Balazs takes care of the existingf requirements, will try to report on some progress. If needed, the ticket will be assigned to very specific person and that person must also react on the ticket.
- Concerning the new set of requirements (https://rt.egi.eu/guest/Ticket/Display.html?id=1808), Patrick wil go through those tickets and propose (via email) accept/reject. Accepted requirements wil be added to EMI req. tracker.
10) AoB
-next meeting: 30 August, 10-12 Tusday morning
-availability: please use the out of office page, now it is (more) secure and only EMI project members can see your posting:
https://twiki.cern.ch/twiki/bin/view/EMI/EmiOutOfOffice
ACTIONS:
--------
- All: check the deliverables and milestones and post any simplification idea.
- Cristina and Balazs: formulate the PTB's role in RfC and Release endorsement. Send outcome to SA2, Maria
-Cristina: Better define what is an emergency release, send info for SA2, Maria
- Morris to contact Iber Grid people and ask them to report the details of the SRM client problem to GGUS.
- Laurence: start the ERIS TF, inform the ERIS TF members.
- Patrick: go through the Data requirements