Difference between revisions of "IPV6 Assessment"
Line 223: | Line 223: | ||
|- | |- | ||
| AsiaPacific<br> | | AsiaPacific<br> | ||
| <br> | | <br> | ||
| <br> | | <br> | ||
| <br> | | <br> | ||
Line 232: | Line 232: | ||
|- | |- | ||
| CERN<br> | | CERN<br> | ||
| <br> | | <br> | ||
| <br> | | <br> | ||
| <br> | | <br> | ||
Line 241: | Line 241: | ||
|- | |- | ||
| NGI_AEGIS<br> | | NGI_AEGIS<br> | ||
| <br> | | <br> | ||
| <br> | | <br> | ||
| <br> | | <br> | ||
Line 250: | Line 250: | ||
|- | |- | ||
| NGI_ARMGRID<br> | | NGI_ARMGRID<br> | ||
| <br> | | <br> | ||
| <br> | | <br> | ||
| <br> | | <br> | ||
Line 259: | Line 259: | ||
|- | |- | ||
| NGI_BG<br> | | NGI_BG<br> | ||
| <br> | | <br> | ||
| <br> | | <br> | ||
| <br> | | <br> | ||
Line 268: | Line 268: | ||
|- | |- | ||
| NGI_BY<br> | | NGI_BY<br> | ||
| <br> | | <br> | ||
| <br> | | <br> | ||
| <br> | | <br> | ||
Line 277: | Line 277: | ||
|- | |- | ||
| NGI_CH<br> | | NGI_CH<br> | ||
| <br> | | <br> | ||
| <br> | | <br> | ||
| <br> | | <br> | ||
Line 286: | Line 286: | ||
|- | |- | ||
| NGI_CZ<br> | | NGI_CZ<br> | ||
| <br> | | <br> | ||
| <br> | | <br> | ||
| <br> | | <br> | ||
Line 295: | Line 295: | ||
|- | |- | ||
| NGI_DE<br> | | NGI_DE<br> | ||
| <br> | | <br> | ||
| <br> | | <br> | ||
| <br> | | <br> | ||
Line 304: | Line 304: | ||
|- | |- | ||
| NGI_FI<br> | | NGI_FI<br> | ||
| <br> | | <br> | ||
| <br> | | <br> | ||
| <br> | | <br> | ||
Line 313: | Line 313: | ||
|- | |- | ||
| NGI_FRANCE<br> | | NGI_FRANCE<br> | ||
| <br> | | <br> | ||
| <br> | | <br> | ||
| <br> | | <br> | ||
Line 322: | Line 322: | ||
|- | |- | ||
| NGI_GE<br> | | NGI_GE<br> | ||
| <br> | | <br> | ||
| <br> | | <br> | ||
| <br> | | <br> | ||
Line 331: | Line 331: | ||
|- | |- | ||
| NGI_GRNET<br> | | NGI_GRNET<br> | ||
| <br> | | <br> | ||
| <br> | | <br> | ||
| <br> | | <br> | ||
Line 340: | Line 340: | ||
|- | |- | ||
| NGI_HR<br> | | NGI_HR<br> | ||
| <br> | | <br> | ||
| <br> | | <br> | ||
| <br> | | <br> | ||
Line 349: | Line 349: | ||
|- | |- | ||
| NGI_HU<br> | | NGI_HU<br> | ||
| <br> | | <br> | ||
| <br> | | <br> | ||
| <br> | | <br> | ||
Line 358: | Line 358: | ||
|- | |- | ||
| NGI_IBERGRID<br> | | NGI_IBERGRID<br> | ||
| <br> | | <br> | ||
| <br> | | <br> | ||
| <br> | | <br> | ||
Line 367: | Line 367: | ||
|- | |- | ||
| NGI_IL<br> | | NGI_IL<br> | ||
| <br> | | <br> | ||
| <br> | | <br> | ||
| <br> | | <br> | ||
Line 376: | Line 376: | ||
|- | |- | ||
| NGI_IT<br> | | NGI_IT<br> | ||
| <br> | | <br> | ||
| <br> | | <br> | ||
| <br> | | <br> | ||
Line 385: | Line 385: | ||
|- | |- | ||
| NGI_MARGI<br> | | NGI_MARGI<br> | ||
| <br> | | <br> | ||
| <br> | | <br> | ||
| <br> | | <br> | ||
Line 394: | Line 394: | ||
|- | |- | ||
| NGI_MD<br> | | NGI_MD<br> | ||
| <br> | | <br> | ||
| <br> | | <br> | ||
| <br> | | <br> | ||
Line 412: | Line 412: | ||
|- | |- | ||
| NGI_NDGF<br> | | NGI_NDGF<br> | ||
| <br> | | <br> | ||
| <br> | | <br> | ||
| <br> | | <br> | ||
Line 421: | Line 421: | ||
|- | |- | ||
| NGI_NL<br> | | NGI_NL<br> | ||
| | | bgcolor="#66ff00" | WILL_DO | ||
| <br> | | 3<br> | ||
| <br> | | 3<br> | ||
| <br> | | 3<br> | ||
| <br> | | NO<br> | ||
| <br> | | NO<br> | ||
| | | | ||
If you, and another NGI or site, are offering capabilities and services that are not yet v6 enabled and offer status web content, please '''consider fronting it with e.g. CloudFlare's free offering to gain such v6''' capability at no cost to you and for the benefit of all | |||
Security training is in general always good, but - just if case they did not get it - for IPv6 a pointer to the proper guidance RFCs on v6 security should be good. The HEPiX v6 WG also has relevant materials in this area that can be re-used. | |||
|- | |- | ||
| NGI_PL<br> | | NGI_PL<br> | ||
| <br> | | <br> | ||
| <br> | | <br> | ||
| <br> | | <br> | ||
Line 439: | Line 443: | ||
|- | |- | ||
| NGI_RO<br> | | NGI_RO<br> | ||
| <br> | | <br> | ||
| <br> | | <br> | ||
| <br> | | <br> | ||
Line 448: | Line 452: | ||
|- | |- | ||
| NGI_SI<br> | | NGI_SI<br> | ||
| <br> | | <br> | ||
| <br> | | <br> | ||
| <br> | | <br> | ||
Line 457: | Line 461: | ||
|- | |- | ||
| NGI_SK<br> | | NGI_SK<br> | ||
| <br> | | <br> | ||
| <br> | | <br> | ||
| <br> | | <br> | ||
Line 475: | Line 479: | ||
|- | |- | ||
| NGI_UA<br> | | NGI_UA<br> | ||
| <br> | | <br> | ||
| <br> | | <br> | ||
| <br> | | <br> | ||
Line 484: | Line 488: | ||
|- | |- | ||
| NGI_UK<br> | | NGI_UK<br> | ||
| <br> | | <br> | ||
| <br> | | <br> | ||
| <br> | | <br> | ||
Line 493: | Line 497: | ||
|- | |- | ||
| ROC_Canada<br> | | ROC_Canada<br> | ||
| bgcolor="#66ff00" | WILL_DO<br> | | bgcolor="#66ff00" | WILL_DO<br> | ||
| 4<br> | | 4<br> | ||
| 4<br> | | 4<br> | ||
Line 502: | Line 506: | ||
|- | |- | ||
| ROC_LA<br> | | ROC_LA<br> | ||
| <br> | | <br> | ||
| <br> | | <br> | ||
| <br> | | <br> | ||
Line 511: | Line 515: | ||
|- | |- | ||
| Russia<br> | | Russia<br> | ||
| <br> | | <br> | ||
| <br> | | <br> | ||
| <br> | | <br> | ||
Line 520: | Line 524: | ||
|- | |- | ||
| IDGF<br> | | IDGF<br> | ||
| <br> | | <br> | ||
| <br> | | <br> | ||
| <br> | | <br> | ||
Line 529: | Line 533: | ||
|- | |- | ||
| NGI_CHINA<br> | | NGI_CHINA<br> | ||
| <br> | | <br> | ||
| <br> | | <br> | ||
| <br> | | <br> |
Revision as of 09:48, 2 November 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 |
WILL_DO | 3 |
3 |
3 |
NO |
NO |
If you, and another NGI or site, are offering capabilities and services that are not yet v6 enabled and offer status web content, please consider fronting it with e.g. CloudFlare's free offering to gain such v6 capability at no cost to you and for the benefit of all Security training is in general always good, but - just if case they did not get it - for IPv6 a pointer to the proper guidance RFCs on v6 security should be good. The HEPiX v6 WG also has relevant materials in this area that can be re-used. |
NGI_PL |
|||||||
NGI_RO |
|||||||
NGI_SI |
|||||||
NGI_SK |
|||||||
NGI_TR |
WILL_DO | 3 |
3 |
YES |
YES |
YES |
|
NGI_UA |
|||||||
NGI_UK |
|||||||
ROC_Canada |
WILL_DO |
4 |
4 |
YES |
YES |
YES |
Four sites: one site has storage testbed with IPv6 enabled and plan to put all production storage services on IPv6 (dual stack) before April 2018. Another 3 sites plan to implement dual stack in 1~2 years. |
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