Alert.png The wiki is deprecated and due to be decommissioned by the end of September 2022.
The content is being migrated to other supports, new updates will be ignored and lost.
If needed you can get in touch with EGI SDIS team using operations @ egi.eu.

Difference between revisions of "IPV6 Assessment"

From EGIWiki
Jump to navigation Jump to search
m
m
Line 64: Line 64:
|- style="height:21px;"
|- style="height:21px;"
| style="overflow:hidden;padding:2px 3px 2px 3px;vertical-align:bottom;font-family:Arial;font-weight:normal;color:#000000;" bgcolor="#ffccff" | Service registry (GOCDB)  
| style="overflow:hidden;padding:2px 3px 2px 3px;vertical-align:bottom;font-family:Arial;font-weight:normal;color:#000000;" bgcolor="#ffccff" | Service registry (GOCDB)  
| style="overflow:hidden;padding:2px 3px 2px 3px;vertical-align:bottom;" | David Meredith
| style="overflow:hidden;padding:2px 3px 2px 3px;vertical-align:bottom;" | George Ryall
| 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;" | IPv6 ready, STFC not ready
| style="overflow:hidden;padding:2px 3px 2px 3px;vertical-align:bottom;" | IPv6 ready, STFC not ready

Revision as of 16:50, 24 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 UNKNOWN
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

NGIs/RCs/RPs plans

WLCG plans

References