Private Cloud: System requirements

General requirements

Operating system: Ubuntu 18–22, Centos Stream 9, Red Hat Enterprise Linux 7 or 8.
RAM: 16 GB–128 GB, depending on the size of the model.
CPU: Any modern x86-64 CPU with 8+ logical cores.
HDD: Approximately 115 GB of total free space. When allocating space, keep in mind that the space can be split between multiple volumes; see below.
Docker: Version 25.0.4 should be installed and working.
Activation: Product key for Team License Server.

Note that the Lite and Pro editions have specific limits on concurrent models:

For Private Cloud Lite: 16 models
For Private Cloud Pro: 64 models

Any cores that exceed the listed limits will not be used.

Additional nodes available to Private Cloud Enterprise users have no specific requirements other than having Docker installed. However, the resources provided by the nodes will directly impact the performance of your cloud-based model runs, so choose the machines with the general requirements in mind.

The requirements listed above are minimal. The desired configuration will depend on the intended use of Private Cloud (types of models that will run in Cloud). For more specific details that take into account network and platform infrastructure, see the section below.

Detailed requirements

Operating system

Private Cloud has been tested on Ubuntu 20.04 LTS and CentOS Stream 9, with Docker 25.0.4 installed. We recommend using the latest Ubuntu LTS distribution for full compatibility.

Red Hat Enterprise Linux has not been tested, but AnyLogic Cloud can be installed on it. Note that Red Hat does not provide official support for Docker on RHEL 8. To install it manually, execute the following commands in sequence:

sudo dnf config-manager --add-repo=https://download.docker.com/linux/centos/docker-ce.repo
sudo dnf install docker-ce

If you are installing AnyLogic Private Cloud on the RedHat OS machine, certain commands will differ from those described in this guide. For example, instead of the Ubuntu command sudo apt install, use sudo yum install.

CPU

Any modern x86-64 CPU with 8+ logical cores. The number of cores should be equal to the expected number of concurrently running models, plus 4. Private Cloud reserves 4 cores for its components.

When choosing a CPU, keep in mind that Private Cloud currently supports only x86-64 CPUs. Attempting to use processors based on other architectures, even those capable of emulating the behavior of the required processors in virtual machines, will result in problems and fatal errors. 3 CPU cores are required for non-execution activities. For example, a 4-core unit will only be able to run one model at a time. Choose the appropriate number of cores based on your workload.

Disk space

Private Cloud requires 115+ GB of total free space.

When allocating space, keep in mind that the space can be split across multiple volumes:

The installation folder requires 5 GB for the application itself and 100 GB for storing future run results.
In /var/lib/docker, 10 GB are required for AnyLogic Cloud containers and their settings.
Other system and Private Cloud volumes must have sufficient free space, including caches of all containers.
The installation package requires about 7 GB of free space for unpacking.
Software services should be able to create new files.
The root volume must have more than 5 GB of free space.
The installation volume must have more than 100 GB of free space.
The inodes table must have sufficient entries.
The hard limit on the number of files opened by the Private Cloud user must be sufficient. We recommend using the default hard limit of the operating system.

Docker

Make sure that the Docker package is installed on your host machine. To do this, run the following command in your Linux terminal:

sudo docker ps

If this command does not return any errors, you can proceed.

To learn how to install Docker, see the official manual.

Private Cloud has been tested with Docker version 25.0.4, build 1a576c5.

Activation (Team License Server)

Private Cloud Lite and Pro require activation through Team License Server. Before installing Private Cloud, do the following:

Install the latest version of Team License Server, as described in its documentation.
Request the activation key for your Private Cloud edition. The key must be valid and not expired.
Use this key to activate the product.
Ensure the instance can connect to Team License Server and obtain the appropriate license.

Private Cloud Enterprise does not require Team License Server to be installed. If no valid license is available, the instance will remain functional except for the runtime engine. Attempting to run a model (via UI or API) without a license will result in an error.

User permissions

The user which extracts the installer archive must have read, write, and execute permissions for each of the extracted files and directories.
The user specified as the installation owner (alcadm by default) must have read, write, and execute permissions for the location of the Private Cloud installer files and directories and the location of the project installation.
The user should be able to modify the hosts file, as this is where the Private Cloud registry address is specified.

Setup commands

The following commands are used during the Private Cloud installation and must be allowed:

sudo
visudo
cp
scp
useradd
passwd
usermod
ssh-copy-id

Ports

The following ports are used by the Private Cloud components:

For internal network configuration and to allow the host to connect to external interfaces: 22, 80, 5000, 5432, 5672, 9000, 9050, 9080, 9101, 9102, 9103, 9200, 9201, and 9202.
For external connections: 80 or 443 (for HTTP and HTTPS, respectively).

For more information on how Private Cloud uses these ports, see the architecture guide.

Miscellaneous requirements

The private key SSH from the controller Docker container to the host machine must be enabled and allowed for the user specified as the installation owner (alcadm by default). If SSH settings are automatically managed by Puppet, Chief, or other similar software, make sure their configuration does not interfere with the SSH connection of the controller service.
Docker must be able to retrieve images from the local registry. If a proxy server is used, the Docker proxy settings must be configured correctly.
The connection between different Docker containers of Private Cloud should not be dropped by iptables or firewall rules or any other software, such as deep packet inspection (DPI) software.
A static IP address or hostname must be specified as the external address of Private Cloud in the appropriate configuration file. Dynamic IP or 127.0.0.1/localhost are not allowed.
To use HTTPS, the instance requires public and private SSL certificates. Self-signed certificates are not permitted. The certificates are provided by you as a customer; AnyLogic does not provide them.

How can we improve this article?