PTB meeting 10:05 - 11:24 on skype
Present: Patrick, Marco, Jon, Laurence, John (joined at 10:40)
Excused: Cristina
0) Release updates by Cristina
Cristina posted the release reports earlier:
https://dl.dropbox.com/u/34258911/ptb_reports/PTB_report_20_11_2012.docx
https://dl.dropbox.com/u/34258911/ptb_reports/PTB_report_20_11_2012.pdf
i) Milestones, deliverables
- Security architecture assessment milestone.
Progress can be followed at the dedicated page:
https://twiki.cern.ch/twiki/bin/view/EMI/EmiJRA1SecArchDoc
Balazs would like to see the overview section written first. John comments that no idea who would write that section, "everybody" from the security area was asked to contribute.
- MJRA1.18 "Data standard milestone"
done by Patrick, being processed by the PO.
- MJRA1.17 "Test suits": delayed to February
- MJRA1.18 "Standard compliance status report"
Will be delivered in December. Weizhong was asked to send the list of PTs who did not yet provide sufficient information.
- MJRA1.4 - Successful computational usage of emerging computing models
due in December, Marco sees no problem with it.
- MJRA1.11 - Easier end-user access capability to EMI components in place
Most probably will be delayed till January.
- MJRA1.15 - Service monitoring and management
Will be delivered in December.
- MJRA1.19.3 - Integrated EMI Major Release Candidates
To be written in December, after the first release candidate.
- Area reports (deliverables)
no plan to bring them earlier. BUT Marco was asked to prepare the compute area Y3 progress report already in February/March because of the large number of cancelled compute area tasks/objectives.
ii) EMI 3 status: development tasks for EMI 3 release and for post-EMI
Balazs explained the overall status of the open dev tracker tasks. There are two categories of task,
a) late tasks that should be completed and released with EMI 3. These are all "problematic" and the task owners must urgntly provide estimated delivery date in the tracker. There are around 40 such tasks
here is the list of EMI-3 open tasks:
http://bit.ly/TdeSc8
b) "post-emi" tasks, these development activities are not expected to be released with EMI-3 though a dev snapshot release is possible. Here the PTs are requested to provide up-to-date progress info in thet racker (percentage complete)
here is the list of post-emi tasks:
http://bit.ly/T8YOoE
iii) Latest Questions from EGI
1) Clarify the requirement #881 (https://rt.egi.eu/guest/Ticket/Display.html?id=881)
Patrick kindly agreed to get in direct contact with the IBERgrid people and explain them his understanding of the request and even present a solution.
2) Report on the scalability limits of top-level BDII (e.g., how many site level BDII can it support?)
Laurence provides a linear extrapolation based on the current top-bdii numbers of 400 sites.
3) Provide Infosys evolution document: describe how the different EMI infosys services (EMIR, BDIIs) are to be used together for information discovery, monitoring, etc...
Laurence starts writing down what we have now.
4) Report on progress with HA CREAM (https://rt.egi.eu/guest/Ticket/Display.html?id=2279)
Marco sends answer next week
5) Report on how non-gridftp EMI SEs could be used in file transfer services (globusonline, FTS), report on the third-party transfer work with webdaw/https.
Patrick provides a "what is available/will be possible" based on EMI technologies" short description regarding file transfer services.
iv) aob
Next meeting will be on 18 December.
ACTIONS
--------
- Jon/Weizhong was asked to send the list of PTs who did not yet provide sufficient information for the "standard adoption" milestone.
- Patrick communicates with IBERGRID regarding the #881 ticket
- Laurence to provide top-BDII scalability performance numbers based on linear extrapolation.
- Laurence starts writing the Infosys evolution document
- Marco reports on the HA CREAM features to be released with EMI-3
- Patrick provides a "what is available/will be possible" based on EMI technologies" short description regarding file transfer services.
There are minutes attached to this event.
Show them.
