Virtual Standard with Controller Storage Installation R6.0

Overview

The Standard with Controller Storage deployment option provides two high availability (HA) controller nodes and a pool of up to 10 worker nodes.

A Standard with Controller Storage configuration provides the following benefits:

  • A pool of up to 10 worker nodes

  • High availability (HA) services run across the controller nodes in either active/active or active/standby mode

  • A storage back end solution using a two-node CEPH deployment across two controller servers

  • Protection against overall controller and worker node failure, where

    • On overall controller node failure, all controller HA services go active on the remaining healthy controller node

    • On overall worker node failure, virtual machines and containers are recovered on the remaining healthy worker nodes

Note

If you are behind a corporate firewall or proxy, you need to set proxy settings. Refer to Docker Proxy Configuration for details.

Standard with Controller Storage deployment configuration

Figure 1: Standard with Controller Storage deployment configuration

Note

By default, StarlingX uses IPv4. To use StarlingX with IPv6:

  • The entire infrastructure and cluster configuration must be IPv6, with the exception of the PXE boot network.

  • Not all external servers are reachable via IPv6 addresses (for example Docker registries). Depending on your infrastructure, it may be necessary to deploy a NAT64/DNS64 gateway to translate the IPv4 addresses to IPv6.

  • Refer to StarlingX IPv6 Deployment for details on how to deploy a NAT64/DNS64 gateway to use StarlingX with IPv6.

Installation