An enterprise-ready solution for ONAP SDN-C

ONAP SDN-C: Redefined

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

lighty.io’s source-code was stripped to only what’s needed. A small source-code means less bug occurence. We just made debugging easier.

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

Without Karaf: have removed Karaf dependency in lighty.io and managed to create a new product, which redefines Software-Defined Networking. lighty.io provides OpenDaylight services in runtime and your application code does not depend on Karaf in any way.

Plain Java: We have made lighty.io one of the most lightweight SDN controllers in the world. This makes not only lighty.io‘s but OpenDaylight’s components usable in the world of containers & micro-services.

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

lighty.io features

lighty.io is used as a set of Java libraries, which enables SDN software developers to use OpenDaylight services in JavaSE frameworks. This means a smaller footprint in your system, faster boot time & more versatility.

lighty.io provides a great platform to build SDN-microservice controller applications thanks to its minuscule build size. lighty.io reuses OpenDaylight’s mature components and features like YANG tools, MD-SAL, NETCONF, and clustering.

lighty.io offers the ability to implement features outside of its controller runtime. We call these applications lighty.io client applications.

lighty.io UI component enables you to view the topology angularly – even large topologies with thousands of nodes & links. You can arrange and group nodes with automatic layouts, highlight paths and customize icons.

Thanks to its small distribution size, fast build time and swift startup features you can develop and deploy SDN applications with ease and speed.

lighty.io comes with a controller application Docker image, which includes RESTCONF Northbound and NETCONF Southbound modules

SDN-C containers take more than 300 seconds to initialize, while consuming 1,125 GB of RAM.

PANTHEON.tech made it efficient.

lighty.io SDN-C comparison with a vanilla container

SDN-C Migration → lighty.io

SDN-C is based on Opendaylight. Our goal is to make it more efficient and suitable for micro-service deployments. An ideal situation for lighty.io! We migrated SDN-C from Opendaylight to lighty.io and build our own Docker image for it.

Our SDN-C x lighty.io migration achievements:

  • Execution of directed graphs
  • Less memory usage
  • Faster start-up time

You can read more about the entire SDN-C // lighty.io migration process here.

71% of OpenDaylight Commits – by PANTHEON.tech

It is no secret, that OpenDaylight is more than a passion project for us. We are proud, that our CTO Robert Varga is leading the numbers of individual commits in OpenDaylight.

He has driven the development of several, core OpenDaylight components, such as odlparent, YANG Tools or MD-SAL and continues to passionately work on OpenDaylight to this day.

OpenDaylight Commits to source-code

ONAP SDN-C Migration Demonstration

A migration of OpenDaylight based application into lighty.io can be pretty straightforward. However, sometimes you have to do more steps, in order to execute your application in lighty.io. Especially if your application is using OSGI/Karaf specific code.

In an ideal world, where dependency injection is used properly and code is decomposed in the right way, migrating to lighty.io is just a manner of instantiation of classes/beans. These are originally instantiated by some dependency injection system (Blueprint for example). We have made a video & written demonstration on how to migrate ONAP SDN-C to lighty.io.

That is why we prepared a video demonstration & guide on ONAP SDN-C Migration to lighty.io.