{'fraction_non_alphanumeric': 0.020677413164459795, 'fraction_numerical': 0.0018230665899059682, 'mean_word_length': 5.2038690476190474, 'pattern_counts': {'":': 0, '<': 0, '<?xml version=': 0, '>': 0, 'https://': 0, 'lorem ipsum': 0, 'www.': 0, 'xml': 0}, 'pii_count': 0, 'substrings_counts': 0, 'word_list_counts': {'cursed_substrings.json': 0, 'profanity_word_list.json': 0, 'sexual_word_list.json': 0, 'zh_pornsignals.json': 0}}
Network Capabilities for the HL-LHC Era

High Energy Physics (HEP) experiments rely on the networks as one of the critical parts of their infrastructure both within the participating laboratories and sites as well as globally to interconnect the sites, data centers and experiments instrumentation. Network virtualisation and programmable networks are two key enablers that facilitate agile, fast and more economical network infrastructures as well as service development, deployment and provisioning.Adoption of these technologies by HEP sites and experiments will allow them to design more scalable and robust networks while decreasing the overall cost and improving the effectiveness of the resource utilization.The primary challenge we currently face is ensuring that WLCG and its constituent collaborations will have the networking capabilities required to most effectively exploit LHC data for the lifetime of the LHC. In this paper we provide a high level summary of the HEPiX NFV Working Group report that explored some of the novel network capabilities that could potentially be deployment in time for HL-LHC.


Introduction
Network virtualisation and programmable networks are nowadays quite common in the commercial clouds and telecommunication deployments and have also been deployed by some of the Research and Education (R&E) network providers to manage Wide-Area Networks (WAN). However there are only few HEP sites pursuing new models and technologies to build up their networks and data centers and most of the existing efforts are currently focused on improvements within a single domain or organisation, usually motivated by the organisationspecific factors. Therefore, most of the existing work is usually site or domain-specific. In addition, there is a significant gap in our understanding of how these new technologies should be adopted, deployed and operated and how the inter-play between LAN and WAN will be organised in the future. While it's still unclear which technologies will become mainstream, it's already clear that software (software-defined) and programmable networks will play a major role in the mid-term.
With the aim to better understand the technologies and their use cases for HEP a Network Functions Virtualisation Working Group (NFV WG) was formed within the High Energy Physics Information Exchange (HEPiX) [1]. The group produced a report [2] identifying the work already done, looking at the existing projects and their results as well as better understanding the various approaches and technologies and how they might support HEP use cases.
This paper focuses on brief high level overview of the existing approaches in network virtualisation and programmable networks. It explains how current paradigm shift in the computing and clouds is impacting networking and how this will fundamentally change the ways networks are designed in the data centers and sites. Cloud native networking approaches involving new topologies, network disaggregation and virtualisation have been identified as primary drivers that will impact data centre networking, which will in turn impact how data centres will be inter-connected in the future. In the second part which is devoted to the programmable wide-area networks, capacity sharing, network provisioning and softwaredefined approaches where key R&D projects in the area are highlighted. The paper concludes with a proposed areas of future work and potential next steps.

Cloud Native Data Centre Networks
One of the main drivers for network evolution in the data centres is the changing nature of the applications. With the dawn of virtualisation, applications have started to morph at an accelerating pace and moved from mostly static deployments (on bare metal servers) through virtual machines to containers and more recently to clusters of containers sometimes referred to as microservices. This evolution causes a particular change for networking, the usual lifecycle of the application (develop, deploy, update, re-deploy) has decreased from hours to microseconds. Establishing a full scale cluster of hundreds of containers can be done in less than a second, and upgrades or re-deployments of such a cluster can be done on a rolling basis, which means that the entire cluster can be replaced with new containers, all over again in seconds. Going even further, all this can be performed from a central location that can control a set of federated clusters requiring very little or no effort on the end sites to perform most of these tasks. This increasingly dynamic environment could become a major challenge for the networking infrastructure, which will need to keep up with this rapid pace.
The rise of Linux and the economics of scale has led to the development and operations of clouds. HEP sites have been predominantly statically deployed with allocations usually served by batch systems, operating at job level granularity with high capacity storage hosting the datasets locally. This is changing as experiments are starting to deploy their job payloads in containers and services are moving to container-based deployments (such as Kubernetes [3] [4]). This creates an interesting environment where multiple technologies are starting to overlap and compete. Some of the NSF-funded projects such as SLATE [5], that investigate new infrastructures for sites, are entirely based on Kubernetes. Physical analysis running in containers with full dataset uploaded to the cloud has been demonstrated running on the Google Cloud Platform [6]. It can be expected that this evolution will continue and accelerate, potentially having a major impact on the networking at HEP labs and sites.
Network engineers are facing major challenges while trying to accommodate the new computing models in an environment where they often need to support not only cutting edge container technologies that are now popular, but at the same time legacy systems ( "bare metal" ), virtual machines and other equipment that needs to be connected to the network or even multiple networks (e.g. experimental equipment, technical networks) with custom designs and protocols.
Fast paced application life-cycle is not the only challenge, virtualisation is progressing into areas that were previously tied to the hardware, such as GPUs or storage systems. With GPU and storage virtualisation, there is a need for lower latency and higher throughput within the data centre in order to enable more efficient allocation and use of resources.
Network vendors have already recognised the cloud opportunity and have started to reprofile their revenue expectations from enterprises towards cloud providers. This will likely have an impact on what the vendors will start offering and how the network infrastructure and supporting software will evolve in the mid-term. The primary drivers that were identified in the report [2] as having a potentially strong impact on the data centre networks are following: • Container networking -the current generation of applications are complex sets of services that run on a simple compute infrastructure with multiple levels of virtualisation that needs to rely on a simple networking model that scales easily and can support significant amount of east-west traffic. Deploying individual solutions for each functionality introduces complexity, making it extremely difficult to operate and troubleshoot. Coming up with a single solution is non trivial and requires both application and network engineers to come together, which (among other things) makes container networking hard.
• Rethinking network design -current cloud-native data centers rely on the Clos topologies [7] to build up a large-scale DC hosting container and VM technologies. Clos can be used to build very large networks with simple fixed form factor switches -allowing homogenous equipment -that greatly simplifies inventory management and configuration. The new interconnect model is usually based only on routing (layer-3) and bridging is supported only at the leaves (i.e. within a single rack). The rest of the inter-connectivity relies on some form of network virtualisation.
• Network Virtualisation -there are many existing approaches in network virtualisation, some of which are shown in Fig.1. They range from open source network operating systems running on hardware/bare metal switches and open routing platform, different software switch deployments up to Linux kernel network stack extensions. Currently it's unclear which approaches will become mainstream as a period of consolidation is likely coming.
• Network Disaggregation -an important trend in network technologies that describes efforts to decouple network devices into open source hardware and open network operating systems. This will have a profound impact on the evolution of the network similar to how server disaggregation impacted compute in the past century.
• Programmable Network Interfaces -an area of intense research and interest of network interface vendors, data center architects and end-users trying to optimize network performance. While network programmability in both NICs and switches has been possible in the past, significant advances were made recently due to network disaggregation efforts, invention of new programming languages and compilers (such as P4) as well as efficient hardware implementations.
Cloud native networking and related technologies are providing a way how to design and cost effectively operate large scale DC networks. Still a number of challenges remain, both technological and non-technological that could impact a broader adoption by the HEP community: • Most existing HEP sites won't be able to re-design their DC networking from scratch, requiring us to find ways to progressively migrate to new capabilities while accommodating existing constraints. • Historically, there has been a very clear separation between network and compute, but this no longer applies for the cloud native approaches where complex networking is present at the level of servers/hypervisors. This means that network and compute engineers must work together and build up expertise in the cross-domain areas. • Collaboration between the sites will also be very important to bridge the gap and come up with more effective approaches that better fit the existing HEP use cases. Encouraging closer collaboration between network and compute engineers within and across sites will be therefore an important factor in the adoption. • Automation of the networking is another important area as relying on the open source network operating systems usually requires migrating to standard open source configuration tools. In addition, the usual approaches that work for configuration of compute might not work for network infrastructure due to various reasons. • Data Center Interconnect technologies (both HW and software-based) are quite novel approaches that will require initial deployments to evaluate how they could benefit inter-DC networking for federated use case such as data lakes [8]. • A range of other approaches that are only mentioned briefly in the report such as GPU, virtualized storage, hyper-converged architectures and edge services for HEP instrumentation and experiments will require initial testbeds and evaluations.
This section highlights core solutions and technologies that could help our community to rethink the way we design and operate our data centre networks and offer a great opportunity to build large scale data centers (centralised or distributed) that could benefit from economies of scale, simplification of the operational models and potential reduction in the overall operational cost, but apart from technology this will require new policies, priorities and funding to materialise.
Some of the most promising areas of R&D that could lead to a broader adoption of the mentioned technologies are container-based compute platforms such as SLATE edge services, HTCondor [9] container back-ends or native container-based sites that could offer the best opportunity to test and evaluate cloud native networking. Provisioning of the storage servers with software switches and/or virtualized storage solutions is another area that has the potential to be easily deployed and tested. Finally, it's also very important that cloud native approaches are considered for any planned extensions of existing centres or new data centers right from the start.

Programmable Networks
Paradigm shift in the computing and its impact on the network technologies as described in the previous section will make it easier to design and develop bigger data centres that will be inter-connected at very high capacities at lower latencies with a possibility to easily off-load to nearby Clouds, HPC centres or other opportunistic resources. A cluster of such centres can then create a federated site that will be exposed behind a single endpoint/interface for the experiments. This transformation has already started within the WLCG data lakes activities and some of the participating sites are already running their storage and or compute in a federated setup [8].
At the same time, small to medium sites will be able to complement the functionality of the core sites by off-loading some of their services by means of Kubernetes or other federated orchestrators. This can have a profound impact as design and development of the offline HEP distributed computing model can be radically simplified. HEP sites that could support different workloads by only running a single container orchestration or edge system are likely to be possible int he future (this is in a way revolutionary and will impact many different aspects of running a HEP site, apart from networking, also security, operations and management policies).
From a network perspective operating a set of clustered DCs will bring its own challenges and will require closer collaboration with the R&E providers. Provisioning of the networks, network telemetry, packet tracing and inspection as well as overall security and network automation will need to improve in order to make it easier for the federations to operate not only their inter-DC activities, but also easily expose their services to the outside.
Historically the National Research and Education Networks (NRENs) have managed to meet HEP networking needs by strategically purchasing capacity when network use exceeded trigger thresholds. This has been a straightforward method to provide seemingly unlimited capacity for HEP, requiring no new technologies, policies or capabilities. There were occasional "bumps" when regional or local capacities didn't keep up, but overall over-provisioning resulted in an excellent networking for HEP. There are reasons to believe that the network situation will change due to both technological and non-technological reasons starting already in the next few years. Other data-intensive sciences will join with data scales similar to LHC [10], which will impact not only R&E providers, but also the way end-users are currently utilising the network. In the new multi-science high throughput environment, network provisioning, design and operations will need to evolve to better share and organise the available resources.
WAN programmable networks address many of the challenges outlined above and have the potential to change the way HEP sites and experiments connect and interact with the network. Some of the key projects in the domain of orchestration, automation and virtualisation of WAN are following: • Programmable Networks for Data-Intensive Sciences has a number of key technologies and projects in different areas such software-defined WAN (SD/WAN), software-defined exchanges (SDX), network orchestrators (e.g., SENSE [11] and NOTED [12]), network provisioning systems (e.g. multi-ONE) and network-aware data transfer systems (e.g. BigDataExpress [13]. • Research & Education Networks Programmable Services are planned by both ESNet [14] and GEANT [15] and include projects such as ESNet6 [16], FABRIC [17], GEANT OAV [18] and GTS [19].

Challenges and Outlook
Programmable WAN is still an area of intensive research and development and while the existing projects have well defined scope and good match to the HEP use cases, there are still a number of challenges that remain: • One of the core challenges for some time is the fact that it appears to be difficult to bring the existing projects from testbed/prototype stage into production. Within LHCONE [20] R&D efforts, a number of projects were successfully demo-ed in the past, but it has proven to be very challenging to deploy them in the production infrastructure. What appears to be missing are network infrastructures where prototypes can be tested at scale and then easily deployed/migrated to production (e.g. FABRIC). • Network provisioning will need to evolve to address multi science domain entering the R&E networks requiring advances in capacity organisation, network management, accounting and monitoring.
• There is currently a significant lack of available telemetry, tracing and insight into how the current network operate and how such data can be programmatically accessed. • From the perspective of data transfer systems, there are significant gaps in both achieving the maximum bandwidth (end-to-end) as well as organising allocations of capacity in ways that would avoid bottlenecks and allow more efficient sharing of the available capacity. • As another alternative, automated methods for traffic engineering that would automatically adapt to the existing workloads have been proposed by different projects (both in SDX and orchestrators). Such systems promise to keep the existing status quo where state of the underlying network and its operations are transparent to the experiments. It remains to be seen if such approaches will be feasible in a large scale federated environments (such as LHCONE).

Proposed Areas of Future Work
A primary goal of the HEPiX report [2] was to seed a collaboration between the experiments, the sites and the research and education networks to deliver capabilities needed by HEP for their future infrastructure while enabling the sites and NRENs to most effectively support HEP with the resources they have.
In this section we outline three possible areas of future work that can help tie together activities within and among the experiments and sites with network engineers, NRENs and researchers. It is critical that we identify projects that are useful to the experiments, deployable by sites, and that involve a range of participants spanning the sites, the experiments and the (N)RENs. Without the involvement of each, we risk creating something unusable, irrelevant or incompatible. The following are not meant to be exclusive, merely suggestions based upon the working groups interactions and discussions amongst its members.
• Making our network use visible -Understanding the HEP traffic flows in detail is critical for understanding how our complex systems are actually using the network. With a standardized way of marking traffic, any NREN or end-site could quickly provide detailed visibility into HEP traffic to and from their site, a benefit for NRENs and users. • Shaping data flows -It remains a challenge for HEP storage endpoints to utilize the network efficiently and fully. Shaping flows via packet pacing to better match the end-to-end usable throughput results in smoother flows which are much friendlier to other users of the network by not bursting and causing buffer overflows. • Network orchestration to enable multi-site infrastructures -Within our data centers, technologies like OpenStack and Kubernetes are being leveraged to create very dynamic infrastructures to meet a range of needs. Critical for these technologies is a level of automation for the required networking using both software defined networking and network function virtualization. As we look toward HL-LHC, the experiments are trying to find tools, technologies and improved workflows that may help bridge the anticipated gap between the resources we can afford and what will actually be required to extract new physics from massive data we expect to produce. To support this type of resource organization evolution, we need to begin to prototype and understand what services and interactions are required from the network. We would suggest a sequence of limited scope proof-of-principle activities in this area would be beneficial for all our stakeholders.

Conclusion and Summary
We have described the work of the HEPiX Network Function Virtualization working group and their phase I report and indicated what we believe are the important areas for HEP to consider regarding future networking requirements as well as outlining specific proposed areas of work for the near, mid and long term.