It is essential that the systems in your environment where you will install Anaconda Enterprise meet all of the requirements outlined here. While the installer itself some pre-flight checks, it does not verify all of our known requirements.
We have created this pre-install checklist to help you verify that you have accounted for everything before you begin, and ensure your installation is successful. Consider printing out a copy and physically checking off items as you go.
We have created an additional pre-flight script that can automatically verify many of these requirements. While not comprehensive, it will help you complete this checklist more easily. Follow these instructions to install and run the script.
All nodes in the cluster meet the minimum or recommended specifications for CPU, RAM and disk space.
A nodes in the cluster meet the minimum IOPS required for reliable performance.
There is 50GB of free space available in the
/tmpdirectory (or another temporary directory to be used during installation) on each node in the cluster.
All cluster nodes are operating the same version of the OS, and that the OS version is supported by Anaconda Enterprise.
The Network Time Protocol (NTP) is being used to synchronize computer system clocks, and the clock of each node in the cluster is in sync with the others. (Instructions for using NTP are provided here.)
The account we will be using to perform the installation has
sudoaccess on all nodes and is not a root user.
All required kernel modules are loaded.
The system control settings are set correctly.
Any GPUs to be used with Anaconda Enterprise have a supported NVIDIA CUDA driver installed.
The system meets all network port requirements, whether the specified ports need to be open internally, externally, or during installation only.
The firewall is configured correctly, and an rules designed to limit traffic have been temporarily disabled until such time that Anaconda Enterprise is installed and verified.
The domains required for online package mirroring have been allowlisted, if applicable.
The final TLS/SSL certificates <certs> to be installed with Anaconda Enterprise have been obtained, including the private keys.
The Anaconda Enterprise
CNAMEdomain record is fully operational, and points to the IP address of the master node.
The wildcard DNS entry for Anaconda Enterprise is also fully operational, and points to the IP address of the master node. More information about the wildcard DNS requirements can be found here.
/etc/resolv.conffile on all the nodes does not include the
Any existing installations of Docker (and
lxdhave been removed from all nodes, as they will conflict with Anaconda Enterprise.
All web browsers to be used to access Anaconda Enterprise are supported by the platform.