DATE: 05.09.2011

Participants: 

Eamonn. Kenny, Christian Bernardt, Michele Dibenedetto, Riccardo Zappi, Mattias Ellert, Massimo Sgaravatto, Paolo Andreetto, Zdenek Sustr, Anders Wäänänen, Valery Tschopp, Andrea Ceccanti, Danilo Dongiovanni, Michail Salichos, Andres Abad Rodriguez, Maria Alandes Pradillo,  Giuseppe Fiameni, Cristina Aiftimiei

Missing: AMGA, DGAS, SAGA SD-RAL, MPI, gLite Security, gLite Infosys, UNICORE
Excused: Vincenzo Ciaschini, Jon Kerr Nielsen

Minutes previous meeting:
- no comments received

QA announcements:
MariaAP:
new policies versions in preparation for:
Change Management Policy:
new section about “EMI Versioning Schema “
Changelog and details at https://twiki.cern.ch/twiki/bin/view/EMI/EmiSa2ChangePolicy#5_Logbook (Details)
Packaging Policy 
waiting for Debina information
added new section “Managing EMI Packages in EPEL “
some other changes may appear after discussing with Balazs the development tasks/tracker
AndresAR
Debian status:
working to the etics-client
wiatig for some from Debian experts regarding a problem they incontered
HP nodes for SL6 – delayed:
trying to add some monitoring scripts 
will be probably available by Wednesday
Discussion:
CristinaA:
the structure of EMI repository for SL6 is ready
delay in making available the third-party packages because using a wrong version of the etics-client
information about the etics-client version to be used for SL6 builds will be aded to the EMI1Update twiki page

ACTION LIST (https://savannah.cern.ch/task/?group=emi-emt)
EMT incidents:
#22244, ARC report on Immediate & High priority RfCs – JonKN is asking about the possibility to make use of the field "Deadline" in bugzilla to notify about when they intend to provide a certain fix. EamonnK wil investigate if this is a commone field also for the other trackers and if it can be used.
#22245, DataManagement: provide source rpms – no update
#22247, InformationSystem: provide binary and source tarballs – no update
#22350, STORM: provide source rpms for all components – MicheleD – they are following this issue in their internal tracker, source rpms will be provided with the next update of the STORM product 
EMT Documentation: 
- no activity on other actions

EMI Release Status:
CristinaA:
Update 6 released on  01.09.2011 contains: BDII core, site, top, dCache, FTS, STORM, WMS
http://www.eu-emi.eu/emi-1-kebnekaise-updates/-/asset_publisher/Ir6q/content/update-6-01-09-2011 
Planned products updates: - reports for Open tasks should be provided before each EMT-meeting, as comments in the corresponding tasks
APEL – no update
ARGUS – Valery – on schedule
CEMon – on schedule
DPM & LFC v.1.8.2 – no update
Hydra – no update
gLExec – Dennis updated the test report
LCMAPS plugins verify-proxy – no update
UNICORE Client, TSI, UNICORE/X – no update
DNA1.3.2 list of products will be used for opening release tasks, and the versioning must follow the “EMI Versioning schema”

EMT report:
CristinaA:
Details about the content of the report are in the agenda
ARC – will try to improve the report so that in the following week we can have a better image about their RfCs
MPI – EnolF answered via e-mail that he was thinking their tracker items are automatically included in the EMT report. EamonnK will investigate
there is no RfC in the report that was not yet planned to be released
STORM report, attached to the agenda – there are only High priority RfCs. MicheleD – the fixes will be made available with the next update of the STORM product. CristinaA – a ask for STORM should be opened referencing this RfCs, with the “Sould be finished on” date probably Update 8.

GGUS situation:
CristinaA:
Mathilde Romberg is monitoring the SLA with EGI, preparing the GGUS status report for each EMT-meeting, present in the agenda
there are no SLA violation for last week
gLite Security, DataManagement, gLite Compute, VOMS, STORM PTs are requested to answer the tickets present at “Tickets to be discussed” link (https://twiki.cern.ch/twiki/bin/view/EMI/SupportStatusReport020911#EmiGGUS)
PTs are requested to act ASAP on their GGUS tickets

 
AOB:
CristinaA – reply to last wee comment (Christian, tkt #73851 ) - communication was send to EGI-UMD about what is the solution that has to be applied by UMD, and it seems that a request was done for a 3rd level support unit UMD SU in GGUS, that will be available from the next update of GGUS.