Standard environment preparation

This topic provides guidance for preparing your environment before Standard installation.

​

Install requirements

Software requirements

The installer is a self-extracting binary that contains the necessary components to run Anaconda Server services. The basic requirements prior to installation are:

• Any Linux variant capable of supporting Docker

• Use a fully qualified domain name (FQDN) or Hostname

• Docker Engine 1.13.1+ or Docker CE/EE 17.04+ (Supports Compose format 3.1)

• Docker Compose 1.11.0+ (Supports Compose format 3.1)

• DNS record and TLS/SSL certs (optional)

• Make sure that SELinux is not in enforcing mode, either by disabling it or putting it in permissive mode in the /etc/selinux/config file. If it is in enforcing mode, you will need to reboot your instance after updating. After rebooting, run the following command to verify that SELinux is not being enforced:

  Copy

  Ask AI

  getenforce
  # The result should be either Disabled or Permissive
  

Some additional recommendations:

• RHEL7/CentOS7: The most popular choice for most Anaconda Server users, and what Anaconda has the most experience supporting. The versions of Docker and Docker-compose available through the default yum package repository are sufficient.
• Anaconda Server 6.3.0 can operate on RHEL8 with Podman.
• Ubuntu 20.04 LTS: This has proven to be a reliable choice for customers as well, using the versions of Docker and Docker-Compose available in the default apt-get package repository.
• Other Linux variants that provide full support for Docker and Docker-Compose are likely to work as well, but we invite you to inquire with the Anaconda implementation team for our most up-to-date experience.

For Docker, the default log driver must be configured to the json-file.

For Red Hat systems, please refer to the Default options for modifying docker daemon options. To verify that you’re running the json-file, run the following command:

docker info --format '{{.LoggingDriver}}'

Hardware requirements

• 4 CPUs
• 8GB RAM
• 1TB storage space

When partitioning space, allocate 20GB for /var/lib and the remaining 1TB for /opt/anaconda.

​

DNS and TLS/SSL certificate requirements

Anaconda Server can use TLS/SSL certificates to provide transport layer security for the cluster. If you do not have these certs prior to installation, self-signed certificates can be generated during the initial installation. You can configure the platform to use organizational TLS/SSL certificates after completing the installation.

You may purchase certificates commercially, use Let’s Encrypt, or generate them using your organization’s internal public key infrastructure (PKI) system. When using an internal PKI-signed setup, the CA certificate is stored on the file system. You will need to make sure that the root certificate of your certificate authority is trusted by the server running the application and the workstations used by users of the application.

In either case, the configuration will include the following:

• A certificate for the root certificate authority (CA)
• An intermediate certificate chain
• A server certificate
• A private server key

DNS requirements

Web browsers use domain names and web origins to separate sites, so they cannot tamper with each other. If you want to use DNS, you must have it ready prior to installation. This DNS name is what users will use to access the application.

You must provide the SSL cert for the hostname your Anaconda Server instance is running on.

​

Security requirements

External — accessible outside of server

It is important to protect all services running on the node from outside access. The exceptions are as shown below:

• :443 nginx - only if you are using HTTPS
• :22 ssh - optional; only if you need SSH

Internal — accessible only within server

Anaconda Server uses several ports for internal communication between components. These ports do not need to be open to the end user.

• :5000 repo - Anaconda Server API
• :5002 repo-proxy - Anaconda Server file serving API proxy
• :5000 repo-dispatcher - Anaconda Server event dispatcher/handler (exposed only for prometheus metrics)
• :5000 repo-worker - Anaconda Server scheduled jobs worker (exposed only for prometheus metrics)
• :8080 keycloak - keycloak’s /auth/* endpoints are proxied in Nginx
• :5432 postgres - Postgresql database used by Anaconda Server and Keycloak
• :6379 redis - Redis instance used by Anaconda Server services
• :9090 prometheus - Prometheus is proxied in Nginx at /Prometheus

To change the postgres user password, run \password postgres when in the shell of the postgres container.

To change the redis user password, follow the instructions under Troubleshooting.

​

Enable IP address forwarding

Forwarding IP addresses allows containers to communicate with one another on your host. You’ll need to configure these settings to allow non-root users to perform installations of Anaconda Server.

sysctl net.ipv4.conf.all.forwarding=1
sysctl net.ipv6.conf.all.forwarding=1
iptables -P FORWARD ACCEPT

​

System validation checks

Once your environment is prepared, run the following commands to verify it is ready for installation of Anaconda Server.

To verify what type of processor your system is running and the number of CPUs present, run the command:

cat /proc/cpuinfo

To verify the amount of system memory is sufficient, run the command:

cat /proc/meminfo

To verify there is a sufficient amount of disk space for the installation, run the command:

df -h

To verify the kernel release version and processor type, run the command:

uname -a

To verify your operating system release version, run the command:

cat /etc/os-release

To verify your version of Docker, run the command:

docker version

To verify your version of docker-compose, run the command:

docker-compose --version

After ensuring all requirements have been met, proceed to Standard installation to install Anaconda Server.