Before deploying the Cloudify platform, please use this section to get familiar with the different deployment options for the Cloudify Platform and select the mode that suits you best.
Cloudify offers the following modes of installation:
- All-in-one single box deployment - Available for Community & Premium
- Compact cluster (3 nodes) - Premium only
- Fully distributed cluster (9+ nodes) - Premium only
All-in-One (AIO) deployment is based on a single Cloudify box (single VM/ container) running all the Cloudify components, mainly the manager, the database, and the messaging queue. An AIO deployment is recommended for non-mission critical use when high-availability is not required and the scale is not extreme. Cloudify AIO is typically used for development and testing systems but is also common in production for smaller-scale areas.
To learn more about installing an AIO Cloudify platform, as an rpm or leveraging OpenStack, Docker container images, please continue to:
Cloudify Compact Cluster (3 Nodes)
The Cloudify Compact Cluster deployment is based on 3 servers, each running all of the Cloudify services. Where the services are deployed in an active-active approach with a high-availability setup. A Compact Cluster provides an enterprise-grade Cloudify deployment suitable to almost any organization with a performance and scale equivalent to a fully distributed cluster containing 3 managers and with the option of further scaling using higher form factor hardware. The Compact Cluster is designed for mission-critical use and is availabel for Premium only.
To learn more about installing the Compact Cluster please continue to:
Note: The above-mentioned section will guide you on how to deploy a Compact Cluster manually. Cloudify provides an automated flow that simplifies the deployment over 3 existing VMs. To use the Cluster Manager package and automate the cluster deployment flow read: Cluster Manager Package.
Cloudify Fully Distributed Cluster
The Cloudify platform can be deployed as a fully distributed cluster, running each of the Cloudify services (mainly the manager, the database, and the messaging queue) on a dedicated VM/ node. This mode of installation provides the complete flexibility to deploy the database, and the messaging queue in a highly available mode (3 VMs per service), or leverage external services for them in the form of an external service or a public managed service such as Amazon RDS. It further allows scaling by leveraging 3 or more manager servers in an active-active mode.
Running the Cloudify platform as a fully distributed cluster provides the most flexibility, scaling options, and fits any enterprise for mission-critical use.
To learn more about installing the Cloudify fully distributed cluster please continue to:
- Fully Distributed Cluster Installation Guide
- Distributed cluster with external database and messaging queue
- Helm chart
Note: The above-mentioned section will guide you on how to deploy a distributed cluster manually. Cloudify provides an automated flow that simplifies the deployment over 9 existing VMs. To use the Cluster Manager package and automate the cluster deployment flow read: [Cluster Manager Package] (/cloudify_manager/premium/fully_distributed/install_and_configure/cluster_manager/).
Cloudify on Kubernetes
The Cloudify platform can be deployed on K8s using the Helm chart. Cloudify creates a stateful pod that will require persistence volume. It can be provisioned as an All-in-One, that contains all three layers (Cloudify Manager, Database, and Message Queue) or deployed as a cluster where the Manager is deployed on a separate pod and PostgreSQL DB or RabbitMQ Message Queue are either deployed on Kubernetes or used as external resources.