dmx

DMX capitalizes abstraction capabilities by defining Yang Model of the devices in the Orchestration plane and enabling NetConf in the data plane. The device data model is the XML code of the device configuration and its capabilities. Device model is stored in the orchestrator and upon user intent of configuration change; the changes can be pushed from the Orchestrator, directly to the devices in the form of XML. The device model in the Orchestrator will be exact replica of the device running in data plane. All the configuration changes will be controlled, mapped and deployed to the devices, as per the Orchestration layer. A limited abstraction behavior can also be achieved by the means of Command Line Interface (CLI).
The services include Topology discovery, Node provisioning, Monitoring, end to end service provisioning. Evolve acts as a single visual interface for all network devices and services with data store for both services and devices.
Evolve solution is spread in three layers which are dependent on each other. The three layers are as follows

NBI
This is the orchestration layer or the interface to users or administrators. Users input their intent through the UI provided which is then translated into a service definition and then passed on to further layers for provisioning.

NRI
This layer consists of several modules like data model, inventory, discovery, topology and provisioning manager etc. These individual modules convert the service definition into network definition and pass it on to the further layer. The modules also collect the information from the network devices and pass it on to the NBI for displaying topology , inventory and monitoring.

SBI
This layer consists of plugins, which interact with the network devices. Several plugins can be used based on underlying hardware. These include Netconf, SNMP, CLI and REST. These plugins are responsible to provision the network definition onto the devices and also to collect the required information from the devices.