SDN Made Easy
lighty.io is a toolkit, made for Software-Defined Networking programmers and solution architects.
It provides a streamlined, effective & versatile experience for you and your new SDN Controller.
Software-defined Networking made easy
Lighty Kit is a toolkit made for Software-Defined Networking application programmers and solution architects, mainly for building Software-Defined Networking controllers. It utilizes main OpenDaylight components, which are available as a set of libraries. The final SDN application architecture is decided by the user. Providing SDN backend components and client bindings for Java, Python and Go, is the easiest way to enter the world of micro-services and SDN. Lighty Kit comes with network device simulators which enable quick integration testing.
FAQ
lighty.io is a set of OpenDaylight components, adapted to run in a plain Java SE environment.
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 ODL 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:
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 an read in our use-case, due to all Opendaylight services are available in the JUnit runtime.
Lighty kit components
SDN Backend
FOR CONTROLLER ASSEMBLY
Client Components
FOR EASY INTEGRATION
Sample Projects
FOR DEVELOPMENT JUMPSTART
Device Simulators
FOR BETTER INTEGRATION TESTING
Docker Images
FOR FASTER DEPLOYMENTS
Visibility Components
FOR FASTER VISUALIZATIONS