Difference between revisions of "IPV6 Assessment"
Jump to navigation
Jump to search
Infrastructure status and plans
Line 11: | Line 11: | ||
| style="overflow:hidden;padding:2px 3px 2px 3px;vertical-align:bottom;" | Adrian Coveney | | style="overflow:hidden;padding:2px 3px 2px 3px;vertical-align:bottom;" | Adrian Coveney | ||
| style="overflow:hidden;padding:2px 3px 2px 3px;vertical-align:bottom;" bgcolor="#ffff00" | PARTIAL | | style="overflow:hidden;padding:2px 3px 2px 3px;vertical-align:bottom;" bgcolor="#ffff00" | PARTIAL | ||
| style="overflow:hidden;padding:2px 3px 2px 3px;vertical-align:bottom;" | Portal is OK, | | style="overflow:hidden;padding:2px 3px 2px 3px;vertical-align:bottom;" | Portal is OK, updates to SSM required to support IPv6. | ||
|- style="height:24px;" | |- style="height:24px;" | ||
| style="overflow:hidden;padding:2px 3px 2px 3px;vertical-align:bottom;" bgcolor="#ffccff" | Activities and services for the long tail of science<br> | | style="overflow:hidden;padding:2px 3px 2px 3px;vertical-align:bottom;" bgcolor="#ffccff" | Activities and services for the long tail of science<br> | ||
Line 104: | Line 104: | ||
| style="overflow:hidden;padding:2px 3px 2px 3px;vertical-align:bottom;" bgcolor="#ccffff" | DIRAC4EGI | | style="overflow:hidden;padding:2px 3px 2px 3px;vertical-align:bottom;" bgcolor="#ccffff" | DIRAC4EGI | ||
| style="overflow:hidden;padding:2px 3px 2px 3px;vertical-align:bottom;" | Andrei Tsaregorodtsev | | style="overflow:hidden;padding:2px 3px 2px 3px;vertical-align:bottom;" | Andrei Tsaregorodtsev | ||
| style="overflow:hidden;padding:2px 3px 2px 3px;vertical-align:bottom;" bgcolor="#66ff00" | YES | | style="overflow:hidden;padding:2px 3px 2px 3px;vertical-align:bottom;" bgcolor="#66ff00" | YES | ||
| style="overflow:hidden;padding:2px 3px 2px 3px;vertical-align:bottom;" | The DIRAC software is dual stack already<br> and supports IPv4/v6 client server communications. However, the hosting infrastructure at<br> CYFRONET where the DIRAC4EGI servers are running is still IPv4 and not IPv6 ready according<br> to the local administrators. I do not have time estimations from them about the IPv6 enabling.<br> | | style="overflow:hidden;padding:2px 3px 2px 3px;vertical-align:bottom;" | The DIRAC software is dual stack already<br> and supports IPv4/v6 client server communications. However, the hosting infrastructure at<br> CYFRONET where the DIRAC4EGI servers are running is still IPv4 and not IPv6 ready according<br> to the local administrators. I do not have time estimations from them about the IPv6 enabling.<br> | ||
|- style="height:21px;" | |- style="height:21px;" |
Revision as of 14:54, 31 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 | ||
FTS | YES | ||
BDII | YES | ||
LFC | YES | ||
VOMS-SERVER | YES | ||
UI | YES | ||
StoRM | YES |
||
frontier-squid-3 | YES | ||
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