Hallo Torsten,
> configuring ARGUS seems to be on the TODO-List for all sites now.
Most of the EGI sites.
> While waiting for my host certificate and after reading:
>
> https://twiki.cern.ch/twiki/bin/view/LCG/GlexecDeployment
> https://wlcg-tf.hep.ac.uk/wiki/Multi_User_Pilot_Jobs
> http://www.eu-emi.eu/products/-/asset_publisher/1gkD/content/argus-2#Documentation
> https://twiki.cern.ch/twiki/bin/view/EMI/ArgusEMIDocumentation
> https://twiki.cern.ch/twiki/bin/view/EGEE/AuthorizationFramework#Argus_Service_Installation
> https://wiki.nikhef.nl/grid/GLExec_Argus_Quick_Installation_Guide
> https://twiki.cern.ch/twiki/bin/view/EGEE/ArgusEMIDeployment
> https://twiki.cern.ch/twiki/bin/view/EGEE/ArgusEMIYaimConfiguration
>
> I would like to ask some questions here on the list (sorry if that is
> documented somewhere, I really tried to find all information which is
> spreaded on the web):
>
> - sharing gridmapdir: metioned on "GlexecDeployment" Twiki, NIKHEF's
> page says there are two modes but I couldn't easily see how to
> distinguish the two when configuring with YAIM. How do I tell YAIM which
> mode to run?
You cannot, that aspect is not managed by YAIM. However, if you also
configure CREAM to use Argus (recommended), there is no need for sharing
the gridmapdir at all: only Argus needs it.
> - is a re-installation/re-configuration of the CREAM CE neccessary
Reconfiguration for using Argus.
> (besides NFS-export gridmapdir)? I read that one has to publish a tag on
I will remove that requirement, it does not seem important any more.
What is important is to declare one's CEs as "gLExec" in the GOCDB,
such that they will automatically be tested by Ops, allowing for quick
detection of problems.
> the BDII, I suppose that can be easily done without re-configuring with
> yaim, but maybe some more changes are needed?
>
> - Are any changes to the batch system (SGE in our case) neccessary?
No changes are supposed to be needed.
> - We're moving our WNs from CentOS 5 to 6 now, so I would like to
> include glExec on the new WNs only, phasing out the old ones. The new
> WNs will be visible on a seperate queue. Is that a problem with the tag
> published by the CREAM CE (as in the transition phase, only a subset of
> the WNs would have glExec enabled).
It might mean your site fails the tests randomly, but that could be
tolerated during the next few months; we may be able to do something
better, though.
> - We are also running an ARC CE (not prodution ready yet). I haven't
> seen anything about glExec and ARC (besides a hint to NordUGrid). How
> does these two (glExec and ARC) interact?
I do not know if the ARC _CE_ can work with gLExec/Argus, but for the
WN the difference is irrelevant: there are a few CMS ARC sites that
already have gLExec on the WN. However, for ATLAS ARC sites that have
their jobs submitted via the ARC Control Tower there is no need to have
gLExec on the WN, as the identity change already happens earlier.
|