Difference between revisions of "IPV6 Assessment"
Jump to navigation
Jump to search
Infrastructure status and plans
(→UMD) |
|||
Line 137: | Line 137: | ||
|- style="background-color:darkgray;" | |- style="background-color:darkgray;" | ||
! Product name | ! Product name | ||
! IPv6 support | ! IPv6 support | ||
! Comments | ! Comments | ||
Line 144: | Line 142: | ||
|- | |- | ||
| CREAM | | CREAM | ||
| bgcolor="#00cc00" | YES | | bgcolor="#00cc00" | YES | ||
| <br> | | <br> | ||
Line 151: | Line 147: | ||
|- | |- | ||
| DPM | | DPM | ||
| bgcolor="#00cc00" | YES | | bgcolor="#00cc00" | YES | ||
| Posible issues in SL6 <br> | | Posible issues in SL6 <br> | ||
Line 158: | Line 152: | ||
|- | |- | ||
| FTS | | FTS | ||
| bgcolor="#00cc00" | YES | | bgcolor="#00cc00" | YES | ||
| <br> | | <br> | ||
Line 165: | Line 157: | ||
|- | |- | ||
| BDII | | BDII | ||
| bgcolor="#00cc00" | YES | | bgcolor="#00cc00" | YES | ||
| <br> | | <br> | ||
Line 172: | Line 162: | ||
|- | |- | ||
| LFC | | LFC | ||
| bgcolor="#00cc00" | YES | | bgcolor="#00cc00" | YES | ||
| <br> | | <br> | ||
Line 179: | Line 167: | ||
|- | |- | ||
| VOMS-SERVER | | VOMS-SERVER | ||
| bgcolor="#00cc00" | YES | | bgcolor="#00cc00" | YES | ||
| <br> | | <br> | ||
Line 186: | Line 172: | ||
|- | |- | ||
| UI | | UI | ||
| bgcolor="#00cc00" | YES | | bgcolor="#00cc00" | YES | ||
| <br> | | <br> | ||
Line 193: | Line 177: | ||
|- | |- | ||
| StoRM | | StoRM | ||
| bgcolor="#00cc00" | YES<br> | |||
| <br> | |||
| bgcolor="# | | <br> | ||
| | |||
| | |||
|- | |- | ||
| frontier-squid-3 | | frontier-squid-3 | ||
| 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 207: | Line 187: | ||
|- | |- | ||
| 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 | ||
| 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 216: | Line 194: | ||
|- | |- | ||
| lcmaps-plugins-scas-client | | lcmaps-plugins-scas-client | ||
| 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 225: | Line 201: | ||
|- | |- | ||
| dCache<br> | | dCache<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. |
Revision as of 11:26, 30 October 2017
Core/EGI services
UMD
The following tables collects the products tested so far during the UMD software provisioning process. Moved from https://wiki.egi.eu/wiki/Middleware_products_verified_for_the_support_of_IPv6
Product name | IPv6 support | Comments | GGUS ticket |
---|---|---|---|
CREAM | YES | ||
DPM | YES | Posible issues in SL6 |
https://ggus.eu/?mode=ticket_info&ticket_id=126286 |
FTS | YES | ||
BDII | YES | ||
LFC | YES | ||
VOMS-SERVER | YES | ||
UI | YES | ||
StoRM | YES |
||
frontier-squid-3 | 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 | 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 |
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. |
CMD and FedCloud product readiness
Infrastructure status and plans
NGI |
Status and plans | Total sites |
Sites implementing IPv6 |
Is NREN ready? |
Willing tutorial on IPv6 in general | Willing tutorial on IPv6 security | Comments |
AsiaPacific |
|||||||
CERN |
|||||||
NGI_AEGIS |
|||||||
NGI_ARMGRID |
|||||||
NGI_BG |
|||||||
NGI_BY |
|||||||
NGI_CH |
|||||||
NGI_CZ |
|||||||
NGI_DE |
|||||||
NGI_FI |
|||||||
NGI_FRANCE |
|||||||
NGI_GE |
In Georgia there is only one Grid site and it is IPv4 only, the same is GRENA network. Currently we are not planing to introduce IPv6 because there is still no demand in it. In this situation mentioned tutorials will not be very useful for our system administrators. | ||||||
NGI_GRNET |
|||||||
NGI_HR |
|||||||
NGI_HU |
|||||||
NGI_IBERGRID |
|||||||
NGI_IL |
|||||||
NGI_IT |
|||||||
NGI_MARGI |
|||||||
NGI_MD |
|||||||
NGI_ME |
WON'T_DO | 1 |
0 |
NO |
|||
NGI_NDGF |
|||||||
NGI_NL |
|||||||
NGI_PL |
|||||||
NGI_RO |
|||||||
NGI_SI |
|||||||
NGI_SK |
|||||||
NGI_TR |
WILL_DO | 3 |
3 |
YES |
YES |
YES |
|
NGI_UA |
|||||||
NGI_UK |
|||||||
ROC_Canada |
|||||||
ROC_LA |
|||||||
Russia |
|||||||
IDGF |
|||||||
NGI_CHINA |
WLCG plans
References
- old wiki https://wiki.egi.eu/wiki/IPv6
- IPv6 test http://ipv6-test.com/
- status of the WLCG Tier0 and Tier 1 sites http://hepix-ipv6.web.cern.ch/sites-connectivity