1 / 10

RAL Site report

This report provides an update on the progress of IPv6 deployment at RAL, including the dual-stack services, storage plans, network upgrades, and future actions. It also discusses the worker nodes and plans for connecting RAL to LHCONE.

duffye
Download Presentation

RAL Site report

An Image/Link below is provided (as is) to download presentation Download Policy: Content on the Website is provided to you AS IS for your information and personal use and may not be sold / licensed / shared on other websites without getting consent from its author. Content is provided to you AS IS for your information and personal use only. Download presentation by click this link. While downloading, if for some reason you are not able to download a presentation, the publisher may have deleted the file from their server. During download, if you can't get a presentation, the file might be deleted by the publisher.

E N D

Presentation Transcript

  1. RAL Site report HEPiX IPv6 Working Group F2F Meeting 25th Jan – 26th Jan 2018 Rajan Atthi rajan.atthi@stfc.ac.uk

  2. About Me • Network Engineer with the Network & Comms group at RAL • 3 month work secondment with RAL Tier-1 • Working on IPv6 Deployment to meet WLCG Deadline • Martin Bly, Catalin Condurache and Kashif Hafeez are continuing with their efforts

  3. Current Status • Squid Service has been dual stack since August 2017 • FTS Service has been dual stack since October 2017 • CVMFS Stratum 1 has been dual stack since October 2017 • HA Proxy service dual stack enabled November 2017 • Echo - 1 test gateway IPV6

  4. Storage Plans • Requirement to have production quality Dual Stack access to storage by April 2018 • RAL runs two storage Services : • CASTOR disk endpoints are being decommissioned • Echo to be made dual stack mid February 2018 • GridFTP & XRootD transfers have been validated against test Echo’s dual stack gateway • We expect significant traffic to go via IPV6 over the OPN as soon as the production gateways are enabled • We need full confidence in the Network …

  5. During initial deployment of IPV6 separate physical links were used, with lower bandwidth.

  6. Currently IPV4 = 2 x 40Gb IPV6 = 2 x 10Gb A Snapshot of recent IPV4 traffic shows that 10Gbs is not enough to handle the current load on the Firewall bypass

  7. 100G External Links to JANET Upgrade of the external connectivity to JANET/JISC to 100Gb. Target of June 2018 New Site Firewall Tier-1’s connection into the Site core. The current Firewall does not support IPV6 Natively. Target upgrade of April 2018

  8. To do • Consolidation of production networks • OPNR Firewall bypass (Feb 7th..) • Echo Gateways dual stack (Feb 14th) • 40Gb into the Site Core • New RAL Firewall (IPV6 Native,Target April 2018) • RAL 100Gb Links (Target June 2018) • Policy going forward  Tier-1 machines are dual stack by default • Deployment needs to be automated • Work has started to connect RAL to the LHCONE • Target is to have part of RAL connected by Q4 of 2018

  9. Worker Nodes • HTCondor Batch Farm • 600+ worker nodes • Running version that supports dual stack • Behind Firewall, connect externally to many services on different ports • We intend to enable restrictive IP6tables on all machine from the beginning • I will be looking at a way to automate this configuration • Comments/suggestions welcome

  10. Any Questions?

More Related