Difference between revisions of "IPV6 Assessment"
Jump to navigation
Jump to search
Infrastructure status and plans
Line 230: | Line 230: | ||
== CMD and FedCloud product readiness == | == CMD and FedCloud product readiness == | ||
== Infrastructure status and plans<br> == | == Infrastructure status and plans<br> == | ||
{| width="200" cellspacing="1" cellpadding="1" border="1" | {| width="200" cellspacing="1" cellpadding="1" border="1" | ||
Line 243: | Line 243: | ||
| '''Comments'''<br> | | '''Comments'''<br> | ||
|- | |- | ||
| <br> | | AsiaPacific<br> | ||
| <br> | | <br> | ||
| <br> | | <br> | ||
Line 251: | Line 251: | ||
| <br> | | <br> | ||
|- | |- | ||
| <br> | | CERN<br> | ||
| <br> | | <br> | ||
| <br> | | <br> | ||
Line 259: | Line 259: | ||
| <br> | | <br> | ||
|- | |- | ||
| <br> | | NGI_AEGIS<br> | ||
| <br> | | <br> | ||
| <br> | | <br> | ||
Line 267: | Line 267: | ||
| <br> | | <br> | ||
|- | |- | ||
| <br> | | NGI_ARMGRID<br> | ||
| <br> | | <br> | ||
| <br> | | <br> | ||
Line 275: | Line 275: | ||
| <br> | | <br> | ||
|- | |- | ||
| <br> | | NGI_BG<br> | ||
| <br> | | <br> | ||
| <br> | | <br> | ||
Line 283: | Line 283: | ||
| <br> | | <br> | ||
|- | |- | ||
| <br> | | NGI_BY<br> | ||
| <br> | | <br> | ||
| <br> | | <br> | ||
Line 291: | Line 291: | ||
| <br> | | <br> | ||
|- | |- | ||
| <br> | | NGI_CH<br> | ||
| <br> | | <br> | ||
| <br> | | <br> | ||
Line 299: | Line 299: | ||
| <br> | | <br> | ||
|- | |- | ||
| <br> | | NGI_CZ<br> | ||
| <br> | | <br> | ||
| <br> | | <br> | ||
Line 307: | Line 307: | ||
| <br> | | <br> | ||
|- | |- | ||
| <br> | | NGI_DE<br> | ||
| <br> | | <br> | ||
| <br> | | <br> | ||
Line 315: | Line 315: | ||
| <br> | | <br> | ||
|- | |- | ||
| <br> | | NGI_FI<br> | ||
| <br> | | <br> | ||
| <br> | | <br> | ||
Line 323: | Line 323: | ||
| <br> | | <br> | ||
|- | |- | ||
| <br> | | NGI_FRANCE<br> | ||
| <br> | | <br> | ||
| <br> | | <br> | ||
Line 331: | Line 331: | ||
| <br> | | <br> | ||
|- | |- | ||
| <br> | | NGI_GE<br> | ||
| <br> | | <br> | ||
| <br> | | <br> | ||
Line 339: | Line 339: | ||
| <br> | | <br> | ||
|- | |- | ||
| <br> | | NGI_GRNET<br> | ||
| <br> | | <br> | ||
| <br> | | <br> | ||
Line 347: | Line 347: | ||
| <br> | | <br> | ||
|- | |- | ||
| <br> | | NGI_HR<br> | ||
| <br> | | <br> | ||
| <br> | | <br> | ||
Line 355: | Line 355: | ||
| <br> | | <br> | ||
|- | |- | ||
| <br> | | NGI_HU<br> | ||
| <br> | | <br> | ||
| <br> | | <br> | ||
Line 363: | Line 363: | ||
| <br> | | <br> | ||
|- | |- | ||
| <br> | | NGI_IBERGRID<br> | ||
| <br> | | <br> | ||
| <br> | | <br> | ||
Line 371: | Line 371: | ||
| <br> | | <br> | ||
|- | |- | ||
| <br> | | NGI_IL<br> | ||
| <br> | | <br> | ||
| <br> | | <br> | ||
Line 379: | Line 379: | ||
| <br> | | <br> | ||
|- | |- | ||
| <br> | | NGI_IT<br> | ||
| <br> | | <br> | ||
| <br> | | <br> | ||
Line 387: | Line 387: | ||
| <br> | | <br> | ||
|- | |- | ||
| <br> | | NGI_MARGI<br> | ||
| <br> | | <br> | ||
| <br> | | <br> | ||
Line 395: | Line 395: | ||
| <br> | | <br> | ||
|- | |- | ||
| <br> | | NGI_MD<br> | ||
| <br> | | <br> | ||
| <br> | | <br> | ||
Line 403: | Line 403: | ||
| <br> | | <br> | ||
|- | |- | ||
| <br> | | NGI_ME<br> | ||
| <br> | | <br> | ||
| <br> | | <br> | ||
Line 411: | Line 411: | ||
| <br> | | <br> | ||
|- | |- | ||
| <br> | | NGI_NDGF<br> | ||
| <br> | | <br> | ||
| <br> | | <br> | ||
Line 419: | Line 419: | ||
| <br> | | <br> | ||
|- | |- | ||
| <br> | | NGI_NL<br> | ||
| <br> | | <br> | ||
| <br> | | <br> | ||
Line 427: | Line 427: | ||
| <br> | | <br> | ||
|- | |- | ||
| <br> | | NGI_PL<br> | ||
| <br> | | <br> | ||
| <br> | | <br> | ||
Line 435: | Line 435: | ||
| <br> | | <br> | ||
|- | |- | ||
| <br> | | NGI_RO<br> | ||
| <br> | | <br> | ||
| <br> | | <br> | ||
Line 443: | Line 443: | ||
| <br> | | <br> | ||
|- | |- | ||
| <br> | | NGI_SI<br> | ||
| <br> | | <br> | ||
| <br> | | <br> | ||
Line 451: | Line 451: | ||
| <br> | | <br> | ||
|- | |- | ||
| <br> | | NGI_SK<br> | ||
| <br> | | <br> | ||
| <br> | | <br> | ||
Line 459: | Line 459: | ||
| <br> | | <br> | ||
|- | |- | ||
| <br> | | NGI_TR<br> | ||
| <br> | | <br> | ||
| <br> | | <br> | ||
Line 467: | Line 467: | ||
| <br> | | <br> | ||
|- | |- | ||
| <br> | | NGI_UA<br> | ||
| <br> | | <br> | ||
| <br> | | <br> | ||
Line 475: | Line 475: | ||
| <br> | | <br> | ||
|- | |- | ||
| <br> | | NGI_UK<br> | ||
| <br> | | <br> | ||
| <br> | | <br> | ||
Line 483: | Line 483: | ||
| <br> | | <br> | ||
|- | |- | ||
| <br> | | ROC_Canada<br> | ||
| <br> | | <br> | ||
| <br> | | <br> | ||
Line 491: | Line 491: | ||
| <br> | | <br> | ||
|- | |- | ||
| <br> | | ROC_LA<br> | ||
| <br> | | <br> | ||
| <br> | | <br> | ||
Line 499: | Line 499: | ||
| <br> | | <br> | ||
|- | |- | ||
| <br> | | Russia<br> | ||
| <br> | | <br> | ||
| <br> | | <br> | ||
Line 507: | Line 507: | ||
| <br> | | <br> | ||
|- | |- | ||
| | | IDGF<br> | ||
| <br> | | <br> | ||
| <br> | | <br> | ||
Line 523: | Line 515: | ||
| <br> | | <br> | ||
|- | |- | ||
| <br> | | NGI_CHINA<br> | ||
| <br> | | <br> | ||
| <br> | | <br> |
Revision as of 12:06, 25 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 | 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. |
CMD and FedCloud product readiness
Infrastructure status and plans
NGI |
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 |
||||||
NGI_GRNET |
||||||
NGI_HR |
||||||
NGI_HU |
||||||
NGI_IBERGRID |
||||||
NGI_IL |
||||||
NGI_IT |
||||||
NGI_MARGI |
||||||
NGI_MD |
||||||
NGI_ME |
||||||
NGI_NDGF |
||||||
NGI_NL |
||||||
NGI_PL |
||||||
NGI_RO |
||||||
NGI_SI |
||||||
NGI_SK |
||||||
NGI_TR |
||||||
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/