Tags:
create new tag
,
view all tags
---+!! gLite-CLUSTER Test work plan %TOC% ---++ Unit tests gLite-CLUSTER is just a set of yaim configuration scripts. So there are not unit tests. ---++ Deployment tests ---+++ Installation The following should be tested: * Fresh installation of a gLite-CLUSTER node, doing what is documented in the CREAM System administratror guide (Section: "Installation of a glite-cluster node") * Update from a previous version of the same EMI major release. This should be tested doing a simple =yum update=. * Update from a previous EMI major release. TBD The following installation and update scenarios should be tested: The following installation and update scenarios should be tested: * gLite-CLUSTER deployed alone * gLite-CLUSTER deployed together with a CREAM CE node in cluster mode ---+++ Configuration The configuration via yaim should be tested. The following scenarios should be tested: * gLite-CLUSTER deployed alone * gLite-CLUSTER deployed together with a CREAM CE node in cluster mode ---++ System tests ---+++ Basic functionality tests ---++++ gridftp test Try a gridftp (e.g. using gridftp) towards the gLite cluster node The test must be done in the two scenarios: * when ARGUS is used (=USE_ARGUS=yes=) * when ARGUS is not used (=USE_ARGUS=no=) ---++++ VO tag dir test Check if under =/opt/glite/var/info= there is a directory for each subcluster. Check that within each of these directories, there is a directory per VO which contains a file called <VO name>.list Status: %RED%Not Implemented%ENDCOLOR% ---++++ Resource BDII test Check if the resource bdii publishes all the relevant objectclasses for both glue1 and glue2. * Check if the resource BDII publishes glue 1 GlueCluster objectclasses. There should be at least one of such objectclasses <verbatim> ldapsearch -h <gLite-CLUSTER hostname> -x -p 2170 -b "o=grid" objectclass=GlueCluster </verbatim> * Check if the resource BDII publishes glue 1 GlueSubCluster objectclasses. There should be at least one of such objectclasses <verbatim> ldapsearch -h <gLite-CUSTER hostname> -x -p 2170 -b "o=grid" objectclass=GlueSubCluster </verbatim> * Check if the resource BDII publishes glue 2 GLUE2ComputingService objectclasses. There should be one GLUE2ComputingService objectclass: <verbatim> ldapsearch -h <gLite-CUSTER hostname> -x -p 2170 -b "o=glue" objectclass=GLUE2ComputingService </verbatim> * Check if the resource BDII publishes glue 2 GLUE2Manager objectclasses. There should be one GLUE2Manager objectclass. <verbatim> ldapsearch -h <gLite-CUSTER hostname> -x -p 2170 -b "o=glue" objectclass=GLUE2Manager </verbatim> * Check if the resource BDII publishes glue 2 GLUE2Share objectclasses. There should be one GLUE2Share objectclass per each VOview. <verbatim> ldapsearch -h <gLite-CUSTER hostname> -x -p 2170 -b "o=glue" objectclass=GLUE2Share </verbatim> * Check if the resource BDII publishes glue 2 GLUE2ExecutionEnvironment objectclasses. There should be at least one GLUE2ExecutionEnvironment objectclass. <verbatim> ldapsearch -h <gLite-CUSTER hostname> -x -p 2170 -b "o=glue" objectclass=GLUE2ExecutionEnvironment </verbatim> * Check if the resource BDII publishes glue 2 GLUE2ComputingEndPoint objectclasses with GLUE2EndpointInterfaceName equal to org.glite.ce.ApplicationPublisher. There should be one of such objectclass. <verbatim> ldapsearch -h <gLite-CUSTER hostname> -x -p 2170 -b "o=glue" "(&(objectclass=GLUE2ComputingEndPoint)(GLUE2EndpointInterfaceName=org.glite.ce.ApplicationPublisher))" </verbatim> Status: %RED%Not Implemented%ENDCOLOR% ---++++ Dynamic information test Log as root on the gLite-CLUSTER node and execute: <verbatim> /sbin/runuser -s /bin/sh ldap -c "/var/lib/bdii/gip/plugin/glite-info-dynamic-lrms" </verbatim> This should print some information for the glue2 Glue2Manager objectclass and for each Glue2Share objectclass. Check if the printed information is correct. Query the resource BDII of the gLite-CLUSTER and check if the published information is the same as the one returned by the glite-info-dynamic-lrms script. Status: %RED%Not Implemented%ENDCOLOR% ---+++ Regression tests See: http://wiki.italiangrid.it/twiki/bin/view/CREAM/RegressionTestWorkPlan ---+++ Performance and scalability tests None ---+++ Standard compliance and conformance tests ---++++ Glue 1 compliance Glue 1 compliance of the information published by the gLite-CLUSTER resource bdii should be tested. This should be done using [[https://tomtools.cern.ch/confluence/display/IS/GLUEValidator][GlueValidator]]. Status: %GREEN%Implemented in the !GlueValidator testsuite%ENDCOLOR% ---++++ Glue 2 compliance Glue 2 compliance of the information published by the gLite-CLUSTER resource bdii should be tested. This should be done using [[https://tomtools.cern.ch/confluence/display/IS/GLUEValidator][GlueValidator]]. Status: %GREEN%Implemented in the !GlueValidator testsuite%ENDCOLOR% -- Main.MassimoSgaravatto - 2011-12-29
E
dit
|
A
ttach
|
PDF
|
H
istory
: r4
<
r3
<
r2
<
r1
|
B
acklinks
|
V
iew topic
|
M
ore topic actions
Topic revision: r4 - 2013-03-11
-
PaoloAndreetto
Home
Site map
CEMon web
CREAM web
Cloud web
Cyclops web
DGAS web
EgeeJra1It web
Gows web
GridOversight web
IGIPortal web
IGIRelease web
MPI web
Main web
MarcheCloud web
MarcheCloudPilotaCNAF web
Middleware web
Operations web
Sandbox web
Security web
SiteAdminCorner web
TWiki web
Training web
UserSupport web
VOMS web
WMS web
WMSMonitor web
WeNMR web
General Doc
Functional Description
Batch System Support
CREAM and Information Service
Release Notes
Known Issues
Security in CREAM
Nagios Probes to monitor CREAM and WN
Papers
Presentations
User Doc
CREAM User Guide for EMI-1
CREAM User Guide for EMI-2
CREAM User Guide for EMI-3
CREAM JDL Guide
BLAH User Guide
Troubleshooting Guide
System Administrator Doc
System Administrator Guide for CREAM (EMI-3 release)
System Administrator Guide for CREAM (EMI-2 release)
System Administrator Guide for CREAM (EMI-1 release)
The CREAM configuration file
The CEMonitor configuration file
The CREAM CE Service Reference Card (EMI-2 release)
The CREAM CE Service Reference Card (EMI-1 release)
Batch System related documentation
Troubleshooting Guide
The guide for integrating EMIR in CREAM
]
Developers Doc
CREAM Client API C++ Documentation
CREAM Client API for Python
Other Doc
Contacts
Moving to CREAM from LCG-CE
Testing
Internal Collaboration Information
Credits
CREAM Web utilities
Create New Topic
Index
Search
Changes
Notifications
RSS Feed
Statistics
Preferences
P
P
View
Raw View
Print version
Find backlinks
History
More topic actions
Edit
Raw edit
Attach file or image
Edit topic preference settings
Set new parent
More topic actions
Account
Log In
E
dit
A
ttach
Copyright © 2008-2024 by the contributing authors. All material on this collaboration platform is the property of the contributing authors.
Ideas, requests, problems regarding TWiki?
Send feedback