FRINX Machine enables customers to create and run infrastructure workflows, build a network inventory and control its elements.
FRINX Machine is based on open source components and enables infrastructure engineers to manage intent, implement changes and obtain operational data from their heterogenous networks and clouds. FRINX Machine uses Netflix’s Conductor for workflows and micro service orchestration, OpenDaylight with UniConfig for network control and Elasticsearch for inventory functions
Network wide transactions
FRINX UniConfig provides the ability to store intent and operational data from services and devices, it enables to commit intent to the network, syncs from the network so that the latest device state is reflected in the controller, compares intended state and operational state and provides device and network wide transactions.
Open-source device library
The FRINX OpenDaylight Distribution with UniConfig provides a common network API across physical and virtual devices from different vendors. It leverages an open source device library that offers connectivity to a multitude of networking devices and VNFs.
Service and device models
In addition, it provides service modules that translate between IETF’s L3VPN and L2VPN service models and device configurations.
Also, FRINX Machine includes workflow orchestration capabilities that allow users to combine multiple tasks into a workflow. We package a number of workflows written in Python out of the box and users can create their own customized workflows in their programming language of choice. In addition, we use Elasticsearch and Kibana as our persistence layer for inventory data.
FRINX MACHINE CONTAINER SETUP
FRINX Machine consists of multiple containers that are orchestrated to run as a solution. FRINX Machine can be cloned from Github and installed and started within a few minutes. FRINX Machine runs in a VM on your laptop or in a high end machine in the cloud.
FRINX Machine comes pre-packaged with the following workflows
Obtain platform data and store in inventory (native & OpenConfig)
Audit configurations (native & OpenConfig)
Push templates (native & OpenConfig)
Push configuration via UniConfig (commit & rollback)
Get LLDP topology data