Understanding LEAP Workflow Automation


For Service Providers striving to streamline efficiencies and provide unparalleled customer experiences, automating workflows is an important part of network enablement. By breaking down high-level network operations into subtasks and then stitching them together, network operators have the fine-tuned control needed to enable on-demand, customizable services.

Enabling this capability for multi-vendor networks, with the solutions on the market today, is a challenge. There are a limited number of ubiquitous automation tools which can cross domains and devices. With proprietary motivations, the companies which build automation solutions can’t help but be influenced by their install base and future proprietary sales. This fact (along with other benefits) is pushing Service Providers to open source solutions.

With an open source automation solution, reducing the overhead of multiple proprietary tools and systems is what the tool is made to do well. While multi-vendor environments create change governance challenges which can lead to service failures and outages, open source provides ubiquitous control to solve these governance challenges.

Beyond tooling to enable the automation of workflows, it allows teams to spend more time on the actual task and less time on the workflows that support them. Managing the frequent and heavy change requests expected in a digital era will take a flexible and scalable approach.

Lumina has the solution to managing workflows with these complicated conditions.

Lumina Extension & Adaptability Platform (LEAP) is an open source framework which enables assured automation configuration of heterogeneous network elements and services. Across domains and vendor elements, LEAP automates the provisioning process while streaming and normalizing telemetry data from an end-to-end network.

LEAP enables automation of workflows by introducing three processes:

    1. User-defined workflows
    2. OpenConfig-based network device models
    3. YANG-driven vendor models applied to network devices

Extending the benefits of Lumina’s OpenDaylight-based controller to a legacy and new resources, LEAP is built on a microservices architecture to enable ease of extensibility. A pure-play open source solution, the platform is based on the Camunda workflow engine. Proven to be highly scalable, this open source engine integrates well with LEAP’s microservices architecture and eases automation of workflows across an end-to-end network.


How does it work?

The workflow engine enables multi-vendor networks with abstractions for complex workflows. Without common standard models in legacy networks, device models have dissimilar ways to configure services which means the workflow engine creates device abstractions that are device-specific. The engine automates through this complexity so application developers only need to know about workflow logic.The engine also provides streamlined pre/post-checking and error handling. These capabilities neutralize the nuances of configuration by vendor, platform, and version.

You can create your own workflow script tasks using your preferred language (Python, Groovy, Javascript) and interfaces. Or, you can use the workflows that ship out of the box with LEAP. Workflows are defined using a Business Process Model and Notation (BPMN) - XML format, used to wire a set of tasks together.

Tasks are either control tasks (fork, conditional, etc.) and are executed on a remote machine. You can execute and monitor workflows via the Lumina SDN Controller’s Restconf UI. In the UI, a defined set of Workflow Management APIs provide managed workflows. This enables users to mount and view device statuses and provides access to device operations like read, edit, commit configurations and sync it from the network.


Understanding LEAP Workflow Automation


For a demonstration on how to automate workflows with open source, please contact us.


Watch the LEAP demo:


Learn more about LEAP and our SDN Controller with these additional resources: