Brief introduction to the Onos of Onos preheating article (i)

Onos after the advent of widespread concern, about Onos and ODL dispute, recently small series read Onos white paper, and do a little superficial summary, the following to share with you.

1 Onos Birth Background 1.1 Onos The benefit analysis of the birth

With the increasing popularity of mobile devices, the rise of OTT services and content distribution has led to an urgent need for a network revolution in service provider networks. To cope with the growing bandwidth demands, service providers want to be more agile and efficient, and to be better share from innovative services and new business models, as SDN becomes more demanding. While the controller in SDN occupies an important part, is a military battleground, a lot of SDN controllers have appeared in succession, such as Opendaylight, Opencontrail, Ryu, Floodlight, NOX, spox and so on, One of the most notable of these is opendaylight.

Opendaylight is a device-led open-source controller, although the banner of Open, but Opendaylight has been rejected based on open protocol scheme, but want to adopt a compromise solution, that is, to open a dedicated interface to preserve traditional devices, Take A to retreat way to defend your own interests. Admittedly, the equipment vendors have rich experience in equipment development, Opendaylight is indeed an excellent controller, but under such pressure, operators have to take countermeasures. As a result, operators launched an open network operating system Onos.

1.2 Onos and why with Opendaylight?

There have been several controllers for software-defined networks over the past few years, however, we know very well that most controllers lack scalability, reliability, and in addition, their performance is not good and the abstraction layer is too simple and coarse, and can not be used for commercial products. These controllers send OpenFlow messages directly to the feature components, which create OpenFlow messages directly for network devices, so that these controllers are more like device drivers. They do not have the performance characteristics required for a complete SDN controller platform. What really needs is an integrated network operating system, Onos is created to meet these needs.

An operating system should have the following features:

• User resource management. Ensure that all users have the same rights, that there is no resource scarcity, and that resources are not distributed equitably and rationally.
• User isolation. Because each user wants to allocate resources in full, it isolates users from one another, multiplexing across multiple applications and multiple devices, and enables users to enjoy their own virtualized OS-actionable applications through resource virtualization technology.
• Abstraction Layer management. Provides an abstraction layer for users to use the operating system to manage the services and resources, without understanding the complexity of the network, and without changing the application of the premise, can flexibly expand the operating system management equipment.
• Provide user security mechanism.
• Provide agile and efficient services. Users do not need to rebuild the same service to improve their efficiency.

Onos has all the features of an operating system, not just the functions of the controller. In addition, Onos also provides a technical community column to provide more research scholars with a broader platform for communication and sharing.

2 Onos Community Overview

Onos's release is an industry feast that gathers well-known service providers (such as T-T, NTT Communications), high-standard network providers (such as Ciena, Ericsson, Fujitsu, Huawei, Intel, NEC), Network operators (such as Internet2, CNIT, create-net), and other partners (such as Sri, Infoblox), and receive onf support.

Goals of the 2.1 Onos community

Create a community to work together to achieve the vision and mission of SDN:

• Production of high-quality network operating system software;
• Create efficient open source processes to attract more people;
• Through continuous efforts and contributions to promote social science and technology, the development of life.

2.2 Onos Community's self-requirements

• Customers, customer service;
• Elite, the use of elite management system;
• Innovation, persist in innovation;
• Quality, consistent pursuit of high quality;
• Respect, always respect others;
• Transparent, transparent operation and management.

3 Onos Introduction

Service providers want their networks to be agile and efficient, to meet growing bandwidth demands, and to gain revenue from innovative services and new business models. Software-Defined Networking SDN is key to service provider network transformation, and Onos is a new carrier-Class SDN network operating system designed to provide services, developed jointly by leading service providers, suppliers and developers in the On.lab and Onos communities.

Onos is the first open Source SDN network operating system, primarily for service providers and enterprise backbone networks. Onos is designed to meet the needs of the network to achieve high reliability, good performance and flexibility. In addition, Onos's north-to-interface abstraction layer and API support simple application development, while the south-to-Interface abstraction layer and interface can control openflow or traditional devices. Overall, Onos will implement the following features:

• Carrier-class features at the SDN control level (high reliability, good performance, flexibility);
• Provide a strong guarantee of network agility;
• Help service providers migrate from existing networks to white-card devices;
• Reduce capital expenditure and operating expenses of service providers.

Onos Architecture Overview:

The Onos has the following core functions:

• Distributed core platform, providing high scalability, high reliability and high stability performance, realize carrier-Class SDN controller platform features. Onos operates like a cluster, enabling the SDN control platform and service provider network to have web-based agility.
• The north-to-interface abstraction Layer/apis, the graphical interface and the application provide more friendly control, management and configuration services, the abstraction layer is also an important factor to achieve web-style agility.
• The south-to-the-interface abstraction Layer/apis, the pluggable South interface protocol can control OpenFlow devices and traditional equipment. The south-to-interface abstraction layer isolates the Onos core platform and the underlying device, shielding the differences between the underlying devices and protocols. And the South interface is the key to move from traditional equipment to openflow white card equipment.
• Software modularity enables Onos to be developed, debugged, maintained and upgraded by community developers and service providers like software operating systems.

Sdnlab Language: The advent of the SDN ERA provides a transformational opportunity for service providers to share from innovative services and new business models, and service providers have been exploring a springboard for transformation. Onos is a product designed to provide services to help service providers transform. With the onos of the war, the industry is increasingly competitive, SDN development prospects are becoming clearer. Looking forward to December 5, Onos's debut!

Article from http://www.sdnlab.com/3991

Brief introduction to the Onos of Onos preheating article (i)