ALICE TEST VO
60 likes | 325 Views
ALICE TEST VO. Miguel Martinez, Pablo Saiz ALICE LCG Task Force Meeting 18 th April 2012. ALICE_TEST. New VO: Using a backup of ALICE catalogue as starting point With all ALICE users With all ALICE SE (for reading) And some ALICE SE (for writing) Current status Central Services running
ALICE TEST VO
E N D
Presentation Transcript
ALICE TEST VO Miguel Martinez, Pablo Saiz ALICE LCG Task Force Meeting 18th April 2012
ALICE_TEST • New VO: • Using a backup of ALICE catalogue as starting point • With all ALICE users • With all ALICE SE (for reading) • And some ALICE SE (for writing) • Current status • Central Services running • API services running • Executing jobs at CERN
Original plan (from 9/3/12) Mar Apr May Now: 1 week: Investigate test system 1 week: Test Catalogue migration 1 week: Define New VO 1 week: Verify quotas 1 month: New hardware for CS 2 days: Central deployment from backup 3 days: First site working (CERN) 2 weeks: At least 2 external sites (CCIN2P3, ?) After that works, keep adding sites 2 months: 1 day: Switch VO 1 day: Overall site upgrade
Migration of the catalogue • Starting from backup: • Convert tables to InnoDB • Change user name/userid • In test machine: 12 hours • Script divides tasks among cpus (test 4 CPU, production 24)
How to connect: • From aliensh: • export alien_API_SERVER_LIST=alientest02.cern.ch:10000 • From alien: • export ALIEN_ORGANISATION=ALICE_TEST • Disclaimers: • Data registered in this VO can be deleted • Jobs submitted to this VO can be deleted
Next steps • Simple jobs work: • Test real jobs (packages, brokering…) • Include trains (?) • Setup voboxes at CERN, CCIN2P3, Torino… • If new hardware, redeploy services