Installing the cluster¶
After you have determined the initial topology for your Anaconda Enterprise cluster, verified that your system meets all of the installation requirements, and you have completed the pre-install checklist, you’re ready to install the cluster.
Basic installation¶
Open a terminal on the master node and log in to a service account with sudo access.
Download and decompress the installer:
If you are in an airgapped environment, deliver the installer to the master node in an alternate manner, and proceed with the
tar
/cd
steps in the same fashion.Set up and initialize your conda environment by running the following command:
Enter
yes
to allow the installer to initialize yourae5-conda
environment by runningconda init
when prompted.Verify your environment successfully created by running the following command:
This command returns a list of existing conda environments. You should see a
base
environment present with an asterisk next to the directory to indicate it is currently active.Run the Anaconda preflight system check on the master node:
Note
You will receive an overall
PASS
orWARN
result from the script. The output is captured in aresults.txt
file for later reference, if necessary. If something goes wrong, you can view the results to determine the cause and course of correction.Create a file named
values.yaml
and populate it with the following content:If you are installing a single-node cluster and you want to use the
/opt/anaconda/storage
volume for managed persistence, thepersistence:
section of thevalues.yaml
can be entered as:Note
The direct use of
/opt/anaconda/storage
for managed persistence works only for single-node clusters. It must be replaced with a network file system (NFS) configuration before adding additional nodes to the cluster. Otherwise, sessions and deployments launched on the additional nodes will fail to start. For more information about managed persistence, see managed persistence.Run the gravity installation command:
Here is an example of what the installation command looks like for a single-node cluster:
If you are using an alternate
TMPDIR
, prepend the command with this new value. For example:Note
The
--service-uid
is the service account UID and cannot be a root user.Monitor the progress from the command line. Your output will look like this:
Allow time for the process to complete, approximately 20-30 minutes.
Create a local user account and password to log in to the Gravity Operations Center. To do so, enter the Gravity environment from any of the nodes:
Then run the following command to create a local user account and password.
Finally, run the following command within the Gravity environment to tell Gravity that you have completed the installation:
Proceed to the post-install configuration steps.
Note
The AE5 application itself will likely require another 30 minutes or so to fully load. The post-install configuration steps describe how to confirm that this process is fully complete.
Wizard installation (deprecated)¶
Prior versions of this documentation recommended the use of Gravity’s web-based wizard. We now strongly recommend the command-line approach offered above, as it is simpler, more reliable, and more flexible. If you prefer the web-based approach, we have moved those instructions to a separate page.