Requirements
Deployment Unit (DU) Requirements
| Deployment | Minimum | Recommended |
|---|---|---|
| Multi Node | Compute: 4 vCPU, Memory: 8GB, Disk: 150GB | Compute: 8vCPU, Memory: 16GB, Disk: 180GB |
| Single Node | Compute: 8 vCPU, Memory: 16 GB, Disk: 150GB | Compute: 12 vCPU, Memory: 16 GB, Disk: 180GB |
Disks
For proper functionality, the Management Plane relies on a performant underlying Kubernetes cluster. To achieve optimal performance, we recommend utilising an SSD (Solid State Drive).
Operating Systems
SMCP is designed to run on the following Operating Systems.
| Operating System | Version |
|---|---|
| CentOS | 7.5, 7.6, 7.7, 7.8, 7.9 |
| RHEL | 8.5, 8.6 |
Networking
Virtual IPs
SMCP uses virtual IPs to access the Management Cluster as well as the DU. We require 2 virtual IPs on the same L2 domain as the nodes in the management cluster.
| VIP | Description | Required | Configuration | |
|---|---|---|---|---|
| VIP 1 | This is the IP where you can access the management DU's UI. | Yes | externalIp and/or externalIpV6 in airctl-config.yaml | |
| VIP 2 | This is used to serve the management cluster's API server. | Optional | masterIp and/or masterIpV6 in clusterSpec.yaml (pointed to by bootstrapCfgPath). For single-master clusters, it is simply the IP of the master node (no VIP). For multi-master, it becomes the VIP |
Proxy
If using a proxy in your environment, edit the /etc/yum/yum.conf file to add the proxy configuration as well as environment variable HTTP_PROXY and HTTPS_PROXY
System Configuration
Passwordless Sudo
Many operations require sudo access (for example, the installation of yum repos, docker etc.). Please ensure your hosts have passwordless sudo enabled.
SSH Keys
SMCP relies on SSH to login to the various nodes of the management cluster, as well as, the user clusters, to install various components and manage them.
Please generate SSH keys and sync them across all nodes of the management cluster as well as all nodes that will run the user's workload clusters.
We recommend generating the keys on one node and then adding the public key to all other hosts in its ~/.ssh/authorized_keys file.
Airctl
Airctl is the CLI based installer for SMCP, and is used to manage the DU and the user nodes. Airctl and its corresponding artifacts needs to be downloaded and installed on one of the nodes of the Management Cluster.
Downloading Artifacts
Platform9 publishes SMCP artifacts as secured HTTP endpoints. These endpoints can be accessed via curl or wget or any other command line utility to download the artifacts.
To downloading these artifacts, contact a Platform9 Support Engineer, Solutions Architect or Sales Team member. They will provide you with the "secret" that can be added to the "_user-agent_" value and the appropriate release version
You can download all artifacts using the following download script:
wget https://raw.githubusercontent.com/platform9/support-locker/master/edge-stack/download.shchmod +x ./download.shOnce you’ve downloaded the script you can then run the script with the following options:
./download.sh <secret-key> <release-version>- secret-key: ask Platform9 Support for this key
- release-version: The latest release version is available on the Platform9 Docs Website: https://platform9.com/docs/PEC/pec-lts2-release
Once all artifacts are downloaded, install them using:
chmod +x ./install.sh./install.sh <release-version>This copies all artifacts under /opt/pf9/airctl.
For airgapped setups, please ensure each node for management cluster has the following Linux packages pre-installed:
curlgzipnet-toolslibcgroup-toolsOnce downloaded, the directory contains a list of .tar or .tar.gz files, an index file, and a simple install.sh file. Visit the Artifacts page to learn more about the downloaded artifacts.