{'fraction_non_alphanumeric': 0.026331538001196888, 'fraction_numerical': 0.0011968880909634949, 'mean_word_length': 5.8244897959183675, '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}}
DataPlane Broker: Open WAN control for multi-site service orchestration

NFV-MANO has become the de-facto standard for network service orchestration in future programmable network infrastructures. Relevant standards define an architecture and a data model that allows an orchestration entity to deploy, dynamically configure and monitor virtual and physical network functions across virtualized datacenters. Although the model offers extensive details for network function management and host-level network configuration, end-to-end connectivity management beyond the datacenter remains limited. The responsibility for cross-site connectivity is delegated to a control abstraction, the WAN Infrastructure Manager (WIM), which is partially defined in relevant standards. The reference implementation of the NFVMANO standards, Open Source MANO (OSM), has recently released a reference WIM driver model, but no open-source WIM implementation is currently available, thus restricting the ability of researchers to experiment with multi-site service deployments. In this paper, we present the DataPlane Broker (DPB), the first open-source WIM implementation for software-defined networks. Using an extensive data model, DPB seamlessly translates NFVMANO requirements into SDN configuration, supporting point-to-point and multipoint connectivity with strong bandwidth guarantees. DPB is integrated with OSM FIVE via a WIM plugin. Initial experiments highlight that path computation can scale to large network topologies and a large number of services, with negligible computational overheads, while DPB increases by less than 10% the overall deployment delay of an OSM service.