SA2.6 Meeting: EMI1 Rollout Status, Automated Testing, EMI Preview

Tuesday 24 May 2011, 15:00 → 17:00 Europe/Zurich

CERN

Agenda:

• EMI-1 deployment testing: internal feedback to optimize process
• Preview Activity and large scale
• Re organization of twiki page
  • Logbook for testing components
• EMI AHM what to report and objectives of second year
  • Automation
    • tests: nagios (there is a session at AHM we should attend to (even though is in parallel with our SA2))
    • deployment?

Title:        EMISA26
Description:    Testbed meeting 
Community:    Universe
Password:    emisa26

Meeting Access Information:
- Meeting URL
    http://evo.caltech.edu/evoNext/koala.jnlp?meeting=MtM8Ma2i29D8DI9l92Ds9t

- Password: emisa26
- Phone Bridge
    ID: 344 5228
    Password: 6598

Central European Summer Time (+0200)
    Start    2011-05-24  15:00
    End      2011-05-24  17:00

EVO Phone Bridge Telephone Numbers:
---------------

- Switzerland (CERN, Geneva)
    +41 22 76 71400

- Slovakia (UPJS, Kosice)
    +421 55 234 2420

- Italy (INFN, several cities)
    http://server10.infn.it/video/index.php?page=telephone_numbers 
    Enter '4000' to access the EVO bridge

- Germany (DESY, Hamburg)
    +49 40 8998 1340

- Czech Republic (CESNET, Prague)
    +420 95 007 2386

Participants: Bjiorn, Tomasz, Danilo, Frantisek, Christian.

1.  FEEDBACK FOR AHM:
   1. ACTION- Danilo writes draft and collects feedback. 3 slides: 1 year achievements + concerns and problem + second year focus..
2. Re organization of twiki page:
   1. separate table of servers into blocks of talking to each other services ? link in other pages some big blocks...
   2. quick f2f meeting at AHM with Tomasz and who wants to participate to decide which changes
3. Logbook for testing components: could be a redundant with some product documentation, but agree that can be useful for future internal reference and for large-scale collaborators. ACTION on all to fill the table in sec. 4.3 of twiki
4. Testing Automation: we start with nagios grid at cern, deploying fake cern CA for robot certificate.
   1. ACTION: Tomasz setup a directory from where download all needed files to put in the testbed.