Orchestrator

Purpose

The orchestrator wraps around the lower-level hypervisor and container orchestration platform running on our boxes to provide an API interface that makes common industrial workflows simple for the user. This API is called by the frontend.

The orchestrator is composed of 2 sections: the configuration management engine orchestrator, and the "clone" orchestrator.

How It Works

Configuration Management Engine Orchestrator

This orchestrator is currently used for the configuration layer, but can be used for containerized applications as well. It consists of an operator for AMD Secure Encrypted Virtualization (SEV) management, as well as an Axilon-developed library to make spinning up the configuration management engine as simple as possible.

"Clone" Orchestrator

The VM manager is used for spinning up and managing clone VMs. It consists of a system to allow for provisioning of resources for VMs, as well as handling network bridging and port forwarding for those VMs. It also includes an integration with the software running on the VMs to allow for passing information to and from the VMs (e.g. the secrets they need to identify themselves uniquely to the Configuration Management Engine).