Middleware products verified for the support of IPv6
|Technology||Software Component Delivery||Software Provisioning||UMD Middleware||Cloud Middleware Distribution||Containers Distribution||Technology Glossary|
|Middleware menu:||Home •||Software Calendars •||Technology Providers •||UMD Release Schedule •||UMD Products Overview •||UMD Products ID Cards •||Release and deployment process •||Middleware Requirements|
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|
|DPM||from 1.8.8 on||UMD3 and UMD4||YES|| Posible issues in SL6
|FTS||every version of FTS||UMD3 and UMD4||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|
||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.
||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.
||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.