Before proceeding, be sure to review our architecture overview, and our minimum requirements. We are also more than happy to help you design your ComputeStacks environments. Please contact us to learn more.

• make (installed by default on all linux & mac systems)
• ansible

Once ansible is installed, run:

make roles

Please first check and see if terraform scripts exist for your platform. This is will greatly aid in building your inventory file and ensuring a more successful installation process.

If you used one of our terraform setup scripts (RECOMMENDED) to create your cluster, then you should already have a skeleton inventory.yml file that you can place in this directory. Otherwise, cp inventory.yml.sample inventory.yml.

Ensure you fill out all the variables and ensure everything is correct. To see all available settings, check each role and look at their defaults/main.yml file.

Various parts of this ansible package will require the domains defined in your inventory.yml file to be correctly setup. Please configure those domains and ensure the changes have been propagated before proceeding.

a.dev.cmptstks.net. IN A %{floating_ip}
metrics.dev.cmptstks.net. IN A %{PUBLIC IP OF METRICS SERVER}
*.a.dev.cmptstks.net. IN CNAME a.dev.cmptstks.net.
portal.dev.cmptstks.net. IN A %{controller ip address}
cr.dev.cmptstks.net. IN CNAME portal.dev.cmptstks.net.

Ensure all hostnames are configured properly on each node. Our system expects the hostnames on nodes to be 1 lowercase word (dashes or underscores are ok), no special characters or spaces. They should not be FQDN or have the dot notation.

hostname node101 && echo "node101" > /etc/hostname && echo "127.0.0.1 node101" >> /etc/hosts

apt-get update
apt-get -y install openssl \
                   ca-certificates \
                   linux-headers-amd64 \
                   python3 \
                   python3-pip \
                   python3-openssl \
                   python3-apt \
                   python3-setuptools \
                   python3-wheel

If you're using a setting other than the default 1500, please add the following to the main vars: section of your inventory.yml file:

container_network_mtu: 1400 # Set the desired MTU for containers to use

Due to an ongoing issue with the container network platform we use, IPv6 is currently not supported on our container nodes. We're able to bring ipv6 connectivity by either using a dedicated load balancer on a separate virtual machine, or by configuring the controller to proxy ipv6 traffic.

For the time being, our installer will disable ipv6 directly on the node. However, we recommend also cleaning out the /etc/sysconfig/network-scripts/ifcfg-* files to remove any ipv6 specific settings, and setting IPV6INIT=no.

We recommend performing this step prior to running this ansible package.

make bootstrap

The last step in this script will reboot servers to finalize configuration.

After running and allowing the servers to reboot, you can perform some basic validation by running:

make validate

To add nodes to existing Availability Zone, simply add the new nodes to the same inventory file you used to deploy the initial cluster.

Please note that you will need to ensure the number of nodes you're deploying will keep the etcd cluster in quorum. As per the etcd documentation, this should be (n/2)+1 nodes. So 3, 5, 7, or 9 nodes per availability zone.

Now you may run the ansible package with:

make add-node

To add a new region or availability zone, make a copy of your previous inventory.yml file and make the following changes:

1. Change region_name and/or, availability_zone_name
2. Replace all nodes with your new nodes
3. (optional) Change metrics / backup servers. You can re-use the existing ones if you wish.

Re-run the bootstrap command:

make bootstrap

brew install ansible

python -m pip install --user ansible
echo 'export PATH="$PATH:$HOME/.local/bin"' >> ~/.bashrc

In order to allow swap limitations set on containers, you need to perform the following on each node:

1. Modify the file /etc/default/grub
2. Add cgroup_enable=memory swapaccount=1 to the existing GRUB_CMDLINE_LINUX_DEFAULT setting
3. run update-grub
4. reboot

Note: This can add about 1% of overhead.

How to Resolve set-hostname: current hostname was changed outside NetworkManager: '<hostname>' in logs:

Edit /etc/NetworkManager/NetworkManager.conf and add hostname-mode=none to the [main] block, and reboot the server.

Example:

[main]
#plugins=ifcfg-rh,ibft
hostname-mode=none