PTB Meeting

Tuesday 8 Nov 2011, 10:00 → 12:00 Europe/Zurich

Teleconference

PTB meeting, 10:00-12:00, 8 November, 2011 Calling details: direct skype conference call Proposed agenda: ---------------- - Follow up - RfC and release plan approval - approval of the caNL product team - Standard compliance tests - Padova follow up: -- new data task force (?): emi-http -- EGI requirements for credential validation - JRA1 wiki pages - Dev tracker: final PTB check

Slides Release_Manager_report08_11_2011.pdf

PTB meeting, 10:19-11:30, 9 November 2011

Calling details:  skype direct call

Present: Patrick, Marco, Jon, Balazs (notes), Cristina, Laurence (joined at 11:05)


0) Follow up

-Approval of the meeting notes from the previous PTB meetings (11.10.2011):

Notes are approved.

- Patrick to post "UMD problem report" and Cristina to propagate it further.

done, EGI, Mario acknowledged the report.

-Actions: checked, open ones are carried over, see below

-- "UMD certification problem report" prepared by Paul and propagated by Cristina made EGI/UMD to acknowledge mistakes on their side.

-- Confirm Nikhef person for the EGI Federated Clouds TF: Oscar Koeroo is the person


1) RfCs and release plan: PTB approval

Cristina presented the following scheduled product updates:

- Emergency Update for APEL publisher  (https://savannah.cern.ch/task/?23903)

This emergency update was requested by the Security Vulnerability Group.

- minor update for UNICORE UVOS, v. 1.5.0-1 (https://savannah.cern.ch/task/index.php?23763)
 
Scheduled for Update 10 (11) – 24.11.2011

- revision update for CREAM, v.1.13.3 (https://savannah.cern.ch/task/index.php?24022)

Schedueld for Update 11 - 15.12.2011

PTB endorses the above product updates.


2) approval of the Common Authentication library new product team

A better name was recommended: COmmon LIbrary for authN, COLIN
leader: Zdenek Sustr
members:  Daniel Kouril, Weizhong, Krzysztof Benedyczak
product: three libraries for the three different languages. The code will sit in three different code repositories (different languages). The product to be distriburted as three packages nevertheless certified and released as one product.

Tech preview will be available for EMI-2

PTB endorses and creates the above product team.


3) Standard compliance tests

The status is captured by the overdue milestone: MJRA1.17 milestone https://twiki.cern.ch/twiki/bin/view/EMI/MilestoneMJRA117

PTB needs to identify the minimum set of standard compliance test suits:

-data area well covered, only gridftp missing

-compute: Marco sends a list

-infra: Laurence to come with list that should contain "GLUE2 ldap", some XML stuff for GLUE2 and something for "accounting record validations"

-security: John to come with a list that will include some "VOMS" tests as VOMS is a de-facto standard

In connection with the standard compliance, the new KPI was presented (already proposed to PEB)

KJRA1.1 - "Standard compliance KPI":

Name: Number of EMI service interfaces and libraries passing standard compliance tests

Description: The metric measures how many EMI service interfaces and libraries are successfully tested for standard compliance. Standard compliance is defined broadly and also includes compliance with EMI internal agreements.

How to measure: The number is taken by checking the available test reports generated during the quarter by the Product Teams.


4) Padova follow up:

- data:  emi-http task force ?
Patrick suggests that the http activcity should stay as an EMI data internal work and not to create a task force, an update will be given at the beginning of next year.

- security: EGI requirements for credential validation

John posted a list of tickets created after the all-hands.  All these requests will be added to EMI req tracker and be prioritized later. The tickets:

Unit test for CRL refresh:
https://rt.egi.eu/guest/Ticket/Display.html?id=3074

Max accepted proxy-lifetime:
https://rt.egi.eu/guest/Ticket/Display.html?id=3075

Drop in trust anchors:
https://rt.egi.eu/guest/Ticket/Display.html?id=3081

Support for OCSP:
https://rt.egi.eu/guest/Ticket/Display.html?id=3076

OID Extensions:
https://rt.egi.eu/guest/Ticket/Display.html?id=3077

SHA2 proxies:
https://rt.egi.eu/guest/Ticket/Display.html?id=3078

Proxies keysize:
https://rt.egi.eu/guest/Ticket/Display.html?id=3079

RPDNC constrains:
https://rt.egi.eu/guest/Ticket/Display.html?id=3080
 
- compute: The need to investigate production quality use of glue2 in compute has emerged. It'll be done after code freeze.

- infra: nothing worth mentioning

5) JRA1 wiki pages

Jon informed PTB members about the updated JRA1 main wiki page. Also asked the area leaders to check whether their most active main area page is linked.


6) Dev tracker: final PTB check

Balazs informed PTB that the dev tracker is now fully populated and should be used as THE tool for task monitoring and eventual task re-prioritization.

The completion of the tracker will be publicly announced once Patrick gives a green light. The other area leaders were happy with the tasks:

-data still will have to check.
-compute: approves
-security: looks fine
-infrastructure: ok


7) AOB

- Patrick will be away till 4th December

- PTB composition was voted at the CB. Outcome was to keep the current PTB. Balazs proposes to have Piotr Bala as an observer invited for the next PTB meetings. No objection.

- KPIs: Jon and Balazs has submitted a proposed revision of the JRA1 KPIs. These were presented to PTB (a mail will be posted as well)
 
- Balazs brings up the "Vision meeting" to where PTB members are also invited.

- next meeting: two weeks from now
 


ACTIONS
-------

- Balazs: Inform Oscar (Nikhef) about his new role as EMI delegate to the EGI Virtualization task force

- John and Laurence and Marco: come with a list of necessary standard compliance test suits for the area

- John: inform Zdenek about the PTB decision regarding the new COLIN PT.