IPv6 WLCG Site Survey
From GridPP Wiki
Revision as of 00:42, 25 July 2017 by Chun-Yu Lin 479225 adaad9bc79 (Talk | contribs)
IPv6 WLCG Site Survey
This questionnaire is aimed at all WLCG Sites. Please add a row for your site to the end of the table below answering the questions. This information can be modified later if/when the situation changes (please change the date field at the same time).
Metadata
- Site name in standard form
- Date in ISO 8601 notation to allow easy sorting
Questions:
- Is your site already offering connectivity, routing and naming services for IPv6 end systems (i.e. is your site already connected to the worldwide IPv6 network and ready to support IPv6 end systems)?
- If so, have you already enabled IPv6 on some of the services you manage? Please provide details on which services are enabled
- If your site is not yet IPv6-ready, are there plans for this? If so, what are the timelines?
- Does your site currently have problems with allocating a sufficient number of IPv4 addresses? Or foreseen in the near future?
- Are there other issues you are aware of? Or interesting work going on in this area?
- Any other comments?
Answers by Site
| Site Name | Date when entered | IPv6 connectivity | IPv6 enabled services | ETA for IPv6 readiness | IPv4 exhaustion issues | Other issues and related work | Comments | |
|---|---|---|---|---|---|---|---|---|
| NDGF | 2014-05-12 | Yes, but not to all of site | For limited services, not main storage yet | About one year | No. Storage has plenty, a lot of worker nodes use private networks | 3 out of 8 subsites are fully IPv6 connected, the rest are partially or IPv4 only | ||
| NERSC | 2014-05-29 | Yes. | Some services yes but not all | Some partially ready now (web, dns), the rest is scheduled for Q215 | No | |||
| praguelcg2 | 2014-05-14 | Yes. | Many services yes but not all | Partially ready now, the rest depends on service providers | Yes | |||
| UKI-LT2-IC-HEP | 2017-07-18 | Yes | Most services enabled | Ready now | No | |||
| UKI-LT2-QMUL | 2014-05-14 | Yes | Perfsonar, RIPE Atlas probe, test SE | Waiting for confidence that middleware won't break | No. Worker nodes behind NAT. Sufficient IPv4 for world facing services (and University sees no risk of running out in the immediate future). | |||
| UKI-LT2-UCL-HEP | 2014-05-14 | No | No | Waiting for central IT to announce service, and middleware to be thoroughly tested | No immediate shortage | Central IT network division has set up IPv6 working group. I'm not up to date with their plans. | ||
| UKI-LT2-RHUL | 2017-07-18 | No | No | Network people got IPv6 allocation from Janet | No immediate shortage | We plan to deploy perfsonar box before upgrade middleware | ||
| UKI-LT2-Brunel | 2017-07-18 | Yes | All services enabled. | Ready now. | No | |||
| UKI-SOUTHGRID-CAM-HEP | 2014-05-14 | No | No | Service available from central IT, IPv6 addresses allocated. | No immediate shortage | Central IT enthusiastic about IPv6 deployment. Lack of manpower at site | ||
| UKI-NORTHGRID-LANCS-HEP | 2014-06-05 | To the institution, not the site. | None. | Early 2015, hope to have some IPv6 services by Q3 2014 | We have enough for the next few years. | Lack of manpower combined with little urgency makes IPv6 a low priority for our network admins, but they're engaging - it could be that we'll be their test case. | ||
| UKI-NORTHGRID-LIV-HEP | 2014-05-14 | We have new routers with IPv6 address that can ping IPv6 internet | Not yet | Planning in progress | No immediate shortage | Dedicating resource to core network with IPv6. | Network team looks forward to offering IPv6 in the future. | |
| UKI-NORTHGRID-SHEF-HEP | 2014-05-28 | No | Not yet | Planning in progress | No immediate shortage | |||
| FNAL | 2014-05-14 | Yes, but limited | web, email and services on IPv6 test network | TBD | No IPv4 exhaustion issues (yet) | IPv6 and 100 Gb/s test networks are being combined | ||
| UKI-SCOTGRID-DURHAM | 2014-05-15 | No | No | No allocations have been finalised by Central IT | None | |||
| UKI-SCOTGRID-GLASGOW | 2014-06-04 | Yes (test cluster) | Yes (test cluster) | Awaiting production IPv6 DNS on campus | None | |||
| DE-KIT (GridKa) | 2014-05-15 | Yes, but still in the process of rolling out | DNS, WEB,..., several projects are already deploying IPv6, Wirelss/WiFi is IPv6 enabled, number 43 at a top 242 list http://www.worldipv6launch.org/measurements/ |
IPv6 are arranged for a project an demand, general readyness available in approx. 1 to 2 years | No IPv4 exhaustion forseable (at least not yet) | |||
| UKI-SOUTHGRID-OX-HEP | 2014-05-16 | Yes, but on a limited 'test' basis | Dual stack site BDII, UI, and test CE, IPv6-only test DPM SE | A University network upgrade is planned for late 2014, which should enable IPv6 as a normal production quality service | The grid site has a /24 which is currently adequate, but with relatively little spare, and little to no prospect of getting more IPv4 space | The main University routers cannot handle IPv6 in hardware so it is handled by dedicated (slow) boxes to avoid CPU load on the main ones. This limits the site's IPv6 bandwidth to <1Gbit/s | ||
| UKI-SOUTHGRID-SUSX | 2014-05-28 | no | no | no plans as yet, still to be discussed with university IT services | The university has a /16 so no problems for IPv4 addresses | |||
| RAL Tier1 | 2014-06-06 | Yes, on a limited test basis | - | A testbed creation has just kicked off. | No problems with IPv4 | |||
| TRIUMF Tier1 | 2014-05-28 | No | None | Not yet determined | No immediate shortage | |||
| BITP | 2014-05-21 | Yes, fully supported and deployed. | All machines are dual stack enabled and published in DNS. No particular configuration was done on the standard services to enable IPv6 support but will work on this next. | Already done. | No | Working in a test cluster to enable IPv6-only for ARC. | ||
| FR-CCIN2P3 | 2014-05-22 | Yes, but on limited test basis. | DNS and limited test machines. | TBD | No immediate shortage | |||
| FR-IN2P3-SUBATECH | 2014-05-28 | No | None | No immediate shortage | Will follow FR plans as conducted by CCIN2P3 | |||
| CH-CERN | 2014-05-26 | Yes: Campus, Datacentre, Firewall are dual stack. | DNS, mail reading, lxplus | Network is ready. No defined date for other IT services. | CERN Public IPv4 addresses will run out in 2015 | |||
| FR-IN2P3-CPPM | 2014-05-28 | NO | None | Not yet determined | No immediate shortage | |||
| T2_FI_HIP | 2014-05-28 | Yes. | httpd, sshd, bdii, CMS xrootd federator and perfsonar. New machines have IPv6 by default but not all services listen on IPv6. | Waiting for confidence that middleware won't break | ||||
| DESY-ZN | 2014-05-28 | NO | None | Not planned, yet | No | |||
| WUPPERTALPROD | 2014-05-28 | No | None | No allocations have been finalised by Central network services | None | |||
| UNI-FREIBURG | 2014-07-04 | No, only single nodes of Central network services. | None, disabled on purpose | Not planned at all, no need | None | Using private network when applicable
| ||
| SIGNET | 2014-05-28 | Yes | Many services enabled, but not all | All the machines have IPv6 addresses, but DNS is not yet populated | No | |||
| T2_Estonia | 2014-05-28 | Doable | none, even disabled on purpose on most | Not planned at all, no need | None, plenty of IPs for years to come | |||
| UKI-SOUTHGRID-BHAM-HEP | 2014-05-28 | No | None | University is (in theory) going to roll out IPv6 with the network upgrade in the next 6-12 months | No immediate shortage | |||
| UKI-SOUTHGRID-BRIS-HEP | 2017-07-19 | Yes but not to all of site | CE+SE(+IO/GridFTP server) | Already for some services | No | Dire lack of staff resources | Dire lack of staff resources | |
| EFDA-JET | 2014-05-28 | NO | None | Not planned, yet | No | |||
| INFN-CNAF-T1 | 2014-05-28 | NO | None | Planned for this year with the first services (Numbering plan is already done) | No | |||
| INFN-LNL-2 | 2014-06-03 | No | None | Not yet determined | No immediate shortage | |||
| INFN-LNL-2 | 2014-06-03 | No | None | Not yet determined | No immediate shortage | |||
| INFN-ROMA1 | 2014-07-07 | No | None | Not yet determined | No | |||
| INFN-ROMA1-CMS | 2014-07-02 | No | None | Not yet determined | No | |||
| INFN-MILANO-ATLASC | 2014-07-04 | Public IPv6 is available on the Tier2 LAN but still routed via the main INFN site network pending a Tier2 router upgrade. | Just DNS so far. | Plan to enable IPv6 routing via the Tier2 uplink by September 2014. | No | |||
| INFN-TORINO | 2014-06-16 | No | None | Not yet determined | No | |||
| INFN-NAPOLI-ATLAS | 2014-06-05 | No | None | Not yet determined | No | |||
| CSCS-LCG2 | 2014-05-28 | Yes | None | Constrained by middleware currently running dCache 2.6. Unsure of support in other services such as Cream and ARC. Thorough testing required. | No | No objections to deploying IPv6 but software needs testing in real world scenarios, not willing to run releases that are testing/ not supported long term in production.
| ||
| JINR-LCG2 | 2017-07-18 | NO | NO | Planned for this year | No immediate shortage |
| ||
| JINR-T1 | 2017-07-18 | YES | Dual stack SEs, WNs, Phedexes | Done | No immediate shortage | IPv6 PMTUD black hole difficult to debug | ||
| FR-IN2P3-IPHC | 2014-06-05 | No | None | First IPv6 services (Perfsonar) should be available in Fall 2017. | No immediate shortage | Last update: 2017-07-21 | ||
| FR-IN2P3-LPC | 2014-05-28 | No | None | Not yet determined | No immediate shortage | |||
| FR-IN2P3-LPSC | 2014-05-28 | No | None | Not yet determined | No immediate shortage | |||
| FR-IN2P3-LAPP | 2014-05-28 | No | None | Not yet determined | No immediate shortage | |||
| WEIZMANN-LCG2 | 2014-05-28 | No | None | Not yet determined | No immediate shortage | |||
| TECHNION-HEP | 2014-06-06 | No | None | Not yet determined | No immediate shortage | |||
| IL-TAU-HEP | 2014-06-06 | No | None | Not yet determined | No immediate shortage | |||
| T2_HU_Budapest | 2014-05-28 | Yes | None | Ready | None in the next few years | |||
| Hephy-Vienna | 2014-05-28 | No | None | Not yet determined | No immediate shortage | |||
| CYFRONET-LCG2 | 2014-05-26 | Yes | DNS | Network is ready. No defined date for other IT services. | No immediate shortage | |||
| T2_US_Nebraska | 2015-03-24 | Yes | All Tier2 hosts are dual stack, exceptions are squid and bestman servers which have no AAAA records until the OSG releases used supports IPv6. Opportunistic resources at Nebraska are still IPv4 only. | Ready | No immediate shortage | None | ||
| UCSD CMS T2 | 2014-05-28 | Yes | DNS, Some test systems fully IPv6 Enabled, rolling out more IPv6 in coming weeks. | Network is ready. No defined date for other IT services. | No immediate shortage | |||
| SAMPA-Sao Paulo | 2014-05-28 | No | None | Not yet determined | No immediate shortage | |||
| Florida CMS T2 | 2014-05-28 | No | None so far. | Discussion on-going with the target date, the end of 2014 | Public name for IPv4 with worker nodes | |||
| SFU-LCG2 T2 | 2014-05-28 | No | None | Not yet determined | No immediate shortage | |||
| CA-VICTORIA-WESTGRID-T2 | 2014-05-28 | No | None | Not yet determined | No immediate shortage | Would need to investigate host and switch configuration | Would need to wait until software is fully tested and ready | |
| CA-SCINET-T2 | 2014-06-06 | Campus is testing this now | None for T2 yet | Not yet determined - 6 months? | No immediate shortage | |||
| AUSTRALIA-ATLAS | 2014-05-29 | No | None | Not yet determined | No immediate shortage | Border routers need upgrading before IPv6 is available | ||
| RU-Protvino-IHEP | 2014-05-29 | No | None | Not yet determined | No IPv4 exhaustion issues | Zero readiness for IPv6 in the Institute infrastructure | ||
| ru-PNPI | 2014-05-29 | No | None | Not yet determined | No | IPv6 deployment depends on our ISP | ||
| Kharkov-KIPT-LCG2 | 2014-05-22 | No | None | Not yet determined | No immediate shortage | |||
| T2_US_Purdue | 2014-05-29 | No | None | IPV6 to servers by 10-2014, nodes by end of 2014 | No immediate shortage | IP over IB gateways only support IPV4, work around in development | ||
| T2_US_MIT | 2014-06-03 | No | None | No immediate shortage | ||||
| T2_US_Caltech | 2014-05-30 | Yes | None | Plan is to have SRM, GridFTPs, Xrootd in production with IPv6 by the beginning of Fall, to support remote IPv6 clients. Other services will migrate as needed. | No immediate shortage | Need to validate the upgrade in test servers before switching in production. | ||
| IN_DAE_VECC_02 | 2014-05-30 | No | None | Yes, we have plan to switch to IPv6, Servers, switches are capable but have to decide with our Network provided. | Shortage of IPv4 addresses. | Discussing with NKN, India and with network provider for IPv6. | ||
| ZA-UJ | 2014-05-30 | No | None | ~ 18 months | No | University is in early stages of planning, production not planned for 18 months
| ||
| LRZ-LMU | 2014-05-30 | Yes | None | There are plans and things should be rather straight forward, but no schedule yet. | For storage-nodes, we do not expect any shortcomming of IPv4 addresses anytime soon. | I'm really pushing for this, but it's still a WIP. | ||
| KR-KISTI-GSDC | 2014-06-02 | No | No | When KISTI network is ready for IPv6 | No | Most of machines are supporting IPv6 but not yet has been tested | ||
| LIP-Lisbon | 2014-06-02 | Yes, but not to all site. | Only DNS and LIPCA, the rest of the site is not IPv6 enabled. | There are plans, but depends of upgrading the switchs firmware, no timeline is defined. | No | Most machines support IPv6 but not tested | ||
| LIP-Coimbra | 2014-06-02 | NO | There are plans, but depends of upgrading the switchs firmware, no timeline is defined. | No | Most machines support IPv6 but not tested | |||
| NCG-INGRID-PT | 2014-06-02 | NO | There are plans, but depends of upgrading the switchs firmware, no timeline is defined. | No | Most machines support IPv6 but not tested | |||
| ru-Moscow-FIAN-LCG2 | 2014-06-02 | No | None | Not yet determined | No immediate shortage | |||
| T3_US_TTU | 2014-06-02 | Yes | Some services enabled | Ready now | No shortage | |||
| FR-GRIF-IRFU | 2017-07-20 | Yes | Storage and WN's (since 10/2016) | No | ||||
| FR-GRIF-LLR | 2017-07-20 | Yes | CMS EU Xrootd redirector (since 5/2017) and storage (since 7/2017) | No | ||||
| T2-ES-CIEMAT | 2014-06-05 | Not yet. External router support ipv6 but we are in upgrading process of our internal routers to support ipv6 | None | Not clear, we pretend to offer basic services and routing within this year | No | |||
| RO-02-NIPNE | 2014-06-05 | No | None | Timeline not defined. No plans for now. | No. WNs on private network. | |||
| RO-13-ISS | 2014-06-08 | No | None | About one year. | No. | |||
| NIHAM | 2014-06-05 | No | None | Timeline not defined. No plans for now. | No. WNs on private network. | |||
| T2-ES-IFCA | 2014-06-05 | Not yet. | None | Timeline not defined. No plans for now. | Not yet. | |||
| T2_TR_METU | 2014-06-05 | No | None | Timeline not defined. No plans for now. | No immediate shortage | |||
| T2_TR_ULAKBIM | 2014-06-05 | No | None | Timeline not defined. No plans for now. | No immediate shortage | |||
| T2_BE_IIHE | 2014-06-05 | NO | None | Not plans yet | No | |||
| USC-LCG2 | 2014-06-05 | No | None | Not yet determined | No. The worker nodes are behind NAT, only our servers are using public IPv4 addresses with enough spares for the foreseeable future. | Central IT has done some preliminary tests to identify the hardware needs to deploy IPV6 | ||
| INFN-PISA | 2014-06-05 | No | None | Not yet planned | No. Worker nodes use private networks. | |||
| UNIBE-LHEP | 2014-06-05 | No | None | Not yet planned | No. All workers use private networks. | |||
| IEPSAS-Kosice | 2014-06-05 | No | None | Not yet planned | No immediate shortage | |||
| EELA-UTFSM | 2014-06-05 | No | None | Not yet planned | No immediate shortage | |||
| NCBJ-CIS | 2014-06-05 | No | None | Not yet planned | No immediate shortage | |||
| FMPhI-Bratislava | 2014-06-05 | No | None | Not yet planned | No. All workers use private networks. | Central IT will make a test in 1-2 years | ||
| T2_BR_SPRACE | 2014-06-05 | No. But switch our network to IPv6 is relatively easy. | none | Around six months, depending on how confident our team will be about running the software stack over IPv6. | No | |||
| CBPF | 2014-06-05 | No | No | Timeline not defined. No plans for now. | No immediate shortage | We do not have anything definite about the migration to IPv6 | Our machines have IPv6 support, but not yet have a date for when we will migrate to IPv6. | |
| UA-ISMA | 2014-06-06 | Yes | No | Before Q4 - 2014. | No | |||
| NCP-LCG2 | 2014-06-06 | To the institution, but not yet for the site. | Few IT services are on Dual Stack like Web. | Waiting for confidence about the middleware stability on IPv6. surely we will start migration very soon. | Almost all available IPv4 pools are in use, so it will near to exhasut. | No other issue as all Switches, Routers and Hardware are fully IPv6 supported. | ||
| Taiwan-LCG2 | 2014-06-06 | Partially, the router should be available to forward ipv4/ipv6 dual stack, but it hasn't verified, because we don't actually have ipv6 service running in our DC | None | Deploying and testing dual stack ipv4/ipv6 network. No concrete schedule yet, but hope to enable ipv6 support by end of 2014, at meanwhile will also follow any decision that made by WLCG | No, we still have at least two class-C available | None | ||
| T2_BR_UERJ | 2014-06-06 | No | None | No plans for now. | No | There is no plan for IPv6 transition. | Our machines have IPv6 support.
| |
| IndiaCMS-TIFR | 2014-06-09 | NO | Network is IPv6 ready but service readiness for IPv6 stack has to be tested and verified | Timeline not defined. No plans for now. | Yes, Managing through NAT, WNs on Private Network | ISP Infrastructure readiness and support needs to be determined | Currently network is served by Multiple ISPs and not all ISP are fully supporting IPv6 routing. Readiness of DNS Authority yet to be tested and verified. | |
| EELA-UNLP | 2014-06-09 | To the institution (slower than IPv4 and in testing), but not yet for the site. | None. | Timeline not defined. | No. | |||
| pic | 2014-06-10 | Yes, but on a limited 'test' basis. | DNS, web, perfsonar and dCache testbed. | Timeline not yet defined. | No. | No. | No. | |
| ifae | 2014-06-10 | Yes, but on a limited 'test' basis. | DNS, web, perfsonar and dCache testbed. | Timeline not yet defined. | No. | No. | No. | |
| MPPMU | 2014-06-11 | No | No | 2015 | No | No | No | |
| CA-CLUMEQ-MCGILL-T2 | 2014-06-17 | NO | NO, Not enabled | About one year | NO, No issues | We have to check with the provider if IPV6 is to be implemented on their end as well. | ||
| UA-KNU | 2014-07-02 | No | No | About one year | Yes | |||
| SARA-MATRIX | 2014-07-02 | Yes | DNS www etc, no grid services yet | Timeline not defined | No | |||
| T2_GR_Ioannina | 2014-07-02 | No | None | Not planned, yet | No | |||
| T2_US_Wisconsin | 2014-10-15 | Yes | Yes, GridFTP, Xrootd | Ready | No immediate shortage | 100 Gb/s switches will be available in this time scale | ||
| T2_KR_KNU | 2014-07-03 | Yes | Limited test machines | Network is ready. No defined date for other IT services. | No | |||
| UB-LCG2 | 2014-07-03 | No | None | Not yet determined | No IPv4 exhaustion issues | Zero readiness for IPv6 in the Institute infrastructure | ||
| ICN-UNAM | 2014-07-04 | No | No | University nework managers planning the full support but information no propagated to users yet. | No, enought ipv4 addresses at least for Grid | No | ||
| SUPERCOMPUTO-UNAM | 2014-07-04 | No | No | University nework managers planning the full support but information no propagated to users yet. | No, enought ipv4 addresses at least for Grid | No | ||
| RWTH-Aachen | 2014-07-11 | Yes, but only certain VLANs | No (with respect to Grid services). | Not yet determined. | No. | No. | IT Center already provides IPv6 connectivity and services. But we have no immediate need for IPv6 with respect to Grid services. | |
| Beijing-LCG2 | 2017-07-18 | Yes | SE is ready, CE and WNs can be done . | Can be done, No defined date. | No. | No. | ||
| T2_US_Vanderbilt | 2017-07-19 | No | No | Work in progress. Connectivity should be up within a month | Plenty of space. WNs are behind NAT and university has a large allocation | No | No | |
| T2_TW_NCHC | 2017-07-25 | No | No | At least one-year. The site will/may migrate to a new cluster and we intend to do it together. | No. We have a /28, but WNs are behind NAT. | No | The IPv6 infra is already OK in our institute. But we need time to migrate and make sure middleware works. Manpower will be the key. |
