Page History

...

In legacy IP/Ethernet networks, network and connectivity configuration (for example configuring BGP, IP subnets, VLANs, or VLANsACLs) usually requires configuring multiple individual devices. With ONOS, the same (or similar) equivalent functionality is usually provided by ONOS applications – software packages for a network application. This application particular task or use case – that usually provide services across multiple devices or the entire network. Some ONOS applications (such as reactive forwarding) either require no configuration or operate perfectly well with a default configuration. However, other applications may require additional specific configuration information that cannot be inferred automatically. These applications 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. 

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 The Network Configuration Service also provides the ability to add information into ONOS's network view. This makes it possible to write a program that reads the device and topology inventory, as well as other information, 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, but may require for correct operation.

Information on configuring ONOS itself (such 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 guideof Configuring ONOS.

...

{
    subject key : {                   # element category, e.g. "devices", "links", etc.
        subject : {                   # unique string, e.g. a device ID
            config key 1 : {          # config class of config, e.g. "basic"
                attr1 : value1,       # attribute : value pairs associated with a config
                attr2 : value2,
                ...
            },
            ...
        },
          ...
    },
    ...
}

...