Virtual Standard with Dedicated Storage Installation¶
Overview¶
The Standard with Dedicated Storage deployment option is a standard installation with independent controller, worker, and storage nodes.
A Standard with Dedicated Storage configuration provides the following benefits:
A pool of up to 200 worker nodes
A 2x node high availability (HA) controller cluster with HA services running across the controller nodes in either active/active or active/standby mode
A storage back end solution using a two-to-9x node HA CEPH storage cluster that supports a replication factor of two or three
Up to four groups of 2x storage nodes, or up to three groups of 3x storage nodes
Note
If you are behind a corporate firewall or proxy, you need to set proxy settings. Refer to Docker Proxy Configuration for details.
Figure 1: Standard with Dedicated 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.
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.
