open platform for customizing and automating networks of any size and scale. The OpenDaylight Project arose out of the SDN movement, with a clear focus on network programmability. It was designed from the outset as a foundation for commercial solutions that address a variety of use cases in existing network environments. ODL is driven by a global, collaborative community of vendor and user organizations that continuously adapts to support the industry's broadest set of SDN and NFV use cases. With over 1000 developers, 50 member organizations and supporting approximately 1 billion subscribers around the world, OpenDaylight is quickly evolving integrated toolchains for leading use cases. Ref: Platform Overview - OpenDaylight
by the Linux Foundation Eclipse Public License 15 founding companies provided software and developers 1000+ contributors 2.5M+ lines of code Mostly Java
OpenDaylight platform is the Model-Driven Service Abstraction Layer (MD-SAL). In OpenDaylight, underlying network devices and network applications are all represented as objects, or models, whose interactions are processed within the SAL. The SAL is a data exchange and adaptation mechanism between YANG models representing network devices and applications. The YANG models provide generalized descriptions of a device or application's capabilities without requiring either to know the speci c implementation details of the other. Within the SAL, models are simply de ned by their respective roles in a given interaction. A "producer" model implements an API and provides the API's data; a "consumer" model uses the API and consumes the API's data. While 'northbound' and 'southbound' provide a network engineer's view of the SAL, 'consumer' and 'producer' are more accurate descriptions of interactions within the SAL. For example, protocol plugin and its associated model can either be a producer of information about the underlying network, or a consumer of application instructions it receives via the SAL.
support for the broadest set of protocols in any SDN platform - OpenFlow, OVSDB, NETCONF, BGP and many more - that improve programmability of modern networks and solve a range of user needs. Southbound protocols and control plane services, anchored by the MD-SAL, can be individually selected or written, and packaged together according to the requirements of a given use case. A controller package is built around four key components (odlparent, controller, MD-SAL and yangtools). To this, the solution developer adds a relevant group of southbound protocols plugins, most or all of the standard control plane functions, and some select number of embedded and external controller applications, managed by policy. Each of these components is isolated as a Karaf feature, to ensure that new work doesn't interfere with mature, tested code. OpenDaylight uses OSGi (Equinox) and Maven to build a package that manages these Karaf features and their interactions.
platform is designed to allow downstream users and solution providers maximum exibility in building a controller to t their needs. This modular framework allows developers and users to: Only install the protocols and services they need Combine multiple services and protocols to solve more complex problems as needs arise Incrementally and collaboratively evolve the capabilities of the open source platform Quickly develop custom, value-added features for highly specialized use cases, leveraging a common platform shared across the industry
the shell now... 100% [========================================================================] Karaf started in 2s. Bundle stats: 52 active, 53 total ________ ________ .__ .__ .__ __ \_____ \ ______ ____ ____ \______ \ _____ ___.__.| | |__| ____ | |___/ |_ / | \\____ \_/ __ \ / \ | | \\__ \< | || | | |/ ___\| | \ __\ / | \ |_> > ___/| | \| ` \/ __ \\___ || |_| / /_/ > Y \ | \_______ / __/ \___ >___| /_______ (____ / ____||____/__\___ /|___| /__| \/|__| \/ \/ \/ \/\/ /_____/ \/ Hit '<tab>' for a list of available commands and '[cmd] --help' for help on a specific command. Hit '<ctrl-d>' or type 'system:shutdown' or 'logout' to shutdown OpenDaylight. opendaylight-user@root>feature feature feature:export-bundles feature:info feat feature:repo-add feature:repo-list feature:repo-refresh feat feature:requirement-remove feature:start feature:stop feat opendaylight-user@root>feature:list --installed Name | Version | Required | State | Repository | Description ---------------------------------------------------------------------------------------------- aries-proxy | 4.0.10 | | Started | standard-4.0.10 | Aries Proxy aries-blueprint | 4.0.10 | | Started | standard-4.0.10 | Aries Blueprint feature | 4.0.10 | | Started | standard-4.0.10 | Features Support shell | 4.0.10 | | Started | standard-4.0.10 | Karaf Shell shell-compat | 4.0.10 | | Started | standard-4.0.10 | Karaf Shell Compatibility deployer | 4.0.10 | | Started | standard-4.0.10 | Karaf Deployer bundle | 4.0.10 | | Started | standard-4.0.10 | Provide Bundle support config | 4.0.10 | | Started | standard-4.0.10 | Provide OSGi ConfigAdmin su diagnostic | 4.0.10 | | Started | standard-4.0.10 | Provide Diagnostic support instance | 4.0.10 | | Started | standard-4.0.10 | Provide Instance support jaas | 4.0.10 | | Started | standard-4.0.10 | Provide JAAS support log | 4.0.10 | | Started | standard-4.0.10 | Provide Log support package | 4.0.10 | | Started | standard-4.0.10 | Package commands and mbeans service | 4.0.10 | | Started | standard-4.0.10 | Provide Service support system | 4.0.10 | | Started | standard-4.0.10 | Provide System support kar | 4.0.10 | | Started | standard-4.0.10 | Provide KAR (KARaf archive) ssh | 4.0.10 | | Started | standard-4.0.10 | Provide a SSHd server on Ka 16 / 56 Run Karaf
| grep dlux odl-dluxapps-yangui | 0.6.1 | x | Started | odl- odl-dluxapps-yangvisualizer | 0.6.1 | x | Started | odl- odl-dluxapps-yangman | 0.6.1 | x | Started | odl- odl-dluxapps-topology | 0.6.1 | x | Started | odl- odl-dluxapps-nodes | 0.6.1 | x | Started | odl- odl-dlux-core | 0.6.1 | x | Started | odl- opendaylight-user@root>feature:list | grep dlux features-dluxapps | 0.6.1 | | Uninstalled | features-dlux | 0.6.1 | | Uninstalled | odl-dluxapps-applications | 0.6.1 | | Uninstalled | odl-dluxapps-yangui | 0.6.1 | x | Started | odl-dluxapps-yangvisualizer | 0.6.1 | x | Started | odl-unimgr-dlux | 0.3.1 | | Uninstalled | odl-dluxapps-yangman | 0.6.1 | x | Started | odl-dluxapps-topology | 0.6.1 | x | Started | odl-dluxapps-nodes | 0.6.1 | x | Started | odl-dluxapps-yangutils | 0.6.1 | | Uninstalled | odl-dlux-core | 0.6.1 | x | Started | opendaylight-user@root>feature:info odl-dluxapps-applications Feature odl-dluxapps-applications 0.6.1 Description: ODL :: dluxapps :: odl-dluxapps-applications Details: OpenDaylight is leading the transformation to Open Software Defined Networking (SDN). For mo Feature has no configuration Feature has no configuration files Feature depends on: odl-dluxapps-nodes 0.6.1 odl-dluxapps-topology 0.6.1 odl-dluxapps-yangui 0.6.1 odl-dluxapps-yangvisualizer 0.6.1 odl-dluxapps-yangman 0.6.1 Feature has no bundles. Feature has no conditionals. 17 / 56 Install Features
guration and state in the datastore. The REST interface has direct access to the controller datastore. RFC 8040 Restful API for YANG data models and provides lighter- weight interface to network datastores leveraging well known combination of REST and JSON. Con guration data and state data exposed as resources HTTP instead of SSH for transport; JSON in addition to XML for data encoding Ref: OpenDaylight as a Platform for Network Programmability
create/read/update/delete (POST, GET, PUT, DELETE) application configurati http://<IP>:8181/restconf/restconf/config/* # This is where applications write state and users read it (GET). http://<IP>:8181/restconf/restconf/operational/* # Most popular databases are topology and inventory: GET http://<IP>:8181/restconf/operational/network-topology:network-topology/ GET http://<IP>:8181/restconf/operational/opendaylight-inventory:nodes/ # Access via curl curl --user "admin":"admin" -H "Accept: application/json" -H "Content-type: application/json" -X # Header: # Authorization (basic): admin/admin # Accept (answer body): application/xml or application/json # Content-Type (request body): application/xml or application/json
others. All rights reserved. * * This program and the accompanying materials are made available under the * terms of the Eclipse Public License v1.0 which accompanies this distribution, * and is available at http://www.eclipse.org/legal/epl-v10.html */ package org.opendaylight.hallo.impl; import java.util.concurrent.Future; import org.opendaylight.yang.gen.v1.urn.opendaylight.params.xml.ns.yang.hallo.rev150105.HalloS import org.opendaylight.yang.gen.v1.urn.opendaylight.params.xml.ns.yang.hallo.rev150105.HalloW import org.opendaylight.yang.gen.v1.urn.opendaylight.params.xml.ns.yang.hallo.rev150105.HalloW import org.opendaylight.yang.gen.v1.urn.opendaylight.params.xml.ns.yang.hallo.rev150105.HalloW import org.opendaylight.yangtools.yang.common.RpcResult; import org.opendaylight.yangtools.yang.common.RpcResultBuilder; public class HalloWorldImpl implements HalloService { @Override public Future<RpcResult<HalloWorldOutput>> halloWorld(HalloWorldInput input) { HalloWorldOutputBuilder halloBuilder = new HalloWorldOutputBuilder(); halloBuilder.setGreeting("Hallo " + input.getName()); return RpcResultBuilder.success(halloBuilder.build()).buildFuture(); } } ~/devfolder/hallo$ ll impl/src/main/java/org/opendaylight/hallo/impl/ total 16 drwxrwxr-x 2 em em 4096 Feb 5 05:20 ./ drwxrwxr-x 3 em em 4096 Feb 5 03:02 ../ -rw-rw-r-- 1 em em 1036 Feb 5 03:02 HalloProvider.java -rw-rw-r-- 1 em em 1302 Feb 5 05:20 HalloWorldImpl.java 45 / 56 HalloService
smarttab sw=4 tabstop=4: --> <!-- Copyright (c) 2017 hallo inc. and others. All rights reserved. This program and the accompanying materials are made available under the terms of the Eclipse Public License v1.0 which accompanies this distribution, and is available at http://www.eclipse.org/legal/epl-v10.html --> <blueprint xmlns="http://www.osgi.org/xmlns/blueprint/v1.0.0" xmlns:odl="http://opendaylight.org/xmlns/blueprint/v1.0.0" odl:use-default-for-reference-types="true"> <reference id="dataBroker" interface="org.opendaylight.controller.md.sal.binding.api.DataBroker" odl:type="default" /> <reference id="rpcRegistry" interface="org.opendaylight.controller.sal.binding.api.RpcProviderRegistry"/> <bean id="provider" class="org.opendaylight.hallo.impl.HalloProvider" init-method="init" destroy-method="close"> <argument ref="dataBroker" /> <argument ref="rpcRegistry" /> </bean> </blueprint> 46 / 56 RPC Registry Reference
and others. All rights reserved. * * This program and the accompanying materials are made available under the * terms of the Eclipse Public License v1.0 which accompanies this distribution, * and is available at http://www.eclipse.org/legal/epl-v10.html */ package org.opendaylight.hallo.impl; import org.opendaylight.controller.md.sal.binding.api.DataBroker; import org.opendaylight.controller.sal.binding.api.RpcProviderRegistry; import org.opendaylight.controller.sal.binding.api.BindingAwareBroker.RpcRegistration; import org.opendaylight.yang.gen.v1.urn.opendaylight.params.xml.ns.yang.hallo.rev150105.HalloS import org.slf4j.Logger; import org.slf4j.LoggerFactory; public class HalloProvider { private static final Logger LOG = LoggerFactory.getLogger(HalloProvider.class); private final DataBroker dataBroker; private final RpcProviderRegistry rpcProviderRegistry; private RpcRegistration<HalloService> serviceRegistration; public HalloProvider(final DataBroker dataBroker,RpcProviderRegistry rpcProviderRegistry) this.dataBroker = dataBroker; this.rpcProviderRegistry = rpcProviderRegistry; } /** * Method called when the blueprint container is created. */ public void init() { serviceRegistration = rpcProviderRegistry.addRpcImplementation(HalloService.class, new LOG.info("HalloProvider Session Initiated"); } /** * Method called when the blueprint container is destroyed. */ public void close() { 47 / 56 HalloProvider
SDN Controller with the Mininet Network Emulator 3. ODL_Summit_OpenFlow_Tutorial 4. OpenDaylight User Guide - OpenDaylight Documentation Nitrogen documentation 5. Getting Started Guide - OpenDaylight Documentation Nitrogen documentation 6. OpenDaylight Application Developer's tutorial | SDN Hub 7. CiscoDevNet/yangman: YANGMAN o ers dynamically generated UI forms and native JSON representation based on RESTCONF APIs 8. OpenDaylight as a Platform for Network Programmability 9. OpenDaylight Controller:MD-SAL:Startup Project Archetype 10. Developing Apps on the OpenDaylight controller - Nitrogen 11. RFC 8040 - RESTCONF Protocol 55 / 56