PTB Meeting

Tuesday 15 Feb 2011, 14:00 → 16:00 Europe/Zurich

Teleconference

PTB meeting, 14:00-16:00, 15 February, 2011 Calling details: skype test conferencing service in Lund (call mailmagnes in skype) Proposed agenda: ---------------- - Approval of previous meeting notes, follow up on actions - News from PEB, EGI - Report from area leaders - Platforms: PTB decision about the debian flavour - quick check on the progress of the task forces -- service monitoring TF -- EMI-UI (also clarification concerning WN, VOBOX) TF -- other TFs - EGI Quality Criteria -- Compute Capabilities Quality Criteria -- Data Quality Criteria -- Information Capabilities Quality Criteria -- Operations Capabilities Quality Criteria -- Security Capabilities Quality Criteria -- Storage Capabilities Quality Criteria https://documents.egi.eu/public/ShowDocument?docid=240 - AoB -- next meetings

Regular PTB meeting, 14:10-16:35 15 February 2011
Present:  Morris, Patrick, Laurence, John, Marco,  Balazs (notes)

The meeting started few minutes later due to skype problems and run considerably longer than planned.


I) Approval of previous meeting notes.

The meeting notes from the 25/01/2011 regular PTB meeting got approved.


II) Actions follow up

* Marco: bootstrap the compute accounting agreement group

Done.
The related info for the Compute Accounting Record agreement group:

coordinator: Cristina.del Cano Novales (to be confirmed)
group members: Cristina.del Cano Novales (APEL), Szigeti Gabor (ARC), Krzysztof Benedyczak (UNICORE), Massimo Sgaravatto (gLite), Andrea Guarise (DGAS)
wiki: https://twiki.cern.ch/twiki/bin/view/EMI/ComputeAccounting
communication: emi-jra1-compute list
status: just formed, no work started yet
expected delivery date: end of March

* Balazs: communicate possible shift of work plan deliverables due to insufficient gap between DNA1.3.x and area plan deliverables and due to overlap of EMI-1 release work and workplan preparation.

Done.
The message was propagated to PEB, unfortunately the possible shift/reordering of deliverables were tagged as "post emi-1 topic".


* Morris: follow up on the virtualization & cloud task force merger, inform the involved people, update the wiki (remove obsolete info/group), report on the revised mandate on the next meeting

Done.
The wiki is merged/cleaned (https://twiki.cern.ch/twiki/bin/view/EMI/EmiJra1T5TaskForceCloudandVirtualization).

PTB will schedule the overview of the cloud task force mandate on the next meeting

* Balazs: Clarify the minor releases vs. major releases of EMI with SA1/SA2 from the viewpoint of area workplans.

Done.
Balazs informs the PTB about the EMI-releases, how the component releases that are prepared after a major EMI release got out first are distributed as updates to EMI major release, then later optionally grouped and released together as a EMI minor release. EMI minor releases may also be used as a communication solution between EGI and EMI. Balazs also tells that the support/repository aspects of minor/major releases are not fully clear. It is something SA1/PEB should figure out after EMI-1.

III) News from PEB, EGI

* As the main message, Balazs emphasized that in the comming months, until EMI-1 is out the kebnekaise release preparation possesses the highest priority in EMI. PTs and areas must always prioritize SA1/SA2 task over JRA1.

* This also means that the EMI workplan preparations within PTB will only be started after the EMI-1 release is on a good track.

* PT members were asked to read the "Kebnekaise" release preparation schedule.

* Balazs informed the PTB about the different trackers that will play an important role in the EMI-2 planning and development. These are the "Development" and the "Requirement" trackers. PTs also need to work together with the "release" tracker.

* Some informal discussion took place about WLCG, EGI and EMI relation, in connection with the last week WLCG GDB meeting.

Balazs stated the official EMI view: EMI has both WLCG, EGI as its key customers.


IV) Report from area leaders

compute: the glue 2 "affair" was mentioned. Marco would like to start the harmonization of LRMS backend layer. Discussion about the client harmonization group work. The later team should present alternatives, starting from the current situation.

data: work going on according to plans, nothing to mention as a news on the middle/long term horizon.

security: no new middle/longer activity is foreseen to start (in addition to the ongoing ones). In connection with the XACML profile the data area input is needed. The security area will have the Zurich meeting next week.

infrastructure: smooth progress. Laurence mentions that the emi registry document soon ready for internal review.


V) Platforms: PTB decision about the debian flavour

The PTB selected the debian 6/64 bit platform as the debian-family to be supported for EMI-2 this way endorsing the expert group's recommendation:

"The Debian 6/64 bit was selected/proposed as the "debian platform" for EMI-2 with the possibility of changing to the next long term support Ubuntu version expected in April 2012 (Ubuntu 12.04 LTS). As of Tomorrow, the porting work should start with the Debian 6/64 platform and once some alpha Ubuntu 12.4 is out, a small expert team will evaluate the costs-benefits of a potential platform change to Ubuntu 12.04 for EMI-2.  But as of Today, the work should start on Debian 6."


VI) Task force issues, progress

* service monitoring TF

The task force, on the shot term (for EMI-1), most guarantee the smooth take over of the corresponding probes of EMI components.

Balazs informed the PTB about the agreed common EMI-EGI strategy concerning the handover of the Nagios probes. According to the agreement, the EMI service monitornig task force is responsible for the coordination of the nagios probes takeover in EMI as its short term high priority duty. The leader(s) of this task force are nominated by EGI and the members are contributed by every EMI PT that has to deliver/maintain a probe.

Emir created an initial list of probes, not clear if that is exclusive:
https://wiki.egi.eu/wiki/EMI_Nagios_probes

Task force leader (for the nagios phase): Emir Imamagic and Peter Solagna (both EGI)
Task force  members: EMI PTs that are responsible for nagios probes must delegate one representative. Morris acts as a contact/coordinator of these PTs.

The long term work of the service monitoring PT is put on hold. Actually, there is noone identified for that task yet. The longer term aspects of service monitoring, together with remote management will be discussed on the next PTB.

bottom line: until EMI-1 is out, the service monitoring TF must focus on nagios probes.


-- EMI-UI TF (also clarification concerning WN, VOBOX)

* EMI-UI: There is already a task force behind, its mandate was repeated:

"define content (list commands, utilities) of an UI box, define a metapackage, work on integration, create a user interface box, work on config, documentation. Main goal is to integrate the existing clients as much as possible."

The EMI-UI TF has a leader and the identified members. The team only need a "kick off".

The outcome of the TF will be offered as the eMI metapackage for an UI box, this will be the solution EMI will offer when customers ask for for the glite-UI

* WN: The integration task together with Maria (as relevant glite expert) will work on the creation of an EMI-WN metapackage. This metapackage and the corresponding deployment scenario will be based on the existing glite-WN.

* The VOBOX metapackage was considered out scope for EMI since it would include packages not available in the EMI distribution.


VII) EGI Quality Criteria

Balazs called the PTB attention to the recently (10 FEbruary!) released EGI quality criteria (https://documents.egi.eu/public/ShowDocument?docid=240) that will be used to certify/reject EMI components for UMD inclusion.

The area leaders were asked to provide feedback on the documents by 23 February.

assignments:
-- Compute Capabilities Quality Criteria: Marco
-- Data Quality Criteria: Patrick
-- Information Capabilities Quality Criteria: Laurence
-- Operations Capabilities Quality Criteria: Laurence
-- Generic Quality Criteria: John (only the security-related part)
-- Security Capabilities Quality Criteria:  John
-- Storage Capabilities Quality Criteria: Patrick


VIII) AoB

- next meetings

-- The next PTB meeting will be on 8th March.

-- a F2F PTB meeting may take place on Thursday during the Vilnius. To be decided latest by the end of next week. Laurence will not attend Vilnius.

- EMI-1 staged roll out

Patrick and Morris wanted to find out more about the recently surfaced EMI RC early adoption/staged roll out (not to confuse it with the EGI staged roll-out). Balazs described what he knew.


ACTIONS
--------

* Balazs: schedule the Cloud task force mandate and the longer term service monitoring and remote management plans for discussion at the next PTB

* Morris: to populate the service monitoring TF with "nagios contacts" of the EMI product teams.

* Area leaders: feedback on the EGI Quality Criteria documents: 23 February