The EMI All-Hands meeting is taking shape. The draft agenda is available at http://indico.cern.ch/conferenceDisplay.py?confId=108375. Logistic information has been provided by the organizers (CESNET) and will be circulated to all EMI members.
If any team is planning to have side meetings before or after the AH, please get in touch with the EMI Project Office
The Technical Director has reported on the creation of a new Product Team called SAGA-SD-RAL and responsible to look after the SAGA Service Discovery implementation currently distributed with gLite. In this occasion, the PEB also reminds that the creation of new Product Teams must be necessary to EMI long term plans and produce actual software products. The PT is not a way of investigating new technologies. In the latter case, the creation of a Task Force under the coordination of the PTB and/or JRA1
A decision about components configuration has been taken by the PTB. EMI Product Teams are responsible to provide ways of configuring their services and have to adopt standard configuration methods recommended by the operating systems they support. EMI is not requested to go beyond this level of configuration, in particular higher level configuration tools are not within the EMI scope. The infrastructures using EMI are responsible to manage how the services are configured by the participating sites and what tools they want to use (YAIM, Quattor, custom scripts, etc). However, EMI must commit to adopt the standard methods and file locations used on the supported platforms
It is reminded that EMI presentations must use the EMI template. For not fully EMI-centric presentations, for example describing work done also as part of other projects or activities, EMI should be explicitly mentioned and at least the EMI-related slides should use the EMI template.