Required Components
The following components are necessary to fulfill the complete configuration as described in this document.
- Commander 8.0 or later
- Commander API PowerShell libraries
You must have the Commander PowerShell Module for REST installed to initialize the first node. Access to the Commander Legacy API (REST v2) is also required on both nodes in the cluster to test to determine if logins are successful.
To download the Commander PowerShell Module for REST package, you must first log in to Snow Globe.
- Commander Node Quarantine script.
The Commander Node Quarantine script is used to shut down a failed node in the cluster. This is done to ensure that a non-responsive node can’t come back online unexpectedly; it's highly recommended over manual shutdown.
- PowerShell v4 or higher must be available on the Commander application server.
AWS deployments
For an AWS deployment, the following components must also be available/provisioned before the installation of the Commander instances:
- AWS CLI
- AWS Application Load Balancer
The Application Load Balancer will monitor the service status using the advanced Health Check feature.
- IAM policy
- SQL database
The database must be highly available. Configuration of the database as highly available is the responsibility of customers using their preferred solution. This guide assumes that a highly-available RDS database will be used.
vCenter deployments
For a vCenter deployment, the following components must also be available/provisioned before the installation of the Commander instances:
- vSphere PowerCLI installed on the Commander application server
- Load balancer capable of monitoring service status
Your load balancer must be capable of monitoring the service status. This document provides examples for Kemp and F5 load balancers. If you're using a load balancer from a different vendor, consult its documentation on how best to monitor the Commander service status in a manner like the examples provided.
- SQL database
The database must be highly available. However, the configuration of the database as highly available is the responsibility of Snow Software customers using their preferred solution.