• 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	LFC, Top and site bdii, Atlas testing(?)	david@lipNOSPAMPLEASE.pt
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
INFN-Catania	2 machines User Interface and AMGA	emidio.giorgio@ctNOSPAMPLEASE.infn.it
UNICORE in collaboration with PL-GRID	For UNICORE + gLite components on 'dedicated small system' first Also interested in testing some tools in EMI	bala@matNOSPAMPLEASE.umk.pl klusi@matNOSPAMPLEASE.umk.pl
D4Science-II	Will install some services; can provide around 4-5 machine for the tests DPM, CREAM, Site BDII, WN, UI	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
LitGrid/NGI.lt	Will deploy gLite, ARC and dCache	grid@mifNOSPAMPLEASE.vu.lt
TCD/Grid-Ireland	Test EMI WN with a particular interest in its portability to SL6; support for GPUs; and portability to other platforms such as PS3.	Eamonn.Kenny@csNOSPAMPLEASE.tcd.ie
SHIWA	Will test the deployment using the SHIWA WF interoperability use case	m.kozlovszky@sztakiNOSPAMPLEASE.hu
EDGI	Will test the deployment using the EDGI use case	smith@sztakiNOSPAMPLEASE.hu
Pl-Grid/QosCosGrid/Mapper	Test PL-Grid tools and services using EMI services	krzysztof.kurowski@manNOSPAMPLEASE.poznan.pl radecki@aghNOSPAMPLEASE.edu.pl Lukasz.Dutka@cyfronetNOSPAMPLEASE.pl
EGEE-SEE-CERT	EMI Products: CREAM, site-bdii,dpm head,dpm pool,glite wn,glite ui,stand alone torque node and a stand alone mysql node. Number of Boxes: 13 boxes.	Dimosthenes Fioretos dfiore@nocNOSPAMPLEASE.edunet.gr, Institution: National and Kapodestrian University of Athens / GRNET

Under discussion:

• CERN

Pending:

• NorduGrid: [balazs.konya@hep.lu.se]
• IGI (Italian NGI): [francesco.giacomini@cnaf.infn.it]

The success depends on the availability of volunteer contributors. Contributors can be either EMI partners or EMI product users ( EGI, NGIs, potential customers, Virtual Organizations etc.) wishing to provide some HW resources and/or collaborative effort to test EMI products they are interested in. Being aware of the fact that interest or effort/resources contribution is always limited in quantity and time, as a contributor you can declare your availability just for a subset of products for a limited number of campaigns per year. Even 2 weeks and few CPUs per year can be very helpful for EMI Testbed.
To become a contributor contact EMI Testbed Staff providing the following information:

1. Your Name, Role and Institution
2. Which EMI products testing activity you may be interested in and why.
3. Type of contribution:
   1. Hardware and Administration Effort: *. Number of boxes ready to deploy EMI components you may provide and for how long *. EMI Products you are interested in (all is assumed if not otherwise specified)
   2. Testing Effort: *. Your Organization use case

1. Requirements for Pre-Deploment Test:
   1. To provide feedbacks Editing Access to CERN twiki is an advantage, but you can also send feedbacks by mail (see below)
2. Deployment modality:
   1. Please deploy the service according to your site typical deployment, this will provide us with use cases representative of real production environment.
3. General Configuration Issues:
   1. EMI Repository Link
   2. General EMI-1 Release and per product Release Notes documentation.
   3. To let EMI Testbed team test your correct installation/configuration and volunteer users test service functionality, some services need to be configured to interact with each other. In particular:
      1. To publish your services you can use at first the EMI Infrastructure information system bdii for configuration , and then the volunteer site deploying site and core bdii will be configured to see your resource. A gLite information system (BDII) was setup ( certtbpre-bdii.cern.ch working as site and top bdii) for gLite and dCache resources.
         1. Top-level BDII . Contact it from UI by command: ldapsearch -x -H ldap://certtbpre-bdii.cern.ch:2170 -b mds-vo-name=local,o=grid (see also details )
         2. Site-level BDII . Contact it from UI by command: ldapsearch -x -H ldap://certtbpre-bdii.cern.ch:2170 -b mds-vo-name=cert-tbpre-cern,o=grid (see also details )
      2. You are also requested to enable emi-testers.emi-eu.eu VO on your instance ( -> section 3.3 )
      3. Depending on the service you are configuring you would to set your configuration values to point to other sites deployed services. For configuration values please contact EMI Testbed Team.
4. Deployment Feedback:
   1. If you are familiar with twiki and have a CERN account for editing it, please:
      1. Go to section 4.1 below
      2. Click on the Feedback Form corresponding to your Institution in the table raw of the service to deploy. You will then directed to a new page with a template form you have to fill following instructions.
      3. Once done, notify EMI Testbed Staff
   2. Or you can download the proper feedback form below and mail it to EMI Testbed Team:
      • For deploying volunteer sites EMI PreView Deployment Report Template
      • For volunteer users EMI PreView Usage Report Template
5. For additional information or support contact EMI Testbed Team

To deploy testers.emi-eu.eu on your service you need:

1. To enable the VO add it in the VOS variable of the yaim site-info.def file of your service (ex. VOS="alice atlas cms dteam infngrid lhcb ops testers.eu-emi.eu")
2. Create in the directory with site-info.def a directory vo.d (if not existing) and save there the following file (including replica): testers.eu-emi.eu
3. Check you have INFN CA installed with command $> rpm -qa |grep INFN .... output should be somethig like "ca_INFN-CA-2006-1.37-1"
4. For pool accounts add in users.conf the following sample: users_testers.conf
5. For groups enabling add in groups.conf the lines in the attached file: groups.conf
6. Add new certificates (master and replica) to /etc/grid-security/vomsdir/ directory:
   • NEW CERTIFICATES FROM Jul 20 2011 NEW !! Install EMI Testing Infrastructure Utility repo and run yum install emi-tb-vomscerts

For the manual configuration of vomses parameters ( ex. .voms/vomses , .glite/vomses on the UI) use the following parameters:

"testers.eu-emi.eu" "emitestbed07.cnaf.infn.it" "15002" "/C=IT/O=INFN/OU=Host/L=CNAF/CN=emitestbed07.cnaf.infn.it" "testers.eu-emi.eu"
"testers.eu-emi.eu" "emitestbed01.cnaf.infn.it" "15002" "/C=IT/O=INFN/OU=Host/L=CNAF/CN=emitestbed01.cnaf.infn.it" "testers.eu-emi.eu"

The second line is for the replica In the near future, the VO will be deployed with EMI releases, and above info and files integrated in yaim profiles/examples and the certificate deployed through an rpm file

For ARC users the VO configuration is described at http://www.nordugrid.org/documents/voms-notes.html . For vomses file use the input as above.

For Unicore users: UNICORE does not support VOMS, so no configuration can be provided. UVOS, UNICORE VO solution, is to be phased out during the course of EMI, so we didn't deploy it in the testbed. It is planned to support the SAML based VOMS later on, but that is not available yet. If you require access to the testbed, you'll have to open a GGUS tkt send me your certificate and I will register it.

• Testers VO subscription: The default VO for testing in EMI is testers.eu-emi.eu. So, for authentication on services supporting voms certificates, users need to subscribe to the VO for accessing the testbed. To enable the VO on Product Teams instances or User Interface follow instructions in section 3.3 in this page.
  

(Note) Request for Deployment Source:

1. Y1: EMI Technical Area Staff (Product Teams, EMT, Technical Area Managers)
2. Y2: Volunteer Sites specifically asked for preview
3. Y3: Critical Component

WORK IN PROGRESS

Starting date: May 18 2011

duration: 2 weeks	Announce start of preview deployment activity Volunteer sites to deploy services and provide feedback. In parallel with deployment volunteer user community provide information about their use cases
duration: 1 week	EMI Testbed team to run tests on the deployed services
duration: 2 weeks	Announce start of preview user community testing activity Volunteers to test their use cases on the tesbed and provide feedback