PANTHEON.tech

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

Karaf is usually 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 framework of your choice, not only Karaf.

lighty.io core contains base ODL services and components like: MD-SAL, Controller, YANG Tools.

• north-bound-plugins: RESTCONF, NETCONF
• south-bound-plugins: SNMP, NETCONF, OpenFlow 
• applications like TransportPCE, ONAP’s SDN-C
• the list is growing rapidly …
• etc. (this list keeps expanding)

Yes, it does. In 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 north-bound-plugin RFC8040 compliant implementation
• Client libraries for Java, Python and GO for lighty.io
• This list is growing as well …

This process is very easy, and we have described it on several OpenDaylight application examples.

Yes this is possible. Your application code does not depend on Karaf anyway, and lighty.io provides ODL services in runtime.

So that the deployment of your SDN application into both environments, at the same time, is possible.

Yes, it is. lighty.io provides one core module and several other modules implementing south/north-bound plugins.

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

This is much easier with lighty.io, because all Opendaylight services are available in the JUnit runtime.