Getting Started with OpenStack

A quick tutorial for getting started with Cloudify and deploying your first blueprint on OpenStack

Try Instantly

You can take Cloudify for an instant test drive with an online trial.


In this tutorial you will bootstrap a Cloudify manager in your OpenStack environment and install a sample Cloudify blueprint on it.

The blueprint you’ll be deploying, describes a nodejs application that connects to a MongoDB database and presents a wine catalog. To learn more about blueprint syntax and elements please refer to the Blueprints Guide.

Before You Begin

It is recommended that you try the Getting started first familiarize yourself with Cloudify and its concepts. Also, to complete this tutorial you’ll need to have an OpenStack cloud environment and credentials.

Step by Step Walkthrough

Step 1: Install the Cloudify CLI

The first thing you’ll need to do is install the Cloudify CLI, which will let you upload blueprints, create deployments, and execute workflows. To do so follow the steps described in the CLI installation guide.

Step 2: Download the Manager Blueprint for OpenStack

Next, let’s create a cloudify-manager dir and download the OpenStack Manager Blueprint.

mkdir -p ~/cloudify-manager
cd ~/cloudify-manager
git clone

Now let’s initialize a local Cloudify working environment:

cfy init

This will create a folder named .cloudify to save the current context for the Cloudify CLI, but you shouldn’t care about that for now.

Now let’s move on to bootstrap configuration.

Configuring your Manager Blueprint for HP OpenStack

HP Cloud is a public OpenStack cloud. As such it provides a fairly easy starting point for experiencing a fully operational OpenStack environment. To use HP Cloud you need to Setup an account on the HP Helion Cloud.

This blueprint defines quite a few input parameters we need to fill out.

Let’s make a copy of the inputs template already provided and edit it:

cd cloudify-manager-blueprints/openstack
cp inputs.json.template inputs.json

The inputs.json file should look somewhat like this:

    "keystone_username": "your_openstack_username",
    "keystone_password": "your_openstack_password",
    "keystone_tenant_name": "your_openstack_tenant",
    "keystone_url": "",
    "region": "region-b.geo-1",
    "manager_public_key_name": "manager-kp",
    "agent_public_key_name": "agent-kp",
    "image_id": "8c096c29-a666-4b82-99c4-c77dc70cfb40",
    "flavor_id": "102",
    "external_network_name": "Ext-Net",

    "use_existing_manager_keypair": false,
    "use_existing_agent_keypair": false,
    "manager_server_name": "cloudify-management-server",
    "manager_server_user": "ubuntu",
    "manager_server_user_home": "/home/ubuntu",
    "manager_private_key_path": "~/.ssh/cloudify-manager-kp.pem",
    "agent_private_key_path": "~/.ssh/cloudify-agent-kp.pem",
    "agents_user": "ubuntu",
    "nova_url": "",
    "neutron_url": "",
    "resources_prefix": "cloudify"

You will, at the very least, have to provide the following:

  • keystone_username
  • keystone_password
  • keystone_tenant_name

In case you are using a different openstack environment, you should also change the following values:

  • image_id
  • flavor_id
  • external_network_name

to fit your specific openstack installation.

Notice that the resources_prefix parameter is set to “cloudify” so that all resources provisioned during this guide are prefixed for easy identification.

Step 3: Bootstrap the Cloudify Management Environment

Now you’re ready to bootstrap your Cloudify manager. To do so type the following command in your shell:

cfy bootstrap --install-plugins -p openstack.yaml -i inputs.json


The install-plugins functionality only works if you are running from within a virtualenv. If this is not the case, installing plugins will require sudo permissions and can be done like so:

cfy local create-requirements -o requirements.txt -p openstack.yaml
sudo pip install -r requirements.txt

This should take a few minutes to complete. After validating the configuration, cfy will create the management VM, related networks and security groups (the latter two will not be created if they already exist), download the relevant Cloudify manager packages from the internet and install all of the components. At the end of this process you should see the following message:

bootstrapping complete
management server is up at <YOUR MANAGER IP ADDRESS>

To validate this installation, point your web browser to the manager IP address (port 80). You should see Cloudify’s Web UI. At this point there’s nothing much to see since you haven’t uploaded any blueprints yet.

Step 4: Upload the Blueprint and Create a Deployment

Next, you’ll upload a sample blueprint and create a deployment based on it.

In the cloudify-nodecellar-example directory you just cloned, you can see a blueprint file (named singlehost-blueprint.yaml) alongside other resources related to this blueprint.

To upload the blueprint run:

cfy blueprints upload -b nodecellar -p openstack-blueprint.yaml

The -b flag assigns a unique name to this blueprint on the Cloudify manager. Before creating a deployment though, let’s see what this blueprint looks like. Point your browser at the manager’s URL again and refresh the screen. You will see the nodecellar blueprint listed there.

Blueprints table

Click the blueprint, and you can see its topology. A topology consists of elements called nodes.

In our case, we have the following nodes:

  • Two VM’s (one for mongo and one for nodejs)
  • A nodejs server
  • A MongoDB database
  • A nodejs application called nodecellar (which is a nice sample nodejs application backed by mongodb).

Nodecellar Blueprint

This blueprint defines some input parameters:

Nodecellar Inputs

Let’s make a copy of the inputs template already provided and edit it:

cd cloudify-nodecellar-example/inputs/openstack.json.template
cp openstack.json.template inputs.json

The inputs.json file should look somewhat like this:

    "image": "8c096c29-a666-4b82-99c4-c77dc70cfb40",
    "flavor": "102",
    "agent_user": "ubuntu"

Next, we need to create a deployment. To do so, type the following command:

cfy deployments create -b nodecellar -d nodecellar --inputs inputs.json

We’ve now created a deployment named nodecellar based on a blueprint with the same name. This deployment is not yet materialized, since we haven’t issued an installation command. If you click the “Deployments” icon in the left sidebar in the web UI, you will see that all nodes are labeled with 0/1, which means they’re pending creation.

Nodecellar Deployment

Step 5: Install the Deployment

In Cloudify, installing a certain deployment is done by executing the a install workflow. type the following command in your terminal:

cfy executions start -w install -d nodecellar

This will take a couple of minutes, during which the resources will be created and configured.

To track the progress of the installation, you can look at the events emitted to the terminal window. Each event is labeled with its time, the deployment name and the node in our topology that it relates to, e.g.

2014-12-02T09:46:05 CFY <nodecellar> [nodejs_d36c8] Creating node

In the Web UI, you can checkout the Logs/Events page for an overview of all Logs and Events in a specific Manager.


You can also have a look at the Monitoring tab and see some default metrics:



The blueprint we installed actually defines a custom collector for the Mongo database. To add mongo related graphs to the dashboard, have a look at Adding Custom Graphs.

Step 6: Test Drive the Application

To test the application, you will need to access it using its public IP address. Because we deploying directly on the vagrant box, you can just go to to access it from your web browser. The marvelous nodecellar application should be up on your screen. Click the “Browse wines” button to verify that the application was installed successfully and can access the mongodb database to read the list of wines.


Step 7: Uninstall the Deployment

Uninstalling the deployment is just a matter of running another workflow, which will teardown all the resources provisioned by the install workflow. To run the uninstall workflow, type the following command:

cfy executions start -w uninstall -d nodecellar

Similarly to the install workflow, you can track the progress of the uninstall process in the CLI or the web UI using the events that are displayed in both. Once the workflow is completed, you can verify that the resources were indeed destroyed.

In a real cloud deployment, each and every resource provisioned by the deployment will be destroyed. In our case, there aren’t any external resources, only application related ones.

Step 8: Delete the Deployment

The next step is deleting the deployment. Assuming the un-installation went fine, all of the application resources should have been removed. However, the deployment itself still has record on the manager. For example, all of its static and runtime properties are still stored in the manager’s database. To clean up all the information related to the deployment on the manager, delete the deployment as follows:

cfy deployments delete -d nodecellar

Step 10: Teardown the Manager

Next, you can also teardown the manager if you have no use for it anymore. This can be done by issuing the following command:

cfy teardown -f

This will terminate the manager VM and delete the resources associated with it.

What’s Next

For a more elaborate installation tutorial, please refer to the Openstack Installation Guide.