Difference between revisions of "IPV6 Assessment"

Revision as of 12:08, 27 October 2017

Core/EGI services

Core/EGI service	Contact point	IPv6 readiness	Comments
Accounting repositories and portal	Adrian Coveney	PARTIAL	Portal is OK, no direct route to Repository but updates to SSM required to support IPv6.
Activities and services for the long tail of science	Stéphane Gérard	UNKNOWN	hosted by CYFRONET, check CYFRONET
Application DB	Kostas Koumantaros	UNKNOWN
Collaboration tools	Martin Kuba	YES	full support
E-GRANT services hosting and technical operations	Tomasz Szepieniec	YES
Helpdesk (GGUS)	Guenter Grein	PARTIAL	For production instances IPv6 configuration is scheduled for the GGUS release on July, 26th 2017.
Helpdesk human support	Zdeněk Šustr	YES	human support, no need to assess readiness
Message brokers	Christos Kanellopoulos	YES
Monitoring services	Christos Kanellopoulos	PARTIAL	The EGI Catch All CA CRL is served only via IPv4 at the moment, but this will be fixed soon
Operations Portal	Cyril L’Orphelin	PARTIAL	planning to virtualize and replace a part of the web cluster (the only non-IPv6 compliant part) next year (2nd semester)
Security coordination and security tools	David Kelsey	UNKNOWN
Service registry (GOCDB)	George Ryall	PARTIAL	IPv6 ready, STFC not ready
Services for AAI	Christos Kanellopoulos	UNKNOWN
UMD quality assurance	Jorge Gomes	NO	IFCA/LIP no plans, CESGA partial
UMD software provisioning infrastructure	Kostas Koumantaros	UNKNOWN
CheckIn	Christos Kanellopoulos	UNKNOWN
CSGF	Roberto Barbera	UNKNOWN
CVMFS Stratum-0	Catalin Condurache	PARTIAL	IPv6 ready, STFC not ready
DIRAC4EGI	Andrei Tsaregorodtsev	UNKNOWN
EC3	Miguel Caballer	YES
Perun	Michal Prochazka	YES
User registration portal	Roksana Dobrzańska	UNKNOWN
WS-PGRADE	Zoltán Farkas	YES	No tests so far, but should be ready.

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

IPv6 infrastructure readiness
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
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/

Difference between revisions of "IPV6 Assessment"

Revision as of 12:08, 27 October 2017

Contents

Core/EGI services

UMD

CMD and FedCloud product readiness

Infrastructure status and plans

WLCG plans

References

Navigation menu

@@ Line 232: / Line 232: @@
 == Infrastructure status and plans<br>  ==
-{| height="1203" width="1089" cellspacing="1" cellpadding="1" border="1"
+{| width="1089" border="1" cellspacing="1" cellpadding="1"
 |+ IPv6 infrastructure readiness
 |-
 | '''NGI'''<br>
+| '''Status and plans'''
 | '''Total sites'''<br>
 | '''Sites implementing IPv6'''<br>
@@ Line 244: / Line 245: @@
 |-
 | AsiaPacific<br>
+|
 | <br>
 | <br>
@@ Line 252: / Line 254: @@
 |-
 | CERN<br>
+|
 | <br>
 | <br>
@@ Line 260: / Line 263: @@
 |-
 | NGI_AEGIS<br>
+|
 | <br>
 | <br>
@@ Line 268: / Line 272: @@
 |-
 | NGI_ARMGRID<br>
+|
 | <br>
 | <br>
@@ Line 276: / Line 281: @@
 |-
 | NGI_BG<br>
+|
 | <br>
 | <br>
@@ Line 284: / Line 290: @@
 |-
 | NGI_BY<br>
+|
 | <br>
 | <br>
@@ Line 292: / Line 299: @@
 |-
 | NGI_CH<br>
+|
 | <br>
 | <br>
@@ Line 300: / Line 308: @@
 |-
 | NGI_CZ<br>
+|
 | <br>
 | <br>
@@ Line 308: / Line 317: @@
 |-
 | NGI_DE<br>
+|
 | <br>
 | <br>
@@ Line 316: / Line 326: @@
 |-
 | NGI_FI<br>
+|
 | <br>
 | <br>
@@ Line 324: / Line 335: @@
 |-
 | NGI_FRANCE<br>
+|
 | <br>
 | <br>
@@ Line 332: / Line 344: @@
 |-
 | NGI_GE<br>
+|
 | <br>
 | <br>
@@ Line 340: / Line 353: @@
 |-
 | NGI_GRNET<br>
+|
 | <br>
 | <br>
@@ Line 348: / Line 362: @@
 |-
 | NGI_HR<br>
+|
 | <br>
 | <br>
@@ Line 356: / Line 371: @@
 |-
 | NGI_HU<br>
+|
 | <br>
 | <br>
@@ Line 364: / Line 380: @@
 |-
 | NGI_IBERGRID<br>
+|
 | <br>
 | <br>
@@ Line 372: / Line 389: @@
 |-
 | NGI_IL<br>
+|
 | <br>
 | <br>
@@ Line 380: / Line 398: @@
 |-
 | NGI_IT<br>
+|
 | <br>
 | <br>
@@ Line 388: / Line 407: @@
 |-
 | NGI_MARGI<br>
+|
 | <br>
 | <br>
@@ Line 396: / Line 416: @@
 |-
 | NGI_MD<br>
+|
 | <br>
 | <br>
@@ Line 404: / Line 425: @@
 |-
 | NGI_ME<br>
-| <br>
+| bgcolor="#ff0000" | WON'T_DO
-| <br>
+| 1<br>
-| <br>
+| 0<br>
+| NO<br>
 | <br>
 | <br>
@@ Line 412: / Line 434: @@
 |-
 | NGI_NDGF<br>
+|
 | <br>
 | <br>
@@ Line 420: / Line 443: @@
 |-
 | NGI_NL<br>
+|
 | <br>
 | <br>
@@ Line 428: / Line 452: @@
 |-
 | NGI_PL<br>
+|
 | <br>
 | <br>
@@ Line 436: / Line 461: @@
 |-
 | NGI_RO<br>
+|
 | <br>
 | <br>
@@ Line 444: / Line 470: @@
 |-
 | NGI_SI<br>
+|
 | <br>
 | <br>
@@ Line 452: / Line 479: @@
 |-
 | NGI_SK<br>
+|
 | <br>
 | <br>
@@ Line 460: / Line 488: @@
 |-
 | NGI_TR<br>
+|
 | <br>
 | <br>
@@ Line 468: / Line 497: @@
 |-
 | NGI_UA<br>
+|
 | <br>
 | <br>
@@ Line 476: / Line 506: @@
 |-
 | NGI_UK<br>
+|
 | <br>
 | <br>
@@ Line 484: / Line 515: @@
 |-
 | ROC_Canada<br>
+|
 | <br>
 | <br>
@@ Line 492: / Line 524: @@
 |-
 | ROC_LA<br>
+|
 | <br>
 | <br>
@@ Line 500: / Line 533: @@
 |-
 | Russia<br>
+|
 | <br>
 | <br>
@@ Line 508: / Line 542: @@
 |-
 | IDGF<br>
+|
 | <br>
 | <br>
@@ Line 516: / Line 551: @@
 |-
 | NGI_CHINA<br>
+|
 | <br>
 | <br>

Difference between revisions of "IPV6 Assessment"

Revision as of 12:08, 27 October 2017

Core/EGI services

UMD

CMD and FedCloud product readiness

Infrastructure status and plans

WLCG plans

References

Navigation menu

Search