https://github.com/cloudify-cosmo/cloudify-nodecellar-example
A sample Cloudify 3 application consisted of a nodejs server and mongodb database.
https://github.com/cloudify-cosmo/cloudify-nodecellar-example
Last synced: 3 months ago
JSON representation
A sample Cloudify 3 application consisted of a nodejs server and mongodb database.
- Host: GitHub
- URL: https://github.com/cloudify-cosmo/cloudify-nodecellar-example
- Owner: cloudify-cosmo
- License: apache-2.0
- Created: 2014-05-04T09:28:30.000Z (about 12 years ago)
- Default Branch: master
- Last Pushed: 2024-10-29T17:30:47.000Z (over 1 year ago)
- Last Synced: 2025-12-20T01:51:19.640Z (5 months ago)
- Language: Shell
- Size: 1.67 MB
- Stars: 17
- Watchers: 42
- Forks: 46
- Open Issues: 12
-
Metadata Files:
- Readme: README.md
- License: LICENSE
Awesome Lists containing this project
README
# Cloudify Nodecellar Example
[](https://circleci.com/gh/cloudify-cosmo/cloudify-nodecellar-example/tree/master)
This repository contains several blueprints for installing the
[nodecellar](http://coenraets.org/blog/2012/10/nodecellar-sample-application-with-backbone-js-twitter-bootstrap-node-js-express-and-mongodb/)
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](http://docs.getcloudify.org/latest/intro/installation/).
This will let you run the various blueprints.
**Note:
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](local-blueprint.yaml) 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](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
- [EC2 Blueprint](aws-ec2-blueprint.yaml)
- [Openstack Blueprint](openstack-blueprint.yaml)
- [Openstack Nova Net Blueprint](openstack-nova-net-blueprint.yaml)
- [Openstack HAProxy Blueprint](openstack-haproxy-blueprint.yaml)
- [Simple Blueprint](simple-blueprint.yaml)
- [Softlayer Blueprint](softlayer-blueprint.yaml)
- [CloudStack Blueprint](cloudstack-blueprint.yaml)
- [CloudStack VPC Blueprint](cloudstack-vpc-blueprint.yaml)
- [Host Pool Blueprint](host-pool-blueprint.yaml) - To install this
blueprint, you must have a running [Host Pool Service](https://github.com/cloudify-cosmo/cloudify-host-pool-service) available. More
information can be found [Here](http://getcloudify.org/guide/3.2/plugin-host-pool.html#host-pool-service)
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](https://docs.cloudify.co/latest/install_maintain/installation/installing-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 `
### 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 -i inputs/`
### Step 4: Install
Once the deployment is created, we can start running workflows:
`cfy executions start install -d `
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 `
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 `
### 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 `
### 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 [getcloudify.org](http://getcloudify.org) for more guides and tutorials.