CORD (Central Office Rearchitected as a Datacenter) combines NFV, SDN, and the elasticity of commodity clouds to bring datacenter economics and cloud agility to the Telco Central Office. An open reference implementation of CORD uses commodity servers and whitebox switches, coupled with open source software that includes OpenStack, Docker, ONOS, and XOS. This reference implementation is a general and extensible platform that supports a variety of domains and business units (e.g., residential, enterprise, mobile), but it is also sufficiently complete to support field trials, with an initial trial planned at AT&T.
E-CORD builds on that same the CORD infrastructure to support enterprise customers, alongside residential and mobile customers. In particular, and allows service providers can continue to offer enterprise connectivity services (L2 and L3VPN), but . It can go far beyond these simple connectivity services, as it allows them to include includes virtual network functions (VNFs) and service composition capabilities to support disruptive cloudbased cloud-based enterprise services.
In turn, enterprise customers can use E-CORD to rapidly create on-demand networks between any number of endpoints or company branches. These networks are dynamically configurable, implying connection attributes and SLAs can be specified and provisioned on the fly. Furthermore, enterprise customers may choose to run network functions such as firewalls, WAN accelerators, traffic analytic tools, virtual routers, etc. as ondemand on-demand services that are provisioned and maintained inside the service provider network.The project is a collaborative effort between leading service providers (AT&T, China Unicom, and NTT Communications) and some of the most prominent vendors in the networking space (NEC, Huawei, Lumentum, Ciena, Fujitsu, Oplink, Cavium). It also has joint activities with the Metro Ethernet Forum, the leading industry consortium for carriergrade Ethernet solutions.
We will demonstrate a proof of concept implementation of E-CORD, which consists of a packet/optical metro network with three Central Offices as CORD sites. The showcase will have user portals and GUIs to configure enterprise services, interact with operational parameters, and visualize the provisioning. Finally, we demonstrate the world's first disaggregated ROADM, moving away from a closed, chassisbased, proprietary, and vertically integrated ROADM and towards a white box model controlled using open interfaces and protocols.
What key business or technical challenge is addressed by this solution? The technical challenges are threefoldtwofold. First, software defined control of a converged packet/optical wide area network requires innovative multi-layer and delegated control primitives. Second, carrier grade connectivity services have elaborate service model specifications, and deploying these on white box infrastructure introduces hardware support issues. Third, control and configuration of a disaggregated ROADM platform needs careful design of abstract interfaces. Finally, an open challenge is maintaining high performance levels for transmission and signal integrity in the optical white box model.challenges.
Describe the “open” component(s) that the solution incorporates: Our work leverages and builds further on a fully open source stack.
● Atrium is the software stack that runs on each whitebox switch. It includes Open Network Linux, the Indigo OpenFlow Agent (OF 1.3), and the OpenFlow Data Plane Abstraction (OFDPA), layered on top of Broadcom merchant silicon. We also present a fully open sourced implementation of MEF Forum (MEF LSO Presto interface) services running on top of commodity hardware using open protocols (OpenFlow etc.). Finally, we demonstrate the world’s first disaggregated, whitebox ROADM, built using commodity hardware components and controlled using open interfaces
E-CORD demonstrated its first PoC at ONS 2016 (March) with an E-line application over hardware, including three Disaggregated ROADMs. Work is in progress to develop Carrier Ethernet services and service models, and formally integrate the E-CORD related functions in ONOS with XOS to enhance NFV functionality.
The timeline below summarizes the goals: