Onos Architecture-Overview

This is read Https://wiki.onosproject.org/display/ONOS/Architecture+Guide is by the way translated, currently intermittent in reading, today first put part

Overview

Based on OSGi, architecture design Objectives:

A. Code modularity to introduce new features with some kind of independence

B. Configuration, functions can be loaded and unloaded during start/run time

C. Clear boundaries between subsystems and modules

D. Protocol flexibility, not binding to specific protocols, protocol libraries and implementations

A.onos consists of a series of sub-projects, each with a code tree, which can be built independently. Onos code tree Hierarchy Organization, leveraging MAVEN's hierarchical Pom file organization concept, and parent directory aggregation

Pom file interaction. The latter contains shared dependencies and configurations for each subproject. The Onos root Pom file is used to build all the sub-projects

---Developer's Guide Appendix C describes pom details

B.onos uses the Karaf as the OSGi framework, the dependency solution, and the runtime module to dynamically load. The KARAF provides

.

Developing rest APIs using the standard JAX-RS API

. Use of the feature concept for custom assembly of a series of bundles

. Bundle and third-party dependent version constraints

. SSH console, customizable extension CLI

. Run-time log level

C.onos can be classified into

. Protocol-aware network-oriented modules that can interact with the network

. Protocol-independent System kernel tracks and provides network status information

. The application uses this information and responds to the kernel with feedback

Each of these items is a critical level in a tiered architecture. This network-oriented module and kernel interacts with the south-to--provider--interface, and the kernel and application interact via the north-to-interface--consumer--interface

。 The south-to-north interface defines a protocol-independent interface that forwards network state information to the kernel through network-oriented modules and network interactions. The north-to-South interface provides an abstraction of network components and attributes for applications, which can be based

In this, the required actions are defined according to the established rules.

D. If the Onos needs to support a new protocol, a new network-oriented module can be defined as a plug-in based on the south-facing interface and loaded into the system.

Onos Architecture-Overview