Alert.png The wiki is deprecated and due to be decommissioned by the end of September 2022.
The content is being migrated to other supports, new updates will be ignored and lost.
If needed you can get in touch with EGI SDIS team using operations @ egi.eu.

Difference between revisions of "Middleware products verified for the support of IPv6"

From EGIWiki
Jump to navigation Jump to search
 
(One intermediate revision by the same user not shown)
Line 1: Line 1:
{{Tech menubar}} {{Middleware_menubar}}  
{{Tech menubar}} {{Middleware_menubar}}  


<br> The following tables collects the products tested so far during the UMD software provisioning process.
<br>  


<br>  
<br>  


{| cellspacing="0" cellpadding="5" width="90%" style="border:1px solid black;" class="wikitable"
Moved to https://wiki.egi.eu/wiki/IPV6_Assessment#UMD.2FCMD_and_FedCloud_products
|- style="background-color:darkgray;"
! Product name
! Version
! Released in UMD update #
! IPv6 support
! Comments
! GGUS ticket
|-
| CREAM
| 1.16.2
| UMD3.0.0 UMD2.0.0
| bgcolor="#00cc00" | YES
| <br>
| <br>
|-
| DPM
| from 1.8.8 on
| UMD3 and UMD4
| bgcolor="#00cc00" | YES
| Posible issues in SL6 <br>
| https://ggus.eu/?mode=ticket_info&amp;ticket_id=126286<br>
|-
| FTS
| every version of FTS
| UMD3 and UMD4
| bgcolor="#00cc00" | YES
| <br>
| <br>
|-
| BDII
| 1.1.3
| UMD3.0.0 UMD2.0.0
| bgcolor="#00cc00" | YES
| <br>
| <br>
|-
| LFC
| 1.8.7
| UMD3.0.0 UMD2.0.0
| bgcolor="#00cc00" | YES
| <br>
| <br>
|-
| VOMS-SERVER
| 2.0.11
| UMD3.3.0
| bgcolor="#00cc00" | YES
| <br>
| <br>
|-
| UI
| 3.5.2-1
| UMD3.x UMD2.x
| bgcolor="#00cc00" | YES
| <br>
| <br>
|-
| StoRM
| 1.11.2
| UMD3.2.1
| bgcolor="#ffcc00" | PARTIAL
| srmv server does not bind to IPv6 socket. workaround available.
| https://ggus.eu/ws/ticket_info.php?ticket=99461
|-
| frontier-squid-3
| ALL
| <br>
| bgcolor="#00cc00" | YES
| squid2 is not IPv6 ready. squid3 is in Preview already, investigating if it's possible to introduce in UMD4.
| <br>
|-
| argus-pep-api-c, lcmaps-plugins-c-pep, argus-gsi-pep-callout, argus-pepcli, XACML
| ALL
| <br>
| 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
does not create sockets or do name lookups.
 
| <br>
|-
| lcmaps-plugins-scas-client
| <br>
| <br>
| bgcolor="#ffcc00" | 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.
 
| <br>
|-
| dCache<br>
| ALL<br>
| <br>
| 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.&nbsp; 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> Additional wiki page with the tests performed for the [[EGI-JRA1 IPv6 Readiness|operations tools]] by JRA1.  
<br> Additional wiki page with the tests performed for the [[EGI-JRA1 IPv6 Readiness|operations tools]] by JRA1.  


[[Category:Middleware]]
[[Category:Middleware]]

Latest revision as of 12:03, 24 October 2017