Editor's note: This series is divided into three ONOS white papers to translate, and then theONOS White Paper medium ONOS Architecture , this article translates the remainder of the white Paper ONOS Value proposition and summary, if there are inappropriate, please correct me.
6.ONOS Value Proposition -- carrier use case
6.1 Multilayer SDN Control
Service providers operate multi-tiered networks. For example, a service provider might operate an IP Data Network and a transport network or optical network at the same time. The IP layer may have a tunnel layer above it, creating a service similar to a virtual IP layer network. Currently, each layer is managed separately resulting in low network utilization, high operating costs, and a reconfiguration cycle of up to several months. For example, in today's environment, data network designers will generally reserve a certain amount of bandwidth to solve network failure and network tidal phenomenon. The transport network designers also make the same reservation. Furthermore, data network designers tend to keep the average utilization of the network at 30%. Therefore, the total will cause network capacity 4-5 times over-provisioning.
the SDN Multilayer network control solves these problems. The solution consists of three parts:
1. extending the OpenFlow, such as adding programmability to optical transmission units (e.g. roadms)
2.ONOS Create graphical views for each layer of network and maintain mapping or communication between them
the PCE application on 3.ONOS establishes and routes the path based on the multiple associated network views.
Although the PCE application is a single individual, it is possible to configure, monitor, and orchestrate each layer. For example,IP connection changes can trigger an automated configuration of the light path. Operators can reduce operating costs through central control, improve network utilization across tiers, and reduce network reconfiguration time to minutes. One of the applications of this network capability is bandwidth planning applications that allow bandwidth reservation. ONOS prepares the data layer and optical network layer resources to provide bandwidth assurance and monitor resources to reroute and adjust operations based on the latest network events and other changes.
SDN Multilayer Network control is a typical example of how ONOS implements SDN control, effectively reducing capex and opex, and facilitating the creation of new services.
6.2sdn-ip Coexistence and extended SDN control Platform
Today, autonomous systems are interconnected with the internet andBGPShare status information. ONOSinSdn-ippeering applications are designed to help service providers grow from small to smallSDNdeployment. A service provider can deploy a smallSDNNetwork or aSDNIslands, and throughSdn-ipPeering Application UtilizationBGPAgreement willSDNThe network is seamlessly interconnected with other parts of the network, withSdn-ipapplication, aSDNThe web is just another part of the Internet as. Over time, service providers have the flexibility to expandSDNnetwork, which achieves all the benefits and does not affect peering with the internet. Also, a service provider can useSdn-ipPeering apps willSDNNetwork interconnection to build a largerSDNhomemade systems, like other asconnected to the Internet.
Sdn-ip Application and as edge routers interconnect, like today's standard exchange between autonomous systems ip prefix routing information. sdn-ip Peering applications use routing information as sdn Multiple network prefixes in the network establish a forwarding path. So, sdn ip address forwarding ip flow.
In addition, sdn-ip onos based sdn control platform. For example, sdn networks can be like non- sdn autonomous system by BGP interconnect, considering these sdn The network works the same way, and the other internet can put a set of sdn as
so Peering applications promote incremental and seamless deployment of service providers on network infrastructure SDN on. Lab internet2 deployed sdn-ip Span style= "font-family: the song Body;" > Peering applications, using internet2 sdn backbone network implementation is sdn migrating campus network interconnection.
6.3 Central Office network function as a service
The most valuable asset that telecom operators have is the central office, which is geographically closer to a large number of end-users, so this is the key to ensuring that telecom operators provide flexible and efficient services to a large number of users. For example , at/T operates near 4500 Central Office in the United States , and a typical office in a large city is serviced by Cable and 10 million cordless phone users, as well as thousands of businesses. A typical central office has a lot of access, Exchange capacity, various network functions of the intermediary devices. Although the Central Bureau is important to telecom operators, it has been developed for many years and is becoming increasingly more complex in terms of network switching / routing, intermediary devices and user terminals, which means significant capital and operating expenses.
No surprise, telecoms operators want to re-structure the central office, they want to the data center economy, flexible application to the Central Bureau. This means using SDN to design the central office structure, transferring the network functionality of the intermediary devices to the x86 Server (known as network function virtualization) as software. and orchestration system running on the software (so become network function virtualization), orchestration System for users and enterprise users to orchestrate network functions and network traffic, dynamic service for all types of users to achieve a variety of users and providers of various strategies.
This shift in the central Office allows service providers to quickly build, deploy, and deliver new services, while significantly reducing costs and operating expenses.
Onos onos and its applications and Span style= "font-family: ' Times New Roman ';" >openflow switch will help push the central office network structure into a transition to sdn structure that provides the flexibility required for network functions as a service. We want to deepen this use case in two directions: demo onos sdn
6.4 Segment Routing- - driving MPLS Development and improvement
The present Ip/mpls is complex and difficult to manage. Label distribution, traffic engineering, and VPN are complex operations and services that rely on a collection of distributed protocols on the control platform. In addition, the network debugging is difficult, it is difficult to take into account the control platform and the label Exchange data platform between the synchronization and state management problems.
The IETF has introduced the concept of segmented routing for MPLS . It introduces a global label that does not need to be exchanged for each hop. Label-based source routing is also introduced to eliminate dependency on label distribution and complex protocols such as LDP,RSVPin LSP setup. In this way, segmented routing simplifies the control layer and data layer of the MPLS network. However , the SR Routing and label distribution still relies on an internal gateway protocol, which allows the external controller to control the end-to-end tunneling initiated by the source router.
The segmented routing use case is seekingONFof theSpring-openProject cooperation. This project demonstrates how to baseONOSand theSRApplication-builtSDNThe control platform implements segmented routing and is capable of running on bare-metal routers based on existing chips. This scenario does not use a router-embedded distributedIGP, but uses theONOSa routing application on the and the application controls the default and policy-based routing of the Edge router and the hub router, which is forwarded using the segmented routing rules. Network operators can communicate their own policy requirements to the controller,ONOSand the tags in their application management network can beIp/mplsimplement these policy controls on the network
So ONOS 's segmented route demonstrates how a service provider Constructs a simple control layer on the MPLS data plane, so it combines the simplicity of the SR MPLS data plane and The flexibility of the SDN control plane.
7. Summary
Our goal is to provide an open-source SDN network operating system for service providers and other core networks. ONOS is designed to provide:
Carrier-grade features such as flexibility, high reliability, throughput, and latency are good performance;
North to abstract layer /apis Reduce the difficulty of creating new service, bring web-style agility to network;
The south-to-the-abstraction layer supports the device / Protocol plug-in, so ONOS can control OpenFlow white cards and traditional devices.
This makes it easier to migrate to SDN based on white-card machines .
Our partners present a range of use cases to guide our work, which includes top service providers and equipment vendors.
ONOS launched a network operating system platform in one month, but we are still a long way from realizing ONOS product. We need to develop more use cases, continue to improve performance, strengthen core features, and do more testing and deployment to create real product support points. ONOS is a milestone in the development of a larger group to join us in driving the growth of this platform, moving towards a common goal of providing carrier-grade, open-source SDN operating systems.
This article is from Sdnlab, click here to read the original. If you are interested in this article, you can participate in the following interactive ways to communicate with the author in close range. In addition, our portal also has a large enterprise recruitment platform, there are many high-quality posts, interested parties please click the recruitment to see the details.
If you are interested in this article, you can participate in the following interactive ways to communicate with the author in close range.
(1) Weibo (http://weibo.com/sdnlab/)
(2) ( account No.:Sdnlab)
(3) QQ Group
SDN Research Group (214146842)
Opendaylight Research Group (194240432)
Onos Onos value proposition in the next article of the white Paper