PTB Meeting

Tuesday 29 Mar 2011, 14:00 → 16:00 Europe/Zurich

Teleconference

PTB meeting, 14:00-16:00, 29 March, 2011 Calling details: skype test conferencing service in Lund (call mailmagnes in skype) Proposed agenda: ---------------- - Approval of previous meeting notes, follow up on actions - Report from area leaders - EMI Service Registry design - EMI-2 workplan: schedule update - Longer term plans for service monitoring and remote management - AoB -- next meeting -- EMI all-hands program

------------------------------------------------------------
Regular PTB meeting, 14:00-15:50, 29 March 2011


Present:  Morris, Patrick, Laurence, John, Marco, Balazs (notes)


I) Approval of previous meeting notes.

The meeting notes from the 8/03/2011 regular PTB meeting got approved.


II) Actions

* Balazs reports the all-hand date problem to PO

Done.

Some discussion about the all-hands date. Marco said he wouldn't be there on Monday. Later corrected to Monday morning.


III) Area leaders

- Compute: there are delays with EMI-ES implementation, something to  correct in he new workplan

- Data: delegation working group and a storage accounting workin group was formed during the OGF31 with EMI leadership (Paul Millar and Jon Kerr Nilsen).

- Security: mostly emi-1 work, there are delays with the AAI work.

- Infrastructure: mostly emi-1 work


IV)  EMI Service Registry design

Patrick and Marco had no possibility to review the document prior to the meeting.

PTB discussed the design document (draft version 0.2). Below couple of excerpts:

Morris: felt that a related work, state of the art part was missing.
Laurence: That has been investigated and there are plans to publish that as part of a paper. However, such a section does not belong to a design specification.

Balazs: proposed to add a section that places the EMI registry (new service) into the landscape of other EMI components. This section should elaborate which EMI services/components are targeted to be replaced by the new registry and also cover the foreseen interaction of the new service with the rest of the EMI/UMD stack (BDII, GOCDB, clients, data/comput services, so on). All in all, place the registry into the EMI "ecosystem".

Proposal was accepted, Laurence will add such a section.

Morris raised the KPI issue: EMI needs to cut back on code, less line of code needed. If we add a new service, we are "working against the KPI"

Laurence/Balazs: This is a political, nevertheless important, aspect. Implementation details are not yet know.

Balazs: in general, he enjoyed reading the document. He mentioned several improvements that he would communicate directly to Shiraz. Some of the more conceptual things:
- use cases, especially the ones around "federation of information" and queries, access control, needs more work.
- use cases, at some place, already assumes architecture, or even implementation details (e.g. shutting down system for de-registration)
- security, access control part is weak.

John: What is the main motivation behind the development of a new service?
Balazs answered that a "common information system, a backbone" is a top priority EGI requirement towards EMI.


As the conclusion of the discussion, the PTB unanimously approved the following statement:

"The registry document draft as of now has been accepted by the PTB with minor comments. PTB gives a green light for the continuation of the EMI registry work while calling the team's attention for sustainability aspects. The next step expected from the team is the finalization of the design document and preparation of first implementation plan."


V) EMI-2 workplan deliverables


Balazs conveyed the message that all the five first year deliverables covering the EMI-2 plans MUST be delivered for the project review. This gives us 8th June deadline.

The date is not negotiable, the content is.

A meeting for next Tuesday was called to adjust the plan and define the content, what is doable knowing the new constraint.

Meanwhile, the area leaders must start working on the "progress report" part of their deliverable.


VI) Longer term plans for service monitoring and remote management


This is high risk area. Requirements gathering, having EGI involved, has been going on. This is not a focus area for year 2.

As a short/middle term objective, the nagios probes work and the numerous "small fixes" are identified.


VII) AoB

- Vilnius attendance:
Patrick: Monday - Thursday noon
Morris: Monday - Thursday
Balazs: Monday - Thursday
John: no
Marco: no
Laurence: no


- next meeting

5 April 10-12

19 April


- EMI all-hands program

Area blocks: the discussion topics should be "future looking"

It is problematic to have a compute area block on Monday morning.


- Brussels review

Balazs informed PTB about the planned rehearsals, the EMI delegation and other details of the June 22 review.


Actions
-------


* Balazs: send out a doodle to find suitable slots for workplan work.