ARGUS collaboration
This twiki summarises the existing ARGUS components and their level of support. In order to cover the areas taken care of by SWITCH, a discussion on establishing an ARGUS collaboration is being discussed. This twiki aims at identifying which of these areas need to be covered by this collaboration.
ARGUS components
Note that the table below shows components currently maintained for user support, development, testing and certification.
Component Name |
Responsible |
Comments |
PEP client and server (Policy Enforcement Point) |
None |
SWITCH has completely stopped any grid related activities. No time from main developer to maintain ARGUS any more. |
argus-gsi-pep-callout |
argus-pep-api-c |
argus-pep-common |
argus-pep-server |
argus-pepcli |
argus-pep-api-java (deprecated) |
PAP (Policy Administration Point) |
INFN |
|
argus-pap-1.6.0-1 |
PDP (Policy Decision Point) |
None |
|
argus-pdp |
argus-pdp-pep-common |
Also part of PEP |
Config and Monitoring packages |
|
|
nagios-plugins-argus |
None |
yaim-argus_server |
INFN |
ARGUS EES |
NIKHEF |
|
ees |
ees-pepd-oh |
nagios-plugins-ees |
LCMAPS plugin for Argus |
NIKHEF |
|
lcmaps-plugins-c-pep |
User Support
Bug tracking
Documentation
Release preparation
- Done independently by each partner
- No common continuous build and integration system
- Testing - TOADD
- Codebase in Github: https://github.com/argus-authz
- Packages in Github: https://argus-authz.github.io/
- Valery Tschopp responsible for attending the EMT meetings as PT leader where requested changes are discussed, priorities and timelines agreed.
Release status
- One package (argus-pdp-pep-common-1.4.1-0) containing a fix for a top priority ticket GGUS:105666
was released in Github and installed at least at CERN - included in ARGUS v. 1.6.3
- Latest releases: