Service
Replace an end-of-life network controller in planned stages, with the network in service
We move networks off an SDN controller or orchestrator that is losing support, such as Tungsten Fabric or Contrail, onto a target chosen to what you use it for. Old and new run side by side while workloads move in waves. Our engineers have built Tungsten Fabric integrations for OpenStack, OpenShift and SmartNICs, and a custom ONOS control plane in production.
Our controller engineering, measured
What changes for your organization
- Today
A controller with no future
The controller the network depends on gets no new releases, fixes or security patches, and every month on it adds risk.
With a planned migrationA supported foundation
The network runs on a controller or stack with an active roadmap, patches and people who know it.
- Today
A move that looks all-or-nothing
Overlays, policies and every workload hang on one controller, so replacing it reads as one risky cut-over.
With a planned migrationA move in planned stages
Old and new controllers run side by side, and workloads move in waves you schedule, with the network in service.
- Today
Features with no obvious successor
Service chaining, multi-tenancy, analytics and integrations with OpenStack or Kubernetes rarely map one to one onto a single new product.
With a planned migrationEvery function accounted for
Each function you use has a home in the target, from an open-source stack, a commercial product or an extension we build.
- Today
Know-how that has thinned out
The people who built the SDN layer have moved on, and the community that supported it has gone quiet.
With a planned migrationA team that owns the result
The target is documented and handed over, and your engineers run it with our support for as long as you want it.
- Today
A decision under time pressure
The replacement gets picked from datasheets, late in the support window, when there is little time left to test it.
With a planned migrationA choice on tested results
Candidate targets are tested in a lab on your topology and workloads before you commit.
What we deliver
How it runs
The order stays the same whatever the source and target; the scope scales with the estate and the functions you use.
Discovery
What the controller does in your network today, the target architecture, and a migration plan with its waves.
Proof of concept
The shortlisted target proved in a lab on your topology, with the extensions it needs confirmed and tested.
Build and integration
The target built as code, integrated with OpenStack, Kubernetes or OpenShift, and the missing functions developed.
Coexistence
Old and new controllers run side by side under one management point, with policies carried across.
Migration
Workloads and compute nodes moved in waves, each validated by automated tests before the next begins.
Decommission and support
The old controller retired, your team trained on the new one, and our support for as long as you want it.
The target fits what you use the controller for
Often no single product covers every function the old controller had. The discovery maps each function to one of these.
An open-source stack
Open-source SDN components, such as ONOS or OpenStack Neutron with ML2 drivers, combined to cover your functions.
A commercial controller
A supported product, when vendor support and a roadmap lead the decision.
Kubernetes-native networking
CNI plugins and operators, when the workloads have moved or are moving to Kubernetes and OpenShift.
Extended in code
A target of any kind, with the functions it lacks built by us: adapters, forwarding apps, plugins and drivers.
Proof
The engineering a controller migration rests on, from our projects: integrations, coexistence, custom control planes and test labs.
- Integrating Tungsten Fabric, OVS and SR-IOV compute nodes through an OpenStack ML2 mechanismOVS, SR-IOV and Tungsten Fabric vRouter workloads side by side under one management point, and OVS computes live migrated to vRouter.
- Controlling a heterogeneous data plane with the ONOS SDN controllerA custom ONOS control plane across legacy fabric devices and new hardware, with the missing adapters built and the result in production.
- Integrating the Tungsten Fabric SDN controller with Red Hat OpenShiftTungsten Fabric installed with OpenShift as a core networking component through a Kubernetes Operator, released as open source.
- Creating an NFV telco cloud based on OpenStack and Tungsten FabricA multi-region OpenStack and Tungsten Fabric lab with one-click deployment, automated tests and a comparison of the platforms on the market.
