Usability. Installation Installation instructions are available and up-to-date in the wiki of the project documentation (▇▇▇▇▇://▇▇▇▇.▇▇▇▇▇▇▇▇▇▇▇▇.▇▇▇). Moreover, an installation guide can be downloaded with the software (▇▇▇▇://▇▇▇.▇▇▇▇▇▇▇▇▇▇▇▇.▇▇▇/software/downloads). Operative documentation A user guide can be downloaded along with the OpenDaylight release. Additionally, a starting guide is also available in the website (▇▇▇▇://▇▇▇.▇▇▇▇▇▇▇▇▇▇▇▇.▇▇▇/resources/getting-started-guide). Development Development documentation A wiki is available for developers at (▇▇▇▇▇://▇▇▇▇.▇▇▇▇▇▇▇▇▇▇▇▇.▇▇▇). It is a live document so it is updated periodically as long as the OpenDaylight project evolves. There is also a set of mailing lists and an IRC channel. Documentation for application development Refer to previous point. Development roadmap Refer to each project section in the OpenDaylight developers’ wiki (▇▇▇▇▇://▇▇▇▇.▇▇▇▇▇▇▇▇▇▇▇▇.▇▇▇/view/GettingStarted:Developer_Main). Also, several sample applications are developed. (▇▇▇▇▇://▇▇▇▇.▇▇▇▇▇▇▇▇▇▇▇▇.▇▇▇/view/OpenDaylight_Controller:Sample_Applications) Toolchain Java 1.7 + Maven + OSGi IDE integration As reported in the wiki of the project (▇▇▇▇▇://▇▇▇▇.▇▇▇▇▇▇▇▇▇▇▇▇.▇▇▇/view/GettingStarted:_Eclipse), at present only the Controller and the OpenFlow plugin projects have been validated to import into Eclipse without compile errors. Deployment System requirements OpenDaylight Controller runs in a JVM. Being a Java application, it can potentially run on any operating system that supports Java. However, for best results a recent Linux distribution and Java 1.7 are recommended. The only information about system requirements for running the controller has been found is more than 1G RAM. Nonetheless, OpenDaylight provides a set of preconfigured VMs with the Hydrogen release of the controller installed. Such VMs contain a GNU/Linux Ubuntu server 13.04 distribution and recommend to allocate 4GB of RAM memory to run the controller. Although the OpenDaylight controller is developed as a normal Java project, it makes heavy use of the Xtend language in some places. While development is possible with bare tools, it is recommend to use Eclipse with the Xtend plugin. Reference target OS Recent Linux distribution is recommended although any OS running a Java 1.7 virtual machine should work. Runtime dependencies Java 1.7 Key features to support COSIGN extensions Supported OpenFlow OpenFlow versions 1.0 and 1.3 are supported. Supported protocols at D- CPI Netconf, SNMP, OVSDB, PCMM/COPS, SNBI, Plugin2OC, LISP, PCEP, BGP Support for additional protocols at D- CPI It is possible to support multiple south-bound plugins in OpenDaylight. Furthermore, OpenDaylight has been designed to allow the extensibility of every part of the architecture including the southbound interface. Integration with Cloud Management Systems OpenDaylight has driver for Neutron ML2 (Modular Layer 2) plugin to enable communication between Neutron and OpenDaylight. On the SDN controller side, OpenDaylight has northbound APIs to interact with Neutron and use OVSDB for southbound configuration of vSwitches on compute nodes. A-CPI language For the A-CPI, OpenDaylight supports the OSGi framework where Java is the developing language, bidirectional REST employing JSON and DOM API employing XML. Available core functions or services The base network service functions available in the OpenDaylight controller are: • Topology Manager • Statistics Manager • Switch Manager • Forwarding Rules Manager • Host Tracker Available applications OpenDOVE and VTN projects extist within the OpenDaylight initiative to implement overlay network virtualization. Moreover, OpenStack integration is enabled through a Neutron API. Available A- CPI methods The associated module directory for the northbound (REST) API reference content is listed below: • Topology REST API • Host Tracker REST API • Flow Programmer REST API • Static Routing REST API • Statistics REST API • Subnets REST API • Switch Manager REST API • User Manager REST API • Container Manager REST API • Connection Manager REST API • Bridge Domain REST API • Neutron ML2 / Network Configuration API Support for ODL-SDNi App entered as an incubation project in May 2014. This project is aimed C2C communicatio n to provide establishment of East-West interface (SDNi communication) between multiple opendaylight controllers. The application will be responsible for sharing and collecting information to/from such federated controllers. Exploitability License Eclipse Public License (EPL-1.0) Membership Not required Potential impact Major industrial partners IBM, CISCO, BROCADE, MICROSOFT, JUNIPER, DELL, HP, ERICSSON, INFINERA, INTEL, ORACLE, … Expert partners from COSIGN consortium IBM, NEXTWORKS, UNIVBRIS, UPC Popularity High. OpenDaylight has a strong support from both the industry and the Open Source community. Usage in research projects LIGHTNESS, ▇▇▇▇▇▇▇, CONTENT Usage in industrial products Brocade has developed a commercial controller built directly from OpenDaylight code: The Brocade Vyatta Controller.
Appears in 2 contracts
Sources: Grant Agreement, Grant Agreement
Usability. Installation Installation instructions are available and up-to-date in the wiki of the project documentation (▇▇▇▇▇://▇▇▇▇.▇▇▇▇▇▇▇▇▇▇▇▇.▇▇▇). Moreover, an installation guide can be downloaded with the software (▇▇▇▇://▇▇▇.▇▇▇▇▇▇▇▇▇▇▇▇.▇▇▇/software/downloads). Operative documentation A user guide can be downloaded along with the OpenDaylight release. Additionally, a starting guide is also available in the website (▇▇▇▇://▇▇▇.▇▇▇▇▇▇▇▇▇▇▇▇.▇▇▇/resources/getting-started-guide). Development Development documentation A wiki is available for developers at (▇▇▇▇▇://▇▇▇▇.▇▇▇▇▇▇▇▇▇▇▇▇.▇▇▇). It is a live document so it is updated periodically as long as the OpenDaylight project evolves. There is also a set of mailing lists and an IRC channel. Documentation for application development Refer to previous point. Development roadmap Refer to each project section in the OpenDaylight developers’ wiki (▇▇▇▇▇://▇▇▇▇.▇▇▇▇▇▇▇▇▇▇▇▇.▇▇▇/view/GettingStarted:Developer_Main). Also, several sample applications are developed. (▇▇▇▇▇://▇▇▇▇.▇▇▇▇▇▇▇▇▇▇▇▇.▇▇▇/view/OpenDaylight_Controller:Sample_Applications) Toolchain Java 1.7 + Maven + OSGi IDE integration As reported in the wiki of the project (▇▇▇▇▇://▇▇▇▇.▇▇▇▇▇▇▇▇▇▇▇▇.▇▇▇/view/GettingStarted:_Eclipse), at present only the Controller and the OpenFlow plugin projects have been validated to import into Eclipse without compile errors. Deployment System requirements OpenDaylight Controller runs in a JVM. Being a Java application, it can potentially run on any operating system that supports Java. However, for best results a recent Linux distribution and Java 1.7 are recommended. The only information about system requirements for running the controller has been found is more than 1G RAM. Nonetheless, OpenDaylight provides a set of preconfigured VMs with the Hydrogen release of the controller installed. Such VMs contain a GNU/Linux Ubuntu server 13.04 distribution and recommend to allocate 4GB of RAM memory to run the controller. Although the OpenDaylight controller is developed as a normal Java project, it makes heavy use of the Xtend language in some places. While development is possible with bare tools, it is recommend to use Eclipse with the Xtend plugin. Reference target OS Recent Linux distribution is recommended although any OS running a Java 1.7 virtual machine should work. Runtime dependencies Java 1.7 Key features to support COSIGN extensions Supported OpenFlow OpenFlow versions 1.0 and 1.3 are supported. Supported protocols at D- CPI Netconf, SNMP, OVSDB, PCMM/COPS, SNBI, Plugin2OC, LISP, PCEP, BGP Support for additional protocols at D- CPI It is possible to support multiple south-bound plugins in OpenDaylight. Furthermore, OpenDaylight has been designed to allow the extensibility of every part of the architecture including the southbound interface. Integration with Cloud Management Systems OpenDaylight has driver for Neutron ML2 (Modular Layer 2) plugin to enable communication between Neutron and OpenDaylight. On the SDN controller side, OpenDaylight has northbound APIs to interact with Neutron and use OVSDB for southbound configuration of vSwitches on compute nodes. A-CPI language For the A-CPI, OpenDaylight supports the OSGi framework where Java is the developing language, bidirectional REST employing JSON and DOM API employing XML. Available core functions or services The base network service functions available in the OpenDaylight controller are: • Topology Manager • Statistics Manager • Switch Manager • Forwarding Rules Manager • Host Tracker Available applications OpenDOVE and VTN projects extist within the OpenDaylight initiative to implement overlay network virtualization. Moreover, OpenStack integration is enabled through a Neutron API. Available A- CPI methods The associated module directory for the northbound (REST) API reference content is listed below: • Topology REST API • Host Tracker REST API • Flow Programmer REST API • Static Routing REST API • Statistics REST API • Subnets REST API • Switch Manager REST API • User Manager REST API • Container Manager REST API • Connection Manager REST API • Bridge Domain REST API • Neutron ML2 / Network Configuration API Support for ODL-SDNi App entered as an incubation project in May 2014. This project is aimed C2C communicatio n to provide establishment of East-West interface (SDNi communication) between multiple opendaylight controllers. The application will be responsible for sharing and collecting information to/from such federated controllers. Exploitability License Eclipse Public License (EPL-1.0) Membership Not required Potential impact Major industrial partners IBM, CISCO, BROCADE, MICROSOFT, JUNIPER, DELL, HP, ERICSSON, INFINERA, INTEL, ORACLE, … Expert partners from COSIGN consortium IBM, NEXTWORKS, UNIVBRIS, UPC Popularity High. OpenDaylight has a strong support from both the industry and the Open Source community. Usage in research projects LIGHTNESS, ▇▇▇▇▇▇▇, CONTENT Usage in industrial products Brocade has developed a commercial controller built directly from OpenDaylight code: The Brocade Vyatta Controller.
Appears in 1 contract
Sources: Grant Agreement