The WP3 engineering team announces that the first release (v1.0) of the SmartenIT prototype has been successfully released.

The first release of the SmartenIT software implements the DTM mechanism components, in 2 architecture entities: SBox and SDN Controller. SBox includes the following components: The QoS Analyzer retrieves the required SNMP measurements from the network entities, the Economic Analyzer calculates the reference vector based on links’ costs and the Network Traffic Manager calculates the compensation vector and also coordinates the interaction with the other entities (remote SBox, local SDN Controller). The inter-SBox Communication Service is responsible for sending and receiving the calculated reference and compensation vector to/from other SBoxes. The SBox-SDN executes the same functionality towards the local SDN controller, and finally, UI and DB provide the necessary interfaces to save and access required configuration. The SDN controller is built on top of Floodlight controller source code to implement DTM functionality, which translates received compensation and reference vectors into flow rules. It also exposes interfaces towards the SBox to receive these vectors and additional configuration parameters.

The deployment diagram of the first release of the SmartenIT software is presented in the figure below. The diagram presents the devices, processes and artifacts used, to deploy an instantiation of the DTM mechanism.

More specifically, the SBox server is an x86 server with Ubuntu 14.04 installed, and requires the installation of Java and the Jetty web server, in which the sbox.war artifact is deployed, exposing an HTTP/HTTPS web interface, accessible by any web browser from the administrator’s PC. In addition, the main.jar is the main executable of the SBox, including all components implementing DTM mechanism’s functionalities. The Sqlite is also used as the SBox’s database.

The SDN Controller also requires an x86 server, with Ubuntu 14.04 as its operating system, requiring Java to be installed. The floodlight.jar executes all the Floodlight SDN Controller’s processes, extended with SmartenIT functionalities, and the Interfaces component, which provides the SBox-SDN communication over HTTP.

Finally, the DTM mechanism requires also a network device, which is Openflow-compatible, and also supports SNMP. QoS Analyzer of SBox retrieves SNMP measurements from the latter interface, while the network device also interacts with the exposed Floodlight SDN Controller’s interface using the OpenFlow protocol.

The source code and release artifacts are currently available internally to consortium partners, but will be published as open-source, as soon as the system testing, performed under the scope of WP4, will be completed.