Skip to content
A sample Cloudify 3 application consisted of a nodejs server and mongodb database.
Branch: master
Clone or download
Latest commit be76680 Jun 5, 2019
Type Name Latest commit message Commit time
Failed to load latest commit information.
inputs Update nodecellar example for vcoud plugin Nov 5, 2015
.gitignore CFY-1746 Upgrade nodecellar example Dec 2, 2014
LICENSE Initial commit May 4, 2014 Install from RPM instead of bootstrapping (#114) Feb 7, 2019
aws-ec2-blueprint.yaml Bump version Jun 5, 2019
azure-blueprint.yaml Bump version Jun 5, 2019
circle.yml Bump version Mar 26, 2018
cloudstack-blueprint.yaml Bump version Jun 5, 2019
host-pool-blueprint.yaml Bump version Jun 5, 2019
local-blueprint.yaml Bump version Jun 5, 2019
openstack-blueprint.yaml Bump version Jun 5, 2019
openstack-haproxy-blueprint.yaml Bump version Jun 5, 2019
openstack-nova-net-blueprint.yaml Bump version Jun 5, 2019
simple-blueprint-with-secrets.yaml Bump version Jun 5, 2019
simple-blueprint.yaml Bump version Jun 5, 2019
softlayer-blueprint.yaml Bump version Jun 5, 2019
vcloud-blueprint.yaml Bump version Jun 5, 2019
vsphere-blueprint.yaml Bump version Jun 5, 2019

Cloudify Nodecellar Example

Circle CI

alt text alt text alt text alt text alt text alt text alt text alt text alt text alt text

This repository contains several blueprints for installing the nodecellar application.
Nodecellar example consists of:

  • A Mongo Database
  • A NodeJS Server
  • A Javascript Application

The first thing you'll need to do is install the Cloudify CLI.
This will let you run the various blueprints.

Documentation about the blueprints content is located inside the blueprint files themselves.
Presented here are only instructions on how to RUN the blueprints using the Cloudify CLI.

From now on, all commands will assume that the working directory is the root of this repository.

Local Blueprint

This blueprint allows you to install the nodecellar application on your local machine.
Let see how this is done:

Step 1: Initialize

cfy init local-blueprint.yaml

This command (as the name suggests) initializes your working directory to work with the given blueprint. Now, you can run any type of workflows on this blueprint.

Step 2: Install

Lets run the install workflow:

cfy executions start install

This command will install all the application components on you local machine. (don't worry, its all installed under the tmp directory)
Once its done, you should be able to browse to http://localhost:8080 and see the application.

Step 3: Uninstall

To uninstall the application we run the uninstall workflow:

cfy executions start uninstall

All other blueprints

All of these blueprints allow you to install the nodecellar application on different cloud environments. Doing this requires first to bootstrap a Cloudify Manager.

Step 1: Install a Cloudify Manager

Please refer to INSTALLING AND CONFIGURING CLOUDIFY MANAGER to install your own Cloudify Manager.

Great, now that you have your very own Cloudify Manager, we can work with these blueprints.

Step 2: Upload the blueprint

cfy blueprints upload -b <choose_blueprint_id> <blueprint_filename>

Step 3: Create a deployment

Every one of these blueprints have inputs, which can be populated for a deployment using input files.
Example input files are located inside the inputs directory.
Note that these files only contain the mandatory inputs, i.e, one's that the blueprint does not define a default value for.

After you filled the input file corresponding to your blueprint, run:

cfy deployments create -b <blueprint_id> <choose_deployment_id> -i inputs/<inputs_filename>

Step 4: Install

Once the deployment is created, we can start running workflows:

cfy executions start install -d <deployment_id>

This process will create all the cloud resources needed for the application:

  • VM's
  • Floating IP's
  • Security Groups

and everything else that is needed and declared in the blueprint.

Step 5: Verify installation

Once the workflow execution is complete, we can view the application endpoint by running:

cfy deployments outputs -d <deployment_id>

Hit that URL to see the application running.

Step 6: Uninstall

Now lets run the uninstall workflow. This will uninstall the application, as well as delete all related resources.

cfy executions start uninstall -d <deployment_id>

Step 7: Delete the deployment

Its best to delete deployments we are no longer using, since they take up memory on the management machine. We do this by running:

cfy deployments delete <deployment_id>

Step 8: Tearing down the manager

If you have no further use for your Cloudify Manager, you can tear it (and all resources created by the bootstrap process) by running:

cfy teardown -f

What's Next

Visit us on the Cloudify community website at for more guides and tutorials.

You can’t perform that action at this time.