EMI 1 Release Candidate Large Scale Pre-deployment Testing

*****draft for discussion********

What

EMI 1 RC large scale pre-deployment testing is test deployment of RCx onto volunteer sites supervised by EMI.

Why

The aim is to get early feedback on RCx during March-April to improve components and fine-tune EMI procedures.
  • Do we follow EGI rollout procedure ?
  • Do we follow (or create) EMI rollout procedure?
    • Deployment documentation
    • Benchmarks, feedback form
      • Feedback on the release notes and documentation
      • Installation / deployment feedback form (check EGEE PPS twiki)
      • Check installation/ deployment of UNICORE and ARC services
  • This is a new activity within EMI Large Scale Acceptance Testbed

How

Scenarios to consider:
  • "Early adoption/rollout" - not to be confused with EGI Staged Rollout
  • Absorbed by EMI Large Scale Acceptance Testbed which operates a Demand-Supply approach eg
    • Demand: A request of test describing the testing scenario (resources needed, services involved, number of instances, number of users involved etc.etc.).
    • Supply: A community of partners (NGI, EGI, PRACE, EMI internal partners) available to participate to specific tests campaigns with X effort, Y resources for Z time to test P1, P2, PN product.
  • Create a pre-production infrastructure which will mimic complete full production infrastructure
  • others?

Things to include in the rollout page:
-repository
-release notes
-installation test template (check how SA2 handles feedback/testing reports)

The "EMI rollout coordination team" to be created. (Maria, Francesco, Danilo, Cristina, UNICORE rollout expert, Balazs + ARC rollout expert) From Danilo, to check: Axel Berg (Axel@saraNOSPAMPLEASE.nl)

Sites

The following sites/institutes have volunteered - mixed set of production and test machines
Site/Institute Details Contact
AS, Taipei   stella.shen@twgridNOSPAMPLEASE.org
CSIC For products they are familiar with STORM, WMS, LFC, combination of LB + CREAM isabel@campos-itNOSPAMPLEASE.es
LIP For LFC and other data man services isabel@campos-itNOSPAMPLEASE.es
DESY NDGF (Tier I) is willing to run EMI-1 dCache before Mid of March.
DESY will follow with 2 of it's 5 dcache instances before mid of the year.
We are talking about production systems.
On early deploying of other EMI componets, I didn't get any feedback yet from our Tier II manager.
patrick.fuhrmann@desyNOSPAMPLEASE.de
GILDA 2 machines emidio.giorgio@ctNOSPAMPLEASE.infn.it
UNICORE in collaboration with PL-GRID For UNICORE + gLite components on 'dedicated small system' first bala@matNOSPAMPLEASE.umk.pl
D4Science-II Will install some services; can provide around 4-5 machine for the tests andrea.manzi@cernNOSPAMPLEASE.ch
HealthGrid Accepts in principle.
How many services will we have to install?
How many days will we have after the RC distribution?
Will there be some benchmarks/ tests to pass on?
As you may know VRCs are being built and HG is the representative of the LSGC, thus I took the liberty to forward your request to the other members of the VRC so, that we can be sure to test all what you need to be tested!
ylegre@maat-gNOSPAMPLEASE.com
maatG Accepts in principle.
Similar concerns as HG; process to follow.
dmanset@maatgNOSPAMPLEASE.com
GISELA Waiting for details on how to proceed ramond@gmailNOSPAMPLEASE.com

Pending:

  • NorduGrid: [balazs.konya@hep.lu.se]
  • IGI (Italian NGI): [francesco.giacomini@cnaf.infn.it]
  • TCD/Grid-Ireland: [david.ocallaghan@cs.tcd.ie]

-- FloridaEstrella - 16-Feb-2011

Edit | Attach | Watch | Print version | History: r10 < r9 < r8 < r7 < r6 | Backlinks | Raw View | WYSIWYG | More topic actions
Topic revision: r10 - 2011-03-04 - DaniloDongiovanniExCern
 
    • 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-2024 by the contributing authors. All material on this collaboration platform is the property of the contributing authors.
or Ideas, requests, problems regarding TWiki? use Discourse or Send feedback