Public | Automated Build

Last pushed: 2 years ago
Short Description
The Webserver component of Chorus.
Full Description

chorus

Chorus is a project for the Docker Community Hackthon.
It has it's roots in a container scheduler called Orchestra.

About

Chorus is a docker build farm, designed to facilitate testing and building docker containers.
It leverages Celery and RabbitMQ to allow communication to happen between nodes.
It is designed to be run over a closed LAN, or inside a private cloud or AWS VPC- segregated from public traffic.
<br>
Overview:
<br>

Quick Start Guide

To deploy Chorus, you'll need machines with docker installed.
On most hosts, this is as simple as (but your mileage may vary, and you should definately consult the docker website:
curl https://get.docker.com/ | sh

You'll probably want to use the bootstrap scripts to get up and running with a worker, so it's probably easiest to
install git on your master, and worker nodes.

Once you've cloned the repo, you'll have to create config.json files, that contain the passwords needed.
Here are two examples:

master config.json (should be placed in the chorus/master/ folder)

{
  "CHORUS_HOST": "THIS IS THE IP WORKERS WILL USE TO CONNECT TO CHORUS",
  "CHORUS_RMQ_MASTER": "THIS IS THE PASSWORD FOR THE MASTER QUEUE",
  "CHORUS_RMQ_WORKER": "THIS IS THE PASSWORD FOR THE WORKER QUEUE",
  "CHORUS_POSTGRES_PASSWORD": "THIS IS THE PASSWORD THAT WILL BE USED FOR POSTGRESQL"
}

worker config.json (should be placed in the chorus/worker/ folder)

{
  "CHORUS_HOST": "THIS IS THE IP WORKERS WILL USE TO CONNECT TO CHORUS",
  "CHORUS_RMQ_MASTER": "THIS IS THE PASSWORD FOR THE MASTER QUEUE",
  "CHORUS_RMQ_WORKER": "THIS IS THE PASSWORD FOR THE WORKER QUEUE",
  "CHORUS_POSTGRES_PASSWORD": "THIS IS THE PASSWORD THAT WILL BE USED FOR POSTGRESQL"
  "DOCKER_GID": "THIS IS THE NUMBER OF THE DOCKER GROUP GID, CAN BE FOUND BY CATTING /etc/groups"
}

Once you have created either a worker, or master config file you can launch either by running:
$ ./bootstrap.sh
(This must be done from the chorus/master or chorus/worker folders.)

If there are any problems, use the docker logs command in conjunction with docker ps -a to find your containers.
Typically configuration problems involve bad values inside the config.json file.

Docker Pull Command
Owner
niallbyrne
Source Repository