EMI-SA2.6 Testbed Meeting: Feedback on draft from developers

Monday 21 Jun 2010, 15:00 → 16:00 Europe/Rome

CERN

AGENDA

1. HW resources requirement estimation.
   1. total number and list of services to be considered?
   2. number of platforms to be supported ?
   3. how to deal with WN (various batch systems (LSF...), should the testbed provide all of them?)?
   4. testbeds for major releases (RC vs RC services cases) + cross middleware testing (Unicore vs gLite vs ARC) are considered as cases where sa2.6 provides HW and coordinates installation and configuration of services. Any idea about possible requirements in these cases? How many contemporary releases mantained? How many RC versions per service?
   5. Any particular requirements for security tests?
2. Agreement on expected (from SA2.6 point of view) PT role/effort in testbed maintenance. We will ask PT to provide and mantain a production version of their products (we can provide part of the HW when needed). This will imply:
   1. having a PT contact (name and mail) for this activity, which will be the only one with root access to his PT servers
   2. installation/configuration of services, including configuration of users or other services support when required by testing needs
   3. be available for actions on PT (savannah tasks) and track activity in savannah tasks.
   4. keep the logbook of assigned testbed services up-to-date o help in debugging
3. Access to testbeds: which certificates to access all testbed servers?
   1. catch all dteam VO? will exist?
   2. some fake CA /users for running massive testing may be needed
   3. access policy for testbeds in case of concurrent usag. Do developers need resources exclusive usage?
4. SA2.6 KPI: availability & reliability of testbed:
   1. we plan to measure with nagios server uptime.
   2. do you expect us to deal with downtimes and broadcasts too?
5. Large Scale Testbeds from outer (of EMI) partners: Testbed KPI 50 cpu target for year 1.
   1. EGI: each SW area manager / PT gives me a list of friedly NGI sites willing to provide some resources and effort for needed scale tests for each given product.
   2. Dteam VO for debugging in EGI: still not clear if the existence of such a catch all VO for quick developers' debugging and testing activity will be granted. Consequences on testing/testbeds in EMI
6. AOB

++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++

EVO Details

Title: EMI-SA2.6 Description: Feedback from developers on testbeds.

Community: Universe

Password: EMISA26

Meeting Access Information:

Meeting URL http://evo.caltech.edu/evoGate/koala.jnlp?meeting=MsMiMI2i2vDsD29s99Dt9s

Password: EMISA26

Phone Bridge ID: 2031116

Password: 6767