Cloudify Examples: Drupal Blueprint
This blueprint deploys a Drupal CMS. This blueprint is part of the End-to-end Solutions Package, which demonstrates functionality in Cloudify using an existing Database and Load Balancer provided as deploy time inputs, and several front-end applications. Before installing this deployment, install the MariaDB Blueprint, the HAProxy Blueprint. Following the drupal deployment, continue with installing the Kubernetes Cluster and the WordPress Application.
- Cloudify 4.2
Upload the required plugins:
Check the relevant blueprint for the latest version of the plugin.
Install the relevant example network blueprint for the IaaS that you wish to deploy on:
In addition to the pre-requisites for your example network blueprint, you will need the following secrets:
agent_key_public. If you do not already have these secrets, can generate them with the
keys.yamlblueprint in the helpful blueprint repo.
Install the MariaDB Blueprint
- After installation is successful, check the deployment outputs. There is a single deployment output called
cluster_addresses, which is a list of IP addresses. Select a single IP, this will be the value for your
application_ipinput in this blueprint, as a seed-IP.
Install the HAproxy Blueprint
There are no special instructions between deployment of HAProxy and Drupal.
On your Cloudify Manager, navigate to Local Blueprints select Upload.
Right-click and copy URL. Paste the URL where it says Enter blueprint url. Provide a blueprint name, such as lb in the field labeled blueprint name.
Select the blueprint for the relevant IaaS you wish to deploy on, for example aws.yaml from Blueprint filename menu. Click Upload.
After the new blueprint has been created, provide the seed
application_ip input (see Install the MariaDB Blueprint above) click the Deploy button.
Navigate to Deployments, find your new deployment, select Install from the workflows menu. At this stage, you may provide your own values for any of the default deployment inputs.
For example, the openstack.yaml blueprint requires that you provide a value for
image. This is the ID of a Centos 7 image. You may also need to override the default
flavor as the default value
2 may not be available in your account or appropriate.
You may also provide new values for the
lb_deployment inputs. These are the deployment IDs of the MariaDB Blueprint Deployment and the HAProxy Blueprint Deployment respectively.
Navigate to the deployment and select
Uninstall. When the uninstall workflow is finished, select