This wiki is obsolete, see the NorduGrid web pages for up to date information.
Testing/ARC-InfoSys 1.0.1
Component:
Savanah task:https://savannah.cern.ch/task/?20928
ETICS Configuration name:
VCS TAG:
EMI Release:
Platform:
Author:
Date:
Deployment tests
Clean Instalation
Update: After installation of BDII 5.2.4-1.el5 from the same repositories, everything works. Also included a query to the index, a ldap registration attempt and enabled all schemas. I think enabling all schemas doesn't make sense, our EGIIS just copes with nordugrid schema AFAIK. --Florido Paganelli 10:58, 14 July 2011 (CEST))
- Description of problem (for example description of bug with link to bugzilla)
Clean install of the ARC Infosys on a SL5 x86_64 machine
- Test scenario (all details needed to reproduce test)
- Freshly installed SL5 system
- Installed testing.repo from EMI repositories
- run
yum update
- Installed metapackage with
yum install nordugrid-arc-information-index
- copied
arc.infosys.template
to/etc/arc.conf
from svn doc trunk [1] - added the following line to
/etc/hosts
:130.235.185.195 gridtest.hep.lu.se
- Installed CA and host certificates obtained by InstantCA.
- enabled slapd error logging by adding the following line to
/etc/syslog.conf
- edited
/etc/arc.conf
:# openldap server config [infosys] #hostname="" user="root" #infosys_compat="enable" overwrite_config="yes" port="2135" debug="3" slapd_loglevel="3" threads="256" registrationlog="/tmp/inforegistration.log" providerlog="/tmp/infoprovider.log" provider_loglevel="3" infosys_nordugrid="enable" infosys_glue12="enable" infosys_glue2_ldap="enable" [infosys/glue12] resource_location="Lund, Sweden" resource_latitude="55.7000" resource_longitude="13.1833" provide_glue_site_info="true" cpu_scaling_reference_si00="2400" processor_other_description="Cores=1" glue_site_web="http://www.hep.lu.se/" glue_site_unique_id="TESTGIIS" [infosys/index/TESTGIIS] name="TESTGIIS" allowreg=* ## Uncomment and CUSTOMIZE the registration blocks in order to connect your ## GIIS to a grid (via a higher level GIIS). Multiple registration blocks are ## possible. #[infosys/index/TESTGIIS/registration/to_top1] #targethostname="index.myinstitute.org" #targetport="2135" #targetsuffix="mds-vo-name=UpperIndex,o=grid" #regperiod="300"
- Issued
service grid-infosys start
- to test that everithing was running, I issued:
ldapsearch -x -h gridtest.hep.lu.se -p 2135 -b 'Mds-vo-name=TESTGIIS,o=Grid' -s base ldapsearch -x -h gridtest.hep.lu.se -p 2135 -b 'o=grid' ldapsearch -x -h gridtest.hep.lu.se -p 2135 -b 'o=glue' ldapsearch -x -h gridtest.hep.lu.se -p 2135 -b 'o=infosys'
- checked logfiles.
- To test joining the index, I added the following to an arc.conf cluster:
[infosys/cluster/registration/toTESTGIIS] targethostname="gridtest.hep.lu.se" targetport="2135" targetsuffix="mds-vo-name=TESTGIIS,o=grid" regperiod="50"
and restarted its infosys.
local4.* /var/log/slapd.log
- Infrastructure used to perform test (for example testbed with specification of software)
Virtual Box Virtual machine with SL5 x86_64 installed. Bridged network to external network. No tests joining an index have been performed.
Tests for a cluster to join have been performed. The cluster machine was a physical server running SL5 and ARC CE
- Expected results
- R1 All the ldap queries must give
result : ... Success
answer, that means that the ldap server is running and returning the
- R1 All the ldap queries must give
proper objectClasses.
- R2 no critical error in logfiles
- R3 a cluster successfully registers to the index.
- Output of test (for example stdout, stderr)
- R1 passed
ldapsearch -x -p 2135 -b "mds-vo-name=TESTGIIS, o=Grid" -h gridtest.hep.lu.se -s base # extended LDIF # # LDAPv3 # base <mds-vo-name=TESTGIIS, o=Grid> with scope baseObject # filter: (objectclass=*) # requesting: ALL # # search result search: 2 result: 0 Success text: Successful query # numResponses: 1 ldapsearch -x -h arctest -p 2135 -b 'o=grid' # extended LDIF # # LDAPv3 # base <o=grid> with scope subtree # filter: (objectclass=*) # requesting: ALL # # Grid dn: o=Grid objectClass: organization o: Grid # search result search: 2 result: 0 Success # numResponses: 2 # numEntries: 1 ldapsearch -x -h arctest -p 2135 -b 'o=glue' # extended LDIF # # LDAPv3 # base <o=glue> with scope subtree # filter: (objectclass=*) # requesting: ALL # # glue dn: o=glue objectClass: top objectClass: organization o: glue # search result search: 2 result: 0 Success # numResponses: 2 # numEntries: 1 ldapsearch -x -h arctest -p 2135 -b 'o=infosys' # extended LDIF # # LDAPv3 # base <o=infosys> with scope subtree # filter: (objectclass=*) # requesting: ALL # # infosys dn: o=infosys objectClass: organization o: infosys # zip, infosys dn: CompressionType=zip,o=infosys objectClass: CompressedContent Hostname: localhost CompressionType: zip Data: file:///var/run/bdii/archive/11-06-22-19-21-14-snapshot.gz # localhost, infosys dn: Hostname=localhost,o=infosys objectClass: UpdateStats Hostname: localhost FailedDeletes: 0 ModifiedEntries: 0 DeletedEntries: 0 UpdateTime: 1 FailedAdds: 2 FailedModifies: 0 TotalEntries: 2 QueryTime: 0 NewEntries: 2 DBUpdateTime: 0 ReadTime: 0 PluginsTime: 0 ProvidersTime: 0 # search result search: 2 result: 0 Success # numResponses: 4 # numEntries: 3
- R2 PASSED: no error on slapd logs.
- R3 PASSED. The cluster shows up in the query:
ldapsearch -x -p 2135 -b "mds-vo-name=TESTGIIS, o=Grid" -h gridtest.hep.lu.se -s base # extended LDIF # # LDAPv3 # base <mds-vo-name=TESTGIIS, o=Grid> with scope baseObject # filter: (objectclass=*) # requesting: ALL # # piff.hep.lu.se, TESTGIIS, grid dn: nordugrid-cluster-name=piff.hep.lu.se,Mds-Vo-name=TESTGIIS,o=grid objectClass: Mds objectClass: MdsVoOp objectClass: MdsService objectClass: MdsServiceLdap Mds-Service-type: ldap Mds-Service-hn: piff.hep.lu.se Mds-Service-port: 2135 Mds-Service-Ldap-suffix: nordugrid-cluster-name=piff.hep.lu.se,Mds-Vo-name=loc al,o=Grid Mds-Service-Ldap-sizelimit: 0 Mds-Service-Ldap-timeout: 30 Mds-Service-Ldap-cachettl: 0 Mds-Bind-Method-servers: ANONYM-ONLY Mds-Reg-status: VALID # search result search: 2 result: 0 Success text: Successful query # numResponses: 2 # numEntries: 1
- Comments and proposals (should be used as feedback for developers)
- The service starts.
- after installation of BDII 5.2.4-1.el5 from the same repositories, bug https://ggus.eu/ws/ticket_info.php?ticket=71581 seems solved,
- registration of a cluster to the service works.
- The final decision PASSED/FAILED
PASSED
Upgrage installation
Tester: Jozef Date: 15.7.2011