lighty.io is a set of OpenDaylight components, adapted to run in a plain Java SE environment.

No, it is not.

The major difference is, that OpenDaylight depends on Karaf – an OSGi runtime environment – to start and operate its components. 

We have removed this dependency in lighty.io and managed to create a new product, which redefines Software-Defined Networking.

However, we are a proud supporter of OpenDaylight and are one of the largest contributors to this project to-date. 

Karaf is used to start OpenDaylight features and components.

lighty.io does this faster with better memory efficiency.

Having Java SE as a runtime, you can use a framework of your choice, not only Karaf.

The lighty.io core contains base OpenDaylight services and components:

• MD-SAL, Controller, YANG Tools
• Northbound plugins: RESTCONF, NETCONF
• Southbound plugins: SNMP, NETCONF, OpenFlow 
• Apps: TransportPCE, ONAP’s SDN-C

Yes, it does. Since the 7.x releases, you can use improved:

• YANG Codecs – library for serialization and deserialization of YANG binding-aware, or YANG normalized nodes from or to JSON and XML
• NETCONF Device Library – enables you to create your own NETCONF devices using your own YANG models
• RESTCONF Northbound plugin, RFC 8040 compliant implementation
• Client libraries for Java, Python and GO for lighty.io

We have prepared several migration scenarios:

• OpenDaylight TransportPCE
• ONAP SDN-C
• Your unique scenario & needs

Yes, this is possible.

lighty.io provides OpenDaylight services in runtime and your application code does not depend on Karaf anyway.

Yes, it is.

lighty.io provides one core module and several other modules implementing Southbound & Northbound plugins.

Your application code can start, stop & restart those modules, as required.

This is much easier with lighty.io, as you can read in our use-case, due to all OpenDaylight services are available in the JUnit runtime.