EMI Release Preview Testbed

EMI Release Preview activity is an opportunity for community of developers, system administrators and users interested in EMI middleware to preview its software products.
This activity involves:

  • Volunteer Sites providing hardware resources and administration effort to install and configure products
  • Volunteer User Communities providing effort to test the products' functionalities under their specific use case
  • EMI Testing Infrastructure and Release experts to coordinate and support volunteers in the deployment and previewing activity

1. Testbed News / Warnings

Check this section before using testbed or asking for support. Subscribe to the twiki notification system to get news on these issues.

2. Testbed Contributors Overview

  • 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]

3. HOWTO section for Volunteer Contributors

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:
  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:

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.

4. Testbed Inventory & Feedback Forms

0 Component Name Service Name Request For Deployment Y1/Y2/Y3 (Note) Type of Setup Deploying Sites & Feedback Form    
1 AMGA v.2.1.2 AMGA Y2   INFN-Catania Feedback Form   No
2 APEL parsers v.0.0.0 To deploy on -> Cream Y3   Sites Deploying Cream (see Cream Row in this table)

CSIC Feedback Form
MAATG Feedback Form
HEALTH-G Feedback Form
  No
3 APEL publisher v.3.2.7 APEL Server Y3   CESNET Feedback Form DONE   No
4 ARC CE v.1.0.0 ARC CE Y1, Y3 With Gridftp interface and ARIS LIT-GRID Feedback Form
  No
5 ARC Clients v.1.0.0 Part of -> UI     LIT-GRID
Please Report about it in the UI Row Feedback Form for your Site
  No
6 ARC Core v.1.0.0 Part of -> all ARC Services     LIT-GRID

  No
7 ARC gridftp server v.1.0.0 ??     LIT-GRID

  No
8 ARC InfoSys v.1.0.0 ARC Information System Y3   LIT-GRID Feedback Form
  No
9 ARGUS v.1.3.0 ARGUS Server Y1, Y3 Site+TOP(Optional)+VO(Optional) Level PAP MAATG Feedback Form
HEALTH-G Feedback Form
  No
10 ARGUS-EES v.0.1.0 To deploy on -> ARGUS Server         No
11 BLAH v.1.16 Part of -> CREAM CE Y1, Y2, Y3   Sites Deploying Cream (see Cream Row in this table)
  No
12 CEMon v.1.13 Part of -> CREAM CE Y1, Y2, Y3   Sites Deploying Cream (see Cream Row in this table)
  No
13 core BDII v.0.0.0 Part of -> all gLite Services Y3   Sites Deploying gLite   No
14 CREAM v.1.13 CREAM Y1, Y2, Y3 LSF + Torque CSIC Feedback Form
MAATG Feedback Form
HEALTH-G Feedback Form
D4Science Feedback Form DONE

EGEE-SEE-CERT Feedback Form DONE
EGEE-SEE-CERT Feedback Form DONE
  No
15 dCache v.1.9.12 dCache Y1, Y2, Y3   DESY NDGF Feedback Form DONE
AachenFeedback Form
DESY Feedback Form
  No
16 Delegation Java v.2.0.0 Part of -> all gLite Services         No
17 DGAS-sensors v.4.0.1 To deploy on -> CREAM     Sites Deploying Cream (see Cream Row in this table)

CSIC Feedback Form
MAATG Feedback Form
HEALTH-G Feedback Form
  No
18 DPM v.1.8.1 SE-DPM Y1, Y3   HEALTH-G Feedback Form
D4SCIENCE Feedback Form DONE
EGEE-SEE-CERT Feedback Form DONE
  No
19 emi-ui v.0.0.0 User Interface Y3   All contributing sites and testers are encouraged to install the User Interface for preview activity.


D4SCIENCE Feedback Form DONE
INFN-Catania Feedback Form
EGEE-SEE-CERT Feedback Form DONE
DONE  
20 emi-wn v.0.0.0 Worker Node Y1, Y2, Y3 glexec enabled Grid Ireland Feedback Form DONE
HEALTH-G Feedback Form
MAATG Feedback Form
GISELA Feedback Form
D4Science Feedback Form DONE
EGEE-SEE-CERT Feedback Form DONE
   
21 FTS v.2.2.6   Y1   ??   No
22 GFAL/lcg_util v.1.11.18 Part of -> UI Y1       No
23 gLExec v.0.8.3 To Deploy on -> WN Y1, Y2, Y3   HEALTH-G Feedback Form
MAATG Feedback Form
GISELA Feedback Form
  No
24 glite-gsoap/gss v.3.0.1 Part of -> all gLite Services         No
25 gLite-MPI v.1.0.0 To Deploy on -> WN Y1   HEALTH-G Feedback Form
MAATG Feedback Form
GISELA Feedback Form
  No
26 glite-proxyrenewal v.1.3.17 Proxy Renewal       DONE  
27 glite-yaim-core v.5.0.0 Part of -> all gLite Services       DONE No
28 gridsite v.1.7.12 Part of -> all gLite Services       DONE No
29 Hydra v.1.0.1 Hydra          
30 L&B v.3.0.5 L&B server Y1, Y2, Y3   CSIC Feedback Form    
31 LCAS v.1.4.0 Part of -> all gLite Services       DONE  
32 lcg-info-clients v1.0.0 Part of -> UI       DONE  
33 LCMAPS v.1.5.0 Part of -> all gLite Services       DONE  
34 LCMAPS-plugins-c-pep v.1.1.0 Part of -> all gLite Services       DONE  
35 LFC v.1.8.1 LFC Y2   CSIC Feedback Form
LIP Feedback Form
  No
36 RAL-SAGA-SD v.1.0.0 Part of -> UI       DONE  
37 site BDII v.1.0.0 site BDII Y2, Y3   LIP Feedback Form
HEALTH-G Feedback Form
MAATG Feedback Form
D4science Feedback Form DONE
EGEE-SEE-CERT Feedback Form DONE
DONE  
38 SLCS v.0.0.0           No
39 StoRM SE v.1.7.0 StorRM SE Y2, Y3   CSIC Feedback Form   No
40 top BDII v.1.0.0 Top BDII Y2, Y3   LIP Feedback Form   No
41 Trustmanager v.3.0.3 Part of -> all gLite Services       DONE  
42 UNICORE AIP v.2.0.0 ? Y2   PL-GRID Feedback Form DONE DONE  
43 UNICORE Client v.6.4.0 Part of UI Y2   PL-GRID Feedback Form DONE DONE  
44 UNICORE Gateway v.6.4.0 ? Y2   PL-GRID Feedback Form DONE DONE  
45 UNICORE HILA v.2.2 NO       DONE  
46 UNICORE Registry v.6.4.0 ? Y2   PL-GRID Feedback Form DONE DONE  
47 UNICORE sec libs v.2.0.0 ? Y2   PL-GRID Feedback Form DONE DONE  
48 UNICORE Services Environment v.6.4.0 ? Y2   PL-GRID Feedback Form DONE DONE  
49 UNICORE TSI v.6.4.0 ? Y2   PL-GRID Feedback Form DONE DONE  
50 UNICORE WS v.6.4.0 ? Y2   PL-GRID Feedback Form DONE DONE  
51 UNICORE XACML PDP v.2.0.0 ? Y2   PL-GRID Feedback Form DONE DONE  
52 UNICORE XNJS v.1.4.0 ? Y2   PL-GRID Feedback Form DONE DONE  
53 UNICORE XUUDB v.1.3.2 NO         No
54 UVOS v.1.4.1 ? Y2   PL-GRID Feedback Form   No
55 VOMS v.2.0.0 VOMS Server + Clients Y1, Y3   INFN-CNAF Feedback Form DONE  
56 VOMS-Admin 2.6.0 Voms Admin Server Y1, Y3   INFN-CNAF -> refer to VOMS DONE  
57 WMS v.3.3.0 WMS Y1, Y2, Y3   CSIC Feedback Form   No

(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

0 User Community Name/Role Services Used Use Case Short Name Feedback Form  
1 SHIWA -- --   1- Feedback Form  
2 WeNMR -- --   1- Feedback Form  
3 ATLAS(via LIP) -- --   --  
4 D4Science-II -- --   --  
5 EDGI          
6 Pl-Grid/QosCosGrid/Mapper          

5. Planning

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






Edit | Attach | Watch | Print version | History: r31 < r30 < r29 < r28 < r27 | Backlinks | Raw View | WYSIWYG | More topic actions
Topic revision: r31 - 2011-11-09 - 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