blob: 501a0efb1eb66f514a40ee73ae516c93e301353a [file] [log] [blame]
Thomas Vachuska4f1a60c2014-10-28 13:39:07 -07001<!--
2 ~ Copyright 2014 Open Networking Laboratory
3 ~
4 ~ Licensed under the Apache License, Version 2.0 (the "License");
5 ~ you may not use this file except in compliance with the License.
6 ~ You may obtain a copy of the License at
7 ~
8 ~
9 ~
10 ~ Unless required by applicable law or agreed to in writing, software
11 ~ distributed under the License is distributed on an "AS IS" BASIS,
12 ~ WITHOUT WARRANTIES OR CONDITIONS OF ANY KIND, either express or implied.
13 ~ See the License for the specific language governing permissions and
14 ~ limitations under the License.
15 -->
tomcfde0622014-09-09 11:02:42 -070016<html>
tom5717f392014-09-13 15:50:43 -070018<p>
19 ONOS architecture is strictly segmented into a <em>protocol-agnostic system
20 core</em> tier and the <em>protocol-aware providers</em> tier as shown in
21 the figure below:<br>
22 <img src="doc-files/onos-tiers.png" alt="ONOS architecture tiers">
tomcfde0622014-09-09 11:02:42 -070024
tom5717f392014-09-13 15:50:43 -070025<p>
26 The <em>ONOS core</em> is responsible for tracking information about the
27 network environment and distributing it to the applications either
28 synchronously via query or asynchronously via listener callbacks. The
29 core is also responsible for persisting select state and synchronizing state
30 among the cluster peers.
tomcfde0622014-09-09 11:02:42 -070032
tom5717f392014-09-13 15:50:43 -070033<p>
34 The <em>protocol-aware providers</em> are responsible for interacting with
35 the network environment using various control and configuration protocols
36 and supplying such sensory data to the core. Some providers may also need to
37 accept control edicts from the core and apply them to the environment
38 using the appropriate protocol-specific means.
42 The following diagram describes a general structure of each ONOS subsystem:
43 <br>
44 <img src="doc-files/onos-subsystem.png" alt="ONOS subsystem structure"><br>
45 For example, the device-subsystem comprises of a core
tombe988312014-09-19 18:38:47 -070046 {@link},
tom5717f392014-09-13 15:50:43 -070047 which exposes a north-bound
48 {@link} through which applications or other core components
49 can learn about the global infrastructure device inventory and through
50 which they can also subscribe for asynchronous {@link}
51 notifications via the {@link} mechanism. A set of
52 administrative actions can be performed via {@link},
53 e.g. setting mastership role, removing a decommissioned device.
tombe988312014-09-19 18:38:47 -070057 On the south-bound side, the core {@link}
tom5717f392014-09-13 15:50:43 -070058 exposes a {@link} through which any number of
59 {@link} entities can register and in turn obtain a
60 {@link}. Device and port information can then be
61 supplied to the core by each provider through the provider service issued
62 to them. When a provider unregisters, its {@link}
63 will be invalidated and can no longer be used for interacting with the
64 core.
68 Within the core, the tasks of indexing, persisting and synchronizing the
69 global device and port state with the cluster peers falls on the
tomc104d282014-09-19 10:57:55 -070070 {@link}.
tom5717f392014-09-13 15:50:43 -070071</p>
74 Similar structure applies to the link subsystem, host subsystem and others.
78 <em>More information to come later...</em>