Reconfigure dCacheConfig to use both Cell and Module

As noted before, the preferred gPlazma configuration uses the cell method but it has been pointed out that the cell can block if there are inter-cell communication problems.

Because of this, for AGLT2 I will be changing our

/opt/d-cache/config/gPlazmaConfig

(really dCacheConfig) to go from:

#         gPlazma tuning
#  -----------------------------------------------------------------------
#   Do not change unless yoy know what you are doing.
#
gplazmaPolicy=${ourHomeDir}/etc/dcachesrm-gplazma.policy
#
#gPlazmaNumberOfSimutaneousRequests  30
#gPlazmaRequestTimeout               30
#
useGPlazmaAuthorizationModule=false
useGPlazmaAuthorizationCell=true
#delegateToGPlazma=false

TO

#         gPlazma tuning
#  -----------------------------------------------------------------------
#   Do not change unless yoy know what you are doing.
#
gplazmaPolicy=${ourHomeDir}/etc/dcachesrm-gplazma.policy
#
#gPlazmaNumberOfSimutaneousRequests  30
#gPlazmaRequestTimeout               30
#
useGPlazmaAuthorizationModule=true
useGPlazmaAuthorizationCell=true
#delegateToGPlazma=false

From the gPlazma Howto:

Using a GPLAZMA Cell with a direct-call fallback

Both the GPLAZMA cell and the direct call of the gplazma module may be specified. In that case, authentication will first be tried via the GPLAZMA cell, and if that does not succeed, authentication by direct invocation of gplazma methods will be tried. Place these lines in the batch file:

-use-gplazma-authorization-cell=true \
-use-gplazma-authorization-module=true \
-gplazma-authorization-module-policy=${gplazmaPolicy} \

Using one method for identity and another method for obligations (e.g., root path) is not supported.

Hopefully this will provide a fall-through option if the cell method blocks.

-- ShawnMcKee - 09 May 2009