Due to a ransomware attack, the wiki was reverted to a July 2022 version. . We apologize for the lack of a more recent valid backup.
The Network Configuration Service provides support for two primary tasks:
- Configuring ONOS applications that provide network services (such as L3 or L2 connectivity, DHCP service, etc.)
- Adding information about devices, links, and device configuration into ONOS's network view
In legacy IP/Ethernet networks, network configuration (for example configuring BGP, IP subnets, or VLANs) usually requires configuring multiple individual devices. With ONOS, the same (or similar) functionality is usually provided by a network application. This application can be configured using the Network Configuration Service.
The Network Configuration Service also provides configuration services to ONOS applications. ONOS applications such as SDN-IP or VPLS accept their own application-specific configuration information from it. Information on application-specific configuration may be found in the individual application sections of Apps and Use Cases.
This section describes how to use the network configuration service to add network elements and links into ONOS’ network view.
Although it is confusingly named, the network configuration service doesn't have much anything to do with configuring ONOS or the network devices themselves. Rather, it is a way of providing topology and inventory information directly to ONOS. This can supplement or completely replace dynamic device and topology discovery. In many cases, such as data center or enterprise networks, the core network devices and topology may be determined by the organization and stored in an inventory database (for example.) The network configuration service makes it possible to write a program that reads the device and topology inventory from a site-specific database and then provides it directly to ONOS, without having to rely on dynamic device and topology discovery. Additionally it may be used to add supplemental information that ONOS does not or cannot discover automatically.
Information on configuring ONOS itself (rather than specifying a topology to ONOSsuch as setting up an ONOS cluster or activating applications), as well as using ONOS to configure network devices, can be found in appropriate sections of this guide.
...
Overview
The network configuration service enables applications and operators to configure the ONOS’ network view, and ONOS’ ONOS network view applications, using a uniform syntax, currently JSON. Examples include:
- Device and device port types and names
- Device location, owner, hardware and software versions
- Whether components are allowed or denied inclusion in the network model
This service doesn’t limit configuration to the network elements that ONOS has knowledge of - configurations can also refer to yet-discovered elements, or those that cannot be discovered by conventional means.
...