https://github.com/greggigon/cloudify-docker-container

Cloudify 3.x in Docker container
https://github.com/greggigon/cloudify-docker-container

Last synced: about 1 month ago
JSON representation

Cloudify 3.x in Docker container

• Host: GitHub
• URL: https://github.com/greggigon/cloudify-docker-container
• Owner: greggigon
• Created: 2014-10-16T11:09:38.000Z (about 10 years ago)
• Default Branch: master
• Last Pushed: 2014-10-30T17:27:14.000Z (about 10 years ago)
• Last Synced: 2023-03-23T01:01:26.974Z (over 1 year ago)
• Language: Shell
• Homepage:
• Size: 167 KB
• Stars: 4
• Watchers: 1
• Forks: 3
• Open Issues: 0
• Metadata Files:
  • Readme: README.md

Awesome Lists containing this project

README

        
Cloudify Docker Container

=========================

[Docker](http://docker.io "Docker") files that prepare [Cloudify 3.x](http://getcloudify.org "Cloudify 3.x") to run as a Docker Container.

> The master branch builds Container with Cloudify version **3.1m4**.

The base image for Cloudify Docker container is the most excelent image from Phussion team [https://github.com/phusion/baseimage-docker](https://github.com/phusion/baseimage-docker).

## Building container

Container builds in two phases:

 1. All Cloudify components (eg. Elasticsearch, RabbitMQ, Logstash, etc.)

 2. Cloudify Manager, REST,  service and other Stuff

> **Prerequisites** You need Docker and Internet access to be able to build

> Cloudify in Docker container.

### Components container

To build components container run:

	sh build-components-intermidiate-container.sh

in the **components-build** folder.

Once the build finishes, you can see **cfy_components** image build (run *docker images* from command line).

### Manager container

Once you got **Components container** build you can build Manager.

To build Manage Container run:

	sh build-manager.sh

in the **manager-build** folder.

Once the build is finished you should see **cfy_manager** added to list of images in docker.

> **IMPORTANT:**

> The manager container build will fail if the components container build was unsuccessful or not done at all.

### Running container

You can run container by running prepared script:

	sh run-manager-container.sh MANAGER_IP_TO_USE KEYS_FOLDER [RUN_INTERACTIVE]

Where: 

* MANAGER_IP_TO_USE - passed to Cloudify components

* KEYS_FOLDER - directory on the host, that will be mapped to Docker Container /keys directory

* RUN_INTERACTIVE - optional, if false or missing, Container will start detached in background. true will leave terminal open with BASH in container.

The script does TCP Port mapping between Docker Container and Docker Host. This makes Clodify manager available to the external world. 

> **IMPORTANT:**

> If you are running Docker inside VM (like I do via Vagrant) you might want to specify your HOST IP address as a parameter when starting Docker container, so Physical Host ports are mapped to VM ports, which in turn maps to Docker ports (yada-yada).