Difference between revisions of "Middleware products verified for the support of IPv6"
Jump to navigation
Jump to search
Line 5: | Line 5: | ||
<br> | <br> | ||
{| | {| cellspacing="0" cellpadding="5" width="90%" style="border:1px solid black;" class="wikitable" | ||
|- style="background-color:darkgray;" | |- style="background-color:darkgray;" | ||
! Product name | ! Product name | ||
Line 18: | Line 18: | ||
| UMD3.0.0 UMD2.0.0 | | UMD3.0.0 UMD2.0.0 | ||
| bgcolor="#00cc00" | YES | | bgcolor="#00cc00" | YES | ||
| <br> | | <br> | ||
| <br> | | <br> | ||
|- | |- | ||
Line 25: | Line 25: | ||
| UMD3 and UMD4 | | UMD3 and UMD4 | ||
| bgcolor="#00cc00" | YES | | bgcolor="#00cc00" | YES | ||
| <br> | | Posible issues in SL6 <br> | ||
| <br> | | https://ggus.eu/?mode=ticket_info&ticket_id=126286<br> | ||
|- | |- | ||
| FTS | | FTS | ||
Line 32: | Line 32: | ||
| UMD3 and UMD4 | | UMD3 and UMD4 | ||
| bgcolor="#00cc00" | YES | | bgcolor="#00cc00" | YES | ||
| <br> | | <br> | ||
| <br> | | <br> | ||
|- | |- | ||
Line 39: | Line 39: | ||
| UMD3.0.0 UMD2.0.0 | | UMD3.0.0 UMD2.0.0 | ||
| bgcolor="#00cc00" | YES | | bgcolor="#00cc00" | YES | ||
| <br> | | <br> | ||
| <br> | | <br> | ||
|- | |- | ||
Line 46: | Line 46: | ||
| UMD3.0.0 UMD2.0.0 | | UMD3.0.0 UMD2.0.0 | ||
| bgcolor="#00cc00" | YES | | bgcolor="#00cc00" | YES | ||
| <br> | | <br> | ||
| <br> | | <br> | ||
|- | |- | ||
Line 53: | Line 53: | ||
| UMD3.3.0 | | UMD3.3.0 | ||
| bgcolor="#00cc00" | YES | | bgcolor="#00cc00" | YES | ||
| <br> | | <br> | ||
| <br> | | <br> | ||
|- | |- | ||
Line 60: | Line 60: | ||
| UMD3.x UMD2.x | | UMD3.x UMD2.x | ||
| bgcolor="#00cc00" | YES | | bgcolor="#00cc00" | YES | ||
| <br> | | <br> | ||
| <br> | | <br> | ||
|- | |- | ||
Line 72: | Line 72: | ||
| frontier-squid-3 | | frontier-squid-3 | ||
| ALL | | ALL | ||
| <br> | | <br> | ||
| bgcolor="#00cc00" | YES | | bgcolor="#00cc00" | YES | ||
| squid2 is not IPv6 ready. squid3 is in Preview already, investigating if it's possible to introduce in UMD4. | | squid2 is not IPv6 ready. squid3 is in Preview already, investigating if it's possible to introduce in UMD4. | ||
Line 79: | Line 79: | ||
| argus-pep-api-c, lcmaps-plugins-c-pep, argus-gsi-pep-callout, argus-pepcli, XACML | | argus-pep-api-c, lcmaps-plugins-c-pep, argus-gsi-pep-callout, argus-pepcli, XACML | ||
| ALL | | ALL | ||
| <br> | | <br> | ||
| bgcolor="#00cc00" | YES | | bgcolor="#00cc00" | YES | ||
| argus-pep-api-c, lcmaps-plugins-c-pep, argus-gsi-pep-callout, argus-pepcli rely fully on libcurl, hence is fully dual-stack. XACML | | argus-pep-api-c, lcmaps-plugins-c-pep, argus-gsi-pep-callout, argus-pepcli rely fully on libcurl, hence is fully dual-stack. XACML | ||
Line 87: | Line 87: | ||
|- | |- | ||
| lcmaps-plugins-scas-client | | lcmaps-plugins-scas-client | ||
| <br> | | <br> | ||
| <br> | | <br> | ||
| bgcolor="#ffcc00" | PARTIAL | | bgcolor="#ffcc00" | PARTIAL | ||
| lcmaps-plugins-scas-client does do a name lookup and socket creation and | | lcmaps-plugins-scas-client does do a name lookup and socket creation and | ||
Line 95: | Line 95: | ||
| <br> | | <br> | ||
|- | |- | ||
| dCache<br> | | dCache<br> | ||
| ALL<br> | | ALL<br> | ||
| <br> | | <br> | ||
| bgcolor="#00cc00" | YES | | bgcolor="#00cc00" | YES | ||
| All currently supported versions of dCache support IPv6 in dual-stack and stand-alone mode.<br> <br> Since dCache is a distributed system, it is possible to have a dCache cluster that comprises of a mixture of IPv4-only, dual-stack, and IPv6-only machines. This, too, is supported, but obviously an IPv4-connected client cannot be redirected to an IPv6-only node. In such cases, dCache will make internal replicas or proxy the data. | | All currently supported versions of dCache support IPv6 in dual-stack and stand-alone mode.<br> <br> Since dCache is a distributed system, it is possible to have a dCache cluster that comprises of a mixture of IPv4-only, dual-stack, and IPv6-only machines. This, too, is supported, but obviously an IPv4-connected client cannot be redirected to an IPv6-only node. In such cases, dCache will make internal replicas or proxy the data. | ||
| <br> | | <br> | ||
|} | |} |
Revision as of 17:39, 15 February 2017
Technology | Software Component Delivery | Software Provisioning | UMD Middleware | Cloud Middleware Distribution | Containers Distribution | Technology Glossary |
The following tables collects the products tested so far during the UMD software provisioning process.
Product name | Version | Released in UMD update # | IPv6 support | Comments | GGUS ticket |
---|---|---|---|---|---|
CREAM | 1.16.2 | UMD3.0.0 UMD2.0.0 | YES | ||
DPM | from 1.8.8 on | UMD3 and UMD4 | YES | Posible issues in SL6 |
https://ggus.eu/?mode=ticket_info&ticket_id=126286 |
FTS | every version of FTS | UMD3 and UMD4 | YES | ||
BDII | 1.1.3 | UMD3.0.0 UMD2.0.0 | YES | ||
LFC | 1.8.7 | UMD3.0.0 UMD2.0.0 | YES | ||
VOMS-SERVER | 2.0.11 | UMD3.3.0 | YES | ||
UI | 3.5.2-1 | UMD3.x UMD2.x | YES | ||
StoRM | 1.11.2 | UMD3.2.1 | PARTIAL | srmv server does not bind to IPv6 socket. workaround available. | https://ggus.eu/ws/ticket_info.php?ticket=99461 |
frontier-squid-3 | ALL | YES | squid2 is not IPv6 ready. squid3 is in Preview already, investigating if it's possible to introduce in UMD4. | ||
argus-pep-api-c, lcmaps-plugins-c-pep, argus-gsi-pep-callout, argus-pepcli, XACML | ALL | YES | argus-pep-api-c, lcmaps-plugins-c-pep, argus-gsi-pep-callout, argus-pepcli rely fully on libcurl, hence is fully dual-stack. XACML
does not create sockets or do name lookups. |
||
lcmaps-plugins-scas-client | PARTIAL | lcmaps-plugins-scas-client does do a name lookup and socket creation and
is currently not IPv6 compliant, but can only connect over IPv4. This is fixed in our trunk and will be released together with a fix for OpenSSL 1.1, which is currently blocked by VOMS. |
|||
dCache |
ALL |
YES | All currently supported versions of dCache support IPv6 in dual-stack and stand-alone mode. Since dCache is a distributed system, it is possible to have a dCache cluster that comprises of a mixture of IPv4-only, dual-stack, and IPv6-only machines. This, too, is supported, but obviously an IPv4-connected client cannot be redirected to an IPv6-only node. In such cases, dCache will make internal replicas or proxy the data. |
Additional wiki page with the tests performed for the operations tools by JRA1.