Cluster Configuration

The Cluster Configuration page outlines the settings provided when deploying the cluster.

Go to Cluster Settings > Cluster Configuration to view the cluster deployment settings.

The following information is provided:

Deployment Type

Select the desired deployment type. Universal Compute Platform supports the following deployment types:

Select the deployment type. Valid values are:
  • ExtremeCloud Edge - Managed OrchestrationExtremeCloud IQ as a distributed cloud application. Supported only on 4120C-1.
  • ExtremeCloud Edge - Self-Orchestration—A variety of on-premise controller applications.

Select Next.

Cluster Node Information

Universal Compute Platform supports a stand-alone mode and a full-cluster mode. Stand-alone mode requires only one defined node, but a cluster can be deployed using multiples of three (for example, three, six, or nine nodes) depending on your resource requirements.

Configure only one node for stand-alone mode or configure a full cluster of nodes (using multiples of three).
Note

Note

When using an ExtremeCloud™ IQ engine, you must configure a cluster of three or more nodes in multiples of three (for example, three, six, or nine nodes). ExtremeCloud IQ is not supported in stand-alone mode, requires a cluster, and does not support engine types other than ExtremeCloud IQ.
  1. Provide the ICC IP Address for each node in the cluster.
  2. Select Next.
When the Deployment Type is ExtremeCloud Edge - Self-Orchestration, you have a variety of engine options to choose from, including the following:
  • ExtremeWireless WiNG™ Controller
  • Extreme Tunnel Concentrator
  • ExtremeCloud™ IQ Controller

Pod Network Configuration

Pods are groups of containers that share networking and storage resources from the same node.
  1. Provide the following Pod Network configuration settings:
    • Pod Network IP Address
    • Pod Network CIDR
    • Service Network IP Address
    • Service Network CIDR
  2. Select Create Cluster.

    The cluster is created.

    If a cluster previously existed, the cluster connections are reset. Then, you must reinstall the engines for each node in the cluster.