Prerequisites for Installing a Cloudify Manager
Before you install a Cloudify Manager, you must review these prerequisites and make sure that your environment is ready to support the Cloudify Manager.
Cloudify Manager requires at the least:
The minimum requirements are enough for small deployments that only manage a few compute instances. Managers that manage more deployments or large deployments need at least the recommended resources.
Recommended resource requirements are tested and verified to be dependent on these criteria:
- Blueprints: The only limit to the number of blueprints is the storage required to store the number and size of the local blueprints.
- Deployments: Each deployment requires minimal storage.
- Nodes: Cloudify can orchestrate 12,000 non-monitored nodes (tested with 2000 deployments, each spanning 6 node instances). Monitored nodes add CPU load to the manager and require storage for the logs, events and metrics.
- Tenants: You can run up to 1000 tenants on a manager.
- Workflows & Concurrency: You can run up to 100 concurrent workflows.
- Logs, events and metrics: You must have enough storage to store the logs, events and metrics sent from the hosts. You can configure log rotation to reduce the amount of storage space required.
Architecture and OS
Cloudify Manager is supported for installation on a 64-bit host with RHEL/CentOS 7.4.
Cloudify Images for Amazon, OpenStack, and Docker
You can also create a Cloudify Manager with the Amazon AWS, OpenStack, or Docker images available at Cloudify downloads.
Cloudify Manager requires at least 2 network interfaces with configured IP addresses:
- Private - This interface is dedicated for communication with other Cloudify components, including agents and cluster members.
- Public - This interface is dedicated for connections to the Cloudify Manager with the Cloudify CLI and Cloudify Console.
There are specific packages that are commonly included in RHEL/CentOS. You must have these packages installed before you install Cloudify Manager:
sudo- Required to run commands with root privileges (note that this is still a requirement even when running with root user)
openssl-1.0.2k- Required to generate internal/external certificates
openssh-server- Required for creating SSH keys during the sanity check
logrotate- Required for rotating Cloudify log files
systemd-sysv- Required by PostgreSQL DB
initscripts- Required by RabbitMQ
which- Required to install Logstash plugins
python-setuptools- Required by Python
python-backports- Required by Python
python-backports-ssl_match_hostname- Required by Python
Cloudify Manager listens on the following ports:
|80||REST API and UI. This port must be accessible when SSL is not enabled.|
|443||REST API and UI. This port must be accessible when SSL is enabled.|
|22||For remote access to the manager from the Cloudify CLI. (Optional)|
|5671||RabbitMQ. This port must be accessible from agent VMs.|
|53333||Internal REST communications. This port must be accessible from agent VMs.|
Additionally, when the Manager is part of a Cloudify Manager cluster, the following ports must be accessible from all the other nodes in the cluster:
|8300||Internal port for the distributed key/value store.|
|8301||Internal port for TCP and UDP heartbeats. Must be accessible for both TCP and UDP.|
|8500||Port used for outage recovery in the event that half of the nodes in the cluster failed.|
|15432||Database replication port.|
|22000||Filesystem replication port.|
All ports are TCP unless noted otherwise.
Cloudify manager is a complete application. As such, it contains several installed dependencies such as PostgreSQL, NGINX, RabbitMQ and others. It is required that you install Cloudify manager on a standalone VM or container and do not co-locate any other applications on that machine or container (beyond possible monitoring or logging software). You must install the Cloudify manager as described in the installation instructions in this guide.