Participants: Cristina Aiftimiei, Massimo Sgaravatto, Patick Fuhrmann , Bjorne Hagemeier , Danilo Dongiovanni, Tomasz Wolak, Alberto Resco.

Discussion in-line in the Agenda:

1.HW resources requirement estimation. 1.1.total number and list of services to be considered? 1.2.number of platforms to be supported ?

Cristina
Points 1.1, 1.2 in agenda : Month 2 PTB should provide list of services and platform
Danilo
Together with the list of services we also need a list of services which are considered different from integration testing point of view (i.e. group services which have differences transparent to other services (DB implementation with same API (ex glite Voms-oracle/mysql ??.. etc ))

1.3.how to deal with WN (various batch systems (LSF...), should the testbed provide all of them?)?

Massimo
WN batch system. Still not clear whether people who provided resources for testing that in the past will continue. Open issue
1.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?
Cristina
Expected 1 RC version for each service per Release.
1.5.Any particular requirements for security tests?
None forseen. Will ask for feedback from security area manager.

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:
2.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.2.installation/configuration of services, including configuration of users or other services support when required by testing needs 2.3.be available for actions on PT (savannah tasks) and track activity in savannah tasks. 2.4.keep the logbook of assigned testbed services up-to-date o help in debugging

Patrick
Agree on PT role with specifications: PT person installing service, on HW provided by testbeds, keeping logbook. Then coordination on problems to make sure ”testbeds services talk to each other” is again in charge of sa2.6, which may ask for further support in case of problems.
Patrick
Mailing lists more than 1 single PT person, accounting for people unavailability periods.
Danilo: check savannah tasks can be assigned to more than 1 person. Will use "squad" in savannah.
MASSIMO, CRISTINA : Agree on PT roles.

3.Access to testbeds: which certificates to access all testbed servers? 3.1.catch all dteam VO? will exist ? 3.2.some fake CA /users for running massive testing may be needed 3.3.access policy for testbeds in case of concurrent usag. Do developers need resources exclusive usage?

Massimo:Integration testing depending on Morris definition. Concurrent usage depending on the test. For performance tests exclusive usage may be required but not clear whether it is a part of integration testing.

Danilo
also consider that integration testbed will rely on virtual servers for >50% so that performance tests cannot be run on that.

4.SA2.6 KPI: availability & reliability of testbed: 4.1.we plan to measure with nagios server uptime. 4.2.do you expect us to deal with downtimes and broadcasts too?
No answer on this.

5.Large Scale Testbeds from outer (of EMI) partners: Testbed KPI 50 cpu target for year 1. 5.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. 5.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

Before contacting PT leaders, we must define with EGI operations a way to have a centralized dteam VO which must be centrally supported. That would make it easier for NGI to accept tests, debug etc..
Danilo Will discuss with EGI-Operations (Tiziana Ferrari)

6.AOB: None.

ACTIONS:
Danilo: will get info about PTB document defining list of services and platforms.
Danilo: will revise draft according to feedbacks and assign tasks in savannah
Danilo will contact PT to define the testbed squad for savannah.

-- DaniloDongiovanni - 21-Jun-2010

Edit | Attach | Watch | Print version | History: r1 | Backlinks | Raw View | WYSIWYG | More topic actions
Topic revision: r1 - 2010-06-21 - DaniloDongiovanniExternal
 
    • Cern Search Icon Cern Search
    • TWiki Search Icon TWiki Search
    • Google Search Icon Google Search

    EMI All webs login

This site is powered by the TWiki collaboration platform Powered by PerlCopyright &© 2008-2020 by the contributing authors. All material on this collaboration platform is the property of the contributing authors.
Ideas, requests, problems regarding TWiki? Send feedback