totem / discover

Service Discovery for Docker

totem.github.io

In order to look at published version for totem documentation , please visit totem.github.io

Issue Tracker

All issues related to totem components and documentation can be tracked at: https://github.com/totem/totem.github.io/issues

Contributing to totem documentation

In order to contribute towards improving totem documentation , please fork this repository and submit pull request to develop branch. (Note: master branch is being used for hosting published version of github pages)

Pre-Requisites

• node v0.10.30+
• bower (npm install -g bower)

Installing Dependencies

npm install
bower install

Running Documentation Server (Locally)

docpad server

This will start docpad server at: http://localhost:9778

Publishing to totem.github.io (Admins Only)

Totem admins can publish the develop branch to totem.github.io using:

node_modules/docpad/bin/docpad deploy-ghpages --env static

Totem Integration

The development version of documentation can be found at: http://totem-site.elb.us-west-1.cu.melt.sh

Feature branches are deployed to: http://totem-site-{{feature_name}}.elb.us-west-1.cu.melt.sh

discover's Issues

Increase logging when there are errors

Something caused the daemon to die and it didn't respawn as expected. This could have been caused by the etcd cluster being down.

Support ENV variables defined both with and without single or double quotation marks

Installation Error : Failed at the [email protected] install script 'node-gyp rebuild'.

npm ERR! Darwin 14.3.0
npm ERR! argv "node" "/usr/local/bin/npm" "install" "-g" "docker-discover"
npm ERR! node v0.12.2
npm ERR! npm v2.7.5
npm ERR! code ELIFECYCLE

npm ERR! [email protected] install: node-gyp rebuild
npm ERR! Exit status 1
npm ERR!
npm ERR! Failed at the [email protected] install script 'node-gyp rebuild'.
npm ERR! This is most likely a problem with the node-v8-clone package,
npm ERR! not with npm itself.
npm ERR! Tell the author that this fails on your system:
npm ERR! node-gyp rebuild
npm ERR! You can get their info via:
npm ERR! npm owner ls node-v8-clone
npm ERR! There is likely additional logging output above.

npm ERR! Please include the following file with any support request:
npm ERR! /Users/jmcnally/projects/npm-debug.log

Look into supporting private ports / IP's

Switch from docker.io to dockerode

docker.io has had a lot of stability problems. dockerode seems to be both stable and have good test coverage. Look into switching underlying libs.

unregister services in any case a container isn't available any more

It seems to me that docker emits a die-event (in addition) every time a container stops, gets killed or dies on its own. Unfortunately I haven't found any documentation on this behavior.

I think it would be better to unregister services in any case a container isn't available any more. So I suggest to check for "die" instead of "stop" here: https://github.com/totem/discover/blob/develop/lib/discover.js#L161

What do you think?

Cannot run discover

After building it from this docker file

FROM totem/ubuntu:raring
RUN apt-get update --fix-missing && apt-get upgrade -y
RUN apt-get install -y wget curl build-essential patch git-core openssl libssl-dev unzip
RUN curl http://nodejs.org/dist/v0.10.20/node-v0.10.20-linux-x64.tar.gz | tar xzvf - --strip-components=1 -C "/usr"
RUN apt-get clean && rm -rf /var/cache/apt/archives/* /var/lib/apt/lists/*
RUN npm install -g node-static
ENV DISCOVER "static-web-server:8080"
ENTRYPOINT ['static']

I get the following error

docker run -p 8080 static-web-server
/bin/sh: 1: [static]: not found

Support lookup and advertising of FQDN within AWS EC2 instances for routing of advertised services.

Currently the IPv4 address of ETH0 is used to advertise services. This works great for resources internal to AWS as this is a private IP, does not work so well when needing to consume services published in AWS from outside the network.

Invalid configuration regardless of config file used

The latest version of discover from npm always gives the following error even when using the example config file at https://github.com/totem/discover/blob/develop/config/defaults.json

Error: Invalid configuration, you must provide valid `host` and `etcd` configuration blocks

The config file I'm using is:

{
  "etcd": {
    "port": 4001,
    "host": "localhost",
    "prefix": "discover/"
  },
  "host": {
    "ip": "localhost",
    "realm": "testing"
  },
  "log": "~/.docker-discover/discover.log"
}