Difference between revisions of "Middleware argus interoperability"
Jump to navigation
Jump to search
(→UMD-3) |
(→UMD-3) |
||
Line 71: | Line 71: | ||
| | | | ||
! | ! | ||
| | | align="centre" style="background: none repeat scroll 0% 0% Red;" | NO | ||
| | | | ||
| | | | ||
Line 78: | Line 78: | ||
| | | | ||
| | | | ||
! | ! align="centre" style="background: none repeat scroll 0% 0% Red;" | NO | ||
| | | | ||
| | | |
Revision as of 15:20, 17 April 2013
Starting from March 2013, as part of the UMD quality criteria products requiring authentication are tested for the interoperability between argus and other middleware components. The following tables collects the products tested so far during the UMD software provisioning process.
UMD-2
Product name | Version | Released in UMD update # | Argus support | Comments | GGUS ticket |
---|---|---|---|---|---|
DPM | 1.8.6 | UMD2.4.0 | YES | Not tested yet | |
dCache | not tested yet | ||||
VOMS | Not available in production | ||||
SRM | YES | Available in production | |||
CREAM-CE | not tested yet |
UMD-3
Product name | Version | Released in UMD update # | Argus support | Comments | GGUS ticket |
---|---|---|---|---|---|
DPM | 1.8.6 | UMD2.4.0 | NO | ||
dCache | NO | ||||
VOMS | NO | ||||
SRM | YES | Available in production | |||
CREAM-CE | not tested yet |