Difference: RegressionTestWorkPlan (22 vs. 23)

Revision 232012-01-13 - MassimoSgaravatto

Line: 1 to 1
 
META TOPICPARENT name="CreamTesting"

Regression Test Work Plan

Line: 643 to 643
 
Added:
>
>

Bug #87690 Not possible to map different queues to different clusters for CREAM configured in cluster mode - Not Implemented

Configure via yaim a CREAM CE in cluster mode with different queues mapped to different clusters, e.g.:

CREAM_CLUSTER_MODE=yes
CE_HOST_cream_47_pd_infn_it_QUEUES="creamtest1 creamtest2"
QUEUE_CREAMTEST1_CLUSTER_UniqueID=cl1id
QUEUE_CREAMTEST2_CLUSTER_UniqueID=cl2id

Then query the resource bdii of the CREAM, and check the GlueForeignKey attributes of the different glueCEs: they should refer to the specified clusters:

ldapsearch -h cream-47.pd.infn.it -p 2170 -x -b o=grid objectclass=GlueCE GlueForeignKey
# extended LDIF
#
# LDAPv3
# base <o=grid> with scope subtree
# filter: objectclass=GlueCE
# requesting: GlueForeignKey 
#

# cream-47.pd.infn.it:8443/cream-lsf-creamtest2, resource, grid
dn: GlueCEUniqueID=cream-47.pd.infn.it:8443/cream-lsf-creamtest2,Mds-Vo-name=r
 esource,o=grid
GlueForeignKey: GlueClusterUniqueID=cl12d

# cream-47.pd.infn.it:8443/cream-lsf-creamtest1, resource, grid
dn: GlueCEUniqueID=cream-47.pd.infn.it:8443/cream-lsf-creamtest1,Mds-Vo-name=r
 esource,o=grid
GlueForeignKey: GlueClusterUniqueID=cl1id

Bug #87799 Add yaim variables to configure the GLUE 2 WorkingArea attributes - Not Implemented

Set all (or some) of the following yaim variables:

WORKING_AREA_SHARED
WORKING_AREA_GUARANTEED
WORKING_AREA_TOTAL
WORKING_AREA_FREE
WORKING_AREA_LIFETIME
WORKING_AREA_MULTISLOT_TOTAL
WORKING_AREA_MULTISLOT_FREE
WORKING_AREA_MULTISLOT_LIFETIME

and then configure via yaim. Then query the resource bdii of the CREAM CE and verify that the relevant attributes of the glue2 ComputingManager object are set.

Bug #88078 CREAM DB names should be configurable - Not Implemented

Configure from scratch a CREAM CE setting the yaim variables: CREAM_DB_NAME and DELEGATION_DB_NAME, e.g.:

CREAM_DB_NAME=abc
DELEGATION_DB_NAME=xyz

and then configure via yaim.

Then check if the two databases have been created:

# mysql -u xxx -p Enter password: Welcome to the MySQL monitor. Commands end with ; or \g. Your MySQL connection id is 7176 Server version: 5.0.77 Source distribution

Type 'help;' or '\h' for help. Type '\c' to clear the buffer.

mysql> show databases;

+--------------------+

Database
+--------------------+
information_schema
abc
test
xyz
+--------------------+ 4 rows in set (0.02 sec)

Try also a job submission to verify if everything works properly.

Bug #89489 yaim plugin for CREAM CE does not execute a check function due to name mismatch - Not Implemented

Configure a CREAM CE via yaim and save the yaim output. It should contain the string:

INFO: Executing function: config_cream_gip_scheduler_plugin_check

Bug #89664 yaim-cream-ce doesn't manage spaces in CE_OTHERDESCR - Not Implemented

Try to set the yaim variable CE_OTHERDESCR to:

CE_OTHERDESCR="Cores=1"

Perform the following ldap query on the resource bdii:

ldapsearch -h <CREAM CE node> -x -p 2170 -b "o=glue" objectclass=GLUE2ExecutionEnvironment GLUE2EntityOtherInfo

This should also return:

GLUE2EntityOtherInfo: Cores=1

Try then to set the yaim variable CE_OTHERDESCR to:

CE_OTHERDESCR="Cores=2, Benchmark=4-HEP-SPEC06"

and reconfigure via yaim.

Perform the following ldap query on the resource bdii:

ldapsearch -h <CREAM CE node> -x -p 2170 -b "o=glue" objectclass=GLUE2ExecutionEnvironment GLUE2EntityOtherInfo

This should also return:

GLUE2EntityOtherInfo: Cores=2

Then perform the following ldap query on the resource bdii:

ldapsearch -h <CREAM CE node> -x -p 2170 -b "o=glue" objectclass=Glue2Benchmark 

This should return something like:

# cream-47.pd.infn.it_hep-spec06, cream-47.pd.infn.it, ppp, resource, glue
dn: GLUE2BenchmarkID=cream-47.pd.infn.it_hep-spec06,GLUE2ResourceID=cream-47.pd.infn.it,GLUE2ServiceID=ppp,GLUE2GroupID=resource,o=glue
GLUE2BenchmarkExecutionEnvironmentForeignKey: cream-47.pd.infn.it
GLUE2BenchmarkID: cream-47.pd.infn.it_hep-spec06
GLUE2BenchmarkType: hep-spec06
objectClass: GLUE2Entity
objectClass: GLUE2Benchmark
GLUE2EntityCreationTime: 2012-01-13T17:07:52Z
GLUE2BenchmarkValue: 4
GLUE2EntityOtherInfo: InfoProviderName=glite-ce-glue2-benchmark-static
GLUE2EntityOtherInfo: InfoProviderVersion=1.0
GLUE2EntityOtherInfo: InfoProviderHost=cream-47.pd.infn.it
GLUE2BenchmarkComputingManagerForeignKey: ppp_Manager
GLUE2EntityName: Benchmark hep-spec06

Bug #89784 Improve client side description of authorization failure - Not Implemented

Try to remove the lsc files for your VO and try a submission to that CE.

It should return an authorization error.

Then check the glite-ce-cream.log. It should report something like:

13 Jan 2012 18:21:21,270 org.glite.voms.PKIVerifier - Cannot find usable certificates to validate the AC. Check that the voms server host certificate is in your vomsdir directory.
13 Jan 2012 18:21:21,602 org.glite.ce.commonj.authz.gjaf.LocalUserPIP - glexec error: [gLExec]:   LCAS failed, see '/var/log/glexec/lcas_lcmaps.log' for more info.
13 Jan 2012 18:21:21,603 org.glite.ce.commonj.authz.gjaf.ServiceAuthorizationChain - Failed to get the local user id via glexec: glexec error: [gLExec]:   LCAS failed, see '/var/log/glexec/lcas_lcmaps.log' for more info.
org.glite.ce.commonj.authz.AuthorizationException: Failed to get the local user id via glexec: glexec error: [gLExec]:   LCAS failed, see '/var/log/glexec/lcas_lcmaps.log' for more info.
 

Fixes provided with CREAM 1.13.3

 
This site is powered by the TWiki collaboration platformCopyright © 2008-2022 by the contributing authors. All material on this collaboration platform is the property of the contributing authors.
Ideas, requests, problems regarding TWiki? Send feedback