In order to test the correct deployment of Argus, after the installation/configuration some basic tests can be done using the pap-admin to store/list/update/remove policies. After this, the pepcli can be used to test authorization requests/responses.
pap-admin and pepcli are documented in the Argus main twiki.
In order to test the interaction glexec-Argus do something like this from a whitelisted account on the Worker Node:
Argus one virtual machine with SL5 64 bit
CE All CEs at GridKa are usable but please refer to cream-3-fzk.gridka.de. The queue must be "pps". All software installations are available on the PPS WNs. Enabled VOs: alice, atlas, cms, dteam, lhcb and ops.
WNs The PPS cluster has been extended to 300 cores
For alice a separate VOBox is available: test-mw-fzk.gridka.de
CNAF
Argus one virtual machine on SL5/64bit
CE One CREAM CE with two virtual WNs (SL5 64 bit). VOs enabled: dteam, infngrid, ops.
CE endpointdevce.cnaf.infn.it:8443/cream-pbs-cert
Results
Feedback from the experiments
Comments and issues from operations
SWITCH
The instructions to manually install the Argus compatible WNs are wrong. It is recommended that yaim be used instead.
FZK / KIT
reduction of the policy refresh time from 4hours to 15 mins requested: Angela opened the bug https://savannah.cern.ch/bugs/index.php?62281
List of issues
Issue
Reported by
Bug(s)
Status
Open/Closed
(Affects glexec on WMS-->GLEXEC-->CREAM chain): Wrongly configured GLITE_LOCATION makes sometimes impossible the discovery of the glexec executable
CERN
BUG:62810)fixed with patch 3760 (with provider)
open
The default policy refresh time set to 4hours seems too long
KIT
BUG:62281
To be discussed with JSPG
open
PEPd should require client-cert authentication support for connecting pep clients
Provide a report describing the issues being faced by CNAF for the installation of glexec on the WNs. INFN-T1 is experiencing a problem on the stability of GPFS interacting with the WN on demand system adopted locally into the resource center. Since they decided to provide virtual WNs for the pilot, the issue is affecting consequently the deployment of the glexec WN component into the site.
Provide instructions on how to preserve local policies during the upgrade of the Argus server to a newer version both in an e-mail to the sites and in the PATCH:3536 this was done on the 2nd of February This is done now at https://savannah.cern.ch/patch/?3536
Open a bug to request the reduction of the policy refresh time from 4hours to 15 mins 3-2-10: Angeal opened the bug https://savannah.cern.ch/bugs/index.php?62281
Provide the timeline for an installation of a reasonable scale (>100WNs) to be available to Atlas in order to test glexec in production Update 18-Dec (Andrea Ceccanti) : Converging on CANF offering the first large-scale installation. They are currently working to the installation at the T! and they hope to have finished before Christmas or alternatively by the 6th of January in order to be ready by the 15th. If the preliminary tests now undergoing suceed they are Ok to use Argus 1.1 whenit will be in status "Ready for Certification"
enumerate available deployment scenarios and see whether new developments have to be requested (or re-negotiations are needed with the sites) Update 26-Nov. After discussion with JRA1 and SA3 it was proposed to extend the support of the clients on SL4 . A new patch has been requested to the developers Antonio Update 1-Dec During the last meeting Gianni was put in charge to open the bug with the change requestUpdate 18-Dec (Gianni) : All new developments are now tracked by bugs
installation in progress at all sites. Platform expected available by the 15th of Dec
1-Dec-2009 : Fist installaiton at SWITCH available for testing
1-Dec-2009 : kick-off with the experiments (PPIslandKickOff2009x12x01)
25-Nov-2009 : kick-off with sites (PPIslandKickOff2009x11x25)
24-Nov-2009 : Pilot Home page created