VoltStack Distributed Infrastructure Management service enables customers to operate their distributed infrastructure like a fleet. Operating as a fleet means that customer declaratively defines his/her intent once, and VoltStack service then takes over the responsibility of ensuring the impacted sites are aligned with the defined intent. Examples of intent include operating system version, network policy, security policy and resource reservation such as CPU, memory.
VoltStack Distributed Infrastructure Management service includes the following features
Fleet configuration capabilities can best be described through an example. Let’s take an example of a user defining a network policy for a specific segment of the fleet. First, the user segments the fleet using labels and virtual sites. A label is made up of two parts, key and value as follows
Once the sites are tagged, operators can define a virtual site using label key-value conditions. This can be visualized as follows using an example of a robot vertical use case.
Next the user defines the network policy for the fleet. VoltStack distributed control plane sends the network policy to the local control plane on each site selected by the virtual site. The local control plane on each site applies the network policy and collect statistics of rules hit per site. Fleet configuration can be visualized as shown in the following figure.
If a new site is added to the fleet, and the user applies the same labels on the site as defined previously, the sites get added to the configured virtual site automatically. The fleet configuration, such as network policy, is automatically applied to the new sites added to the virtual site, reducing the burden on operation teams and eliminating human errors.
Upgrading a single site’s operating system was described in earlier section. Fleet configuration capability enables a user to upgrade the operating system across the entire fleet (or segment of the fleet). First, the user defines the intent of upgrading the operating system from version 1 to version 2. Next, the user defines a deployment strategy across the fleet, such as a rolling update or A/B. A rolling update means that the operating system of every site in the fleet (or segment of the fleet) is upgraded sequentially. An A/B deployment strategy means the user wishes to test the upgrade on a set of “A” sites (e.g., dev sites) and compare the health with “B” sites (e.g., prod sites) that aren’t upgraded. Users can get an aggregated view of the upgrade status of the fleet in the virtual site dashboard.
VoltStack Distributed Infrastructure Management service provides the ability to provision each customer site in zero-touch fashion. The benefit to customers, especially on the edge, is an accelerated new service rollout, without requiring technically skilled personnel to deploy and provision new sites. The zero-touch provisioning process is similar across private/public cloud and edge environments as described next.
Installing Volterra software on Customer Site
The hardware, with Volterra software installed, is then shipped from manufacturer or system integrator directly to the customer’s location, such as private data centers, retail stores, factory sites or charging stations.
At the customer site, unskilled personnel has to simply plug-in the hardware and as soon as Volterra node software boots up, it calls home to the centralized control and management plane.
Installing Volterra Software on Customer Site:
The following concepts are used by Distributed Infrastructure Management features. Click on each one to learn more:
The following How-to guides are examples of using Distributed Infrastructure Management features: