Professional Documents
Culture Documents
https://wiki.onosproject.org/display/ONOS/Overview+of+ONOS+architecture
https://wiki.onosproject.org/display/ONOS/Overview+of+ONOS+architecture
Primary services:
Packet Subsystem
Host Subsystem - Manages the inventory of end-station hosts and their locations on the network.
PathService - Computes/finds paths between infrastructure devices or between end-station hosts using the
most recent topology graph snapshot.
FlowRule Subsystem - Manages inventory of the match/action flow rules installed on infrastructure devices and
provides flow metrics.
Packet Subsystem - Allows applications to listen for data packets received from network devices and to emit
data packets out onto the network via one or more network devices.
Provider: responsible for interacting with the network environment using various control and
configuration protocols, and supplying service-specific sensory data to the core.
interface with the network via protocol-specific libraries
interface with the core via the ProviderService
Manager: mediator between the providers (and the network) and the applications
Service interface: applications or other core components learn about a particular aspect of the
network state
AdminService interface: handles administrative commands towards the network state or the system
ProviderRegistry interface: Providers can register with the manager
ProviderService interface: registered Providers can send and receive information to and from the
manager
Listener: Applications consume and manipulate information aggregated by the managers via the
AdminService and Service interfaces.
https://wiki.onosproject.org/display/ONOS/Overview+of+ONOS+architecture
Interfaces
Southbound (provider) API: network-facing modules interact
with the core
abstraction: protocol-neutral means to relay network state
information to the core
Interfaces
Northbound (consumer) API: the core interacts with the
applications
abstractions that describe network operation components
application logic expressed as a policy instead of mechanism
SDN seminar 2017, Systems Group 17
NORTHBOUND INTERFACE
Intent
network-centric abstraction for programming data-plane in
topology-dependent manner
Flow Objective
device-centric abstraction for programming data-plane flows in
table pipeline
Flow objective:
supported by the Flow Objective service
focus on how traffic should be handled by a device (switch)
rather than prescribing how the processing pipeline is built
abstracts device specific implementation of the data plane
drivers interpret flow objectives and map them to the tables
pipeline, i.e., install flows accordingly
https://wiki.onosproject.org/display/ONOS/Overview+of+ONOS+architecture
https://wiki.onosproject.org/display/ONOS/Cluster+Coordination
Consistency schemes
eventually consistent
strongly consistent
Accuracy:
https://wiki.onosproject.org/display/ONOS/Network+Topology+State
The master instance sends out topology events and their logical
timestamps
Other instances can detect changes in the topology they did know
about.
https://wiki.onosproject.org/display/ONOS/Network+Topology+State