Difference between revisions of "IPv6 WLCG Site Survey"
From GridPP Wiki
(→Answers by Site) |
(→Answers by Site) |
||
| Line 475: | Line 475: | ||
| Not yet determined | | Not yet determined | ||
| No immediate shortage | | No immediate shortage | ||
| − | | | + | | Border routers need upgrading before IPv6 is available |
| | | | ||
|- | |- | ||
Revision as of 06:53, 29 May 2014
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 | |||
| 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 | 2014-05-14 | Yes | Most services enabled but not dCache storage element | Essentially ready now. Storage element should be ready when when dCache v2.9.0 goes into production | 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-Brunel | 2014-05-14 | Yes | Perfsonar enabled. Experimental DPM storage enabled and passing Nagios tests. | Only limitation to completely convert to dual-stack is DPM-xroot: No IPv6 version available. However, we have tested and jobs can run on dual stack nodes using IPv4 xroot. | 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-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 | ||||
| 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-05-16 | No | - | A testbed creation is in progress, ETA end of summer 2014 | 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 | ||||
| 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 | ||||
| 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 | ||||
| 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 | 2014-05-28 | NO | NO | Planned for this year | None | Dedicating resource to core network with IPv6. | |||
| JINR-T1 | 2014-05-28 | NO | NO | Planned for this year | None | Dedicating resource to core network with IPv6. | |||
| 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 | ||||
| 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 | 2014-05-28 | Yes | xrootd, gridftp, SRM endpoints primarily though all Tier2 related machines have IPv6 addresses (just not necessarily AAAA records) | Remaining issue is full DHCPv6/DNS support for all hosts to have proper DNS. Supplied via campus networking, should be within months. | Yes in that we switched workers to public IPs but likely can't grow by an order of magnitude in this way | Just the lack of full DHCPv6/DNS support from our campus | |||
| 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 | ||
| 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 infrustructure |
