Hi Antonio,
the short answer is, it doesn't work and is a documentation problem.
I have just updated the two pages you are referring to. Note that you
referred to an outdated Nikhef wiki page, see the first line...
We started implementing it, but this has never been completed as it
turned out that all existing use cases could be solved in a different
way (server side, e.g. round-robin DNS etc.) and that the argus pep-c
client library also does not have the support.
Btw, we are all in different conferences at the moment and therefore not
very communicative.
Cheers,
Mischa
On Wed, Apr 10, 2013 at 07:35:08PM +0200, Antonio Delgado Peris wrote:
> Hi all,
>
> Several documentation pieces state that glexec can be configured
> with several Argus endpoints. E.g. in https://twiki.cern.ch/twiki/bin/view/LCG/Site-info_configuration_variables#ARGUS,
> it says:
>
> ARGUS_PEPD_ENDPOINTS If glexec is a PEP client, define the
> PEPD endpoints with this variable. It is a whitespace separated list
> of URLs, e.g. https://argus1.example.com:8154/authz
>
>
> Also, in http://wiki.nikhef.nl/grid/Set_up_gLExec_for_Argus, one can read:
>
> ARGUS_PEPD_ENDPOINTS="https://argus1.example.com:8154/authz
> https://argus2.example.com:8145/authz"
>
> In this example the site has two service endpoints; the quotes
> are necessary as this is interpreted shell code. Multiple endpoints
> may be defined for scale; the pep-c plug-in will randomly choose one
> endpoint to talk to, and automatically fail-over to the others. (??
> Verify please)
>
>
> The "(?? Verify please)" part makes me quite suspicious. And, in
> fact, I have tried it and this round-robin/failover does not seem to
> work.
>
> Instead of using YAIM, I have takes its job and manually modified
> /etc/lcmaps/lcmaps-glexec.db and, in the "pepc" part, added a couple
> of lines like the following:
>
> "--pep-daemon-endpoint-url https://gaergus.ciemat.es:8154/authz"
> "--pep-daemon-endpoint-url
> https://gaergus02.ciemat.es:8154/authz"
>
>
> But it does not work. If both argus servers work fine, glexec will
> ask only one of them. If this one fails, glexec will not fail-over,
> it will just return an error. If I enable debug info, I can see that
> the second time "--pep-daemon-endpoint-url" is parsed, the client
> complains with:
>
> 2013-04-10 19:08:55 DEBUG: pep_setoption: PEP#0
> option_endpoint_url already set to
> 'https://gaergus02.ciemat.es:8154/authz', freeing...
>
> So... is this known? Has anyone out there achieved that glexec works
> with multiple Argus endpoints? If so, how?
>
>
> BTW, I am using:
>
> Client:
> lcmaps-1.5.5-1.el6.x86_64
> glexec-0.9.6-1.el6.x86_64
> argus-pep-api-c-2.1.0-3.sl6.x86_64
> lcmaps-plugins-c-pep-1.2.2-1.el6.x86_64
>
> Server:
> argus-pap-1.5.1-1.el6.noarch
> argus-pepcli-2.1.0-2.sl6.x86_64
> emi-argus-1.5.0-1.sl6.x86_64
> argus-pdp-pep-common-1.3.1-1.sl6.noarch
> argus-pep-common-2.2.0-1.sl6.noarch
> argus-pdp-1.5.1-2.sl6.noarch
> argus-pep-api-c-2.1.0-3.sl6.x86_64
> argus-pep-server-1.5.1-2.sl6.noarch
>
>
> Thanks.
>
> Cheers,
> Antonio
--
Nikhef Room H155
Science Park 105 Tel. +31-20-592 5102
1098 XG Amsterdam Fax +31-20-592 5155
The Netherlands Email [log in to unmask]
__ .. ... _._. .... ._ ... ._ ._.. ._.. .._..
|