Provision consul, registrator, LB and backend fia Fig

[shanesveller]

@bellycard/infrastructure

Playground: fig scale app=3 and refresh your browser a few times to watch the backend container ID change.

[kevinreedy]

Looking sweet so far

[shanesveller]

@kevinreedy When you're not busy and have good Internet, can you play with the instructions and see what I've missed?

[kevinreedy]

Playing with it now

[kevinreedy]

I got it working, but here were the gotchas:

• You might want to add a brew update in the top of the readme
• I'd replace From within the subdirectory with cd nginx-official
• boot2docker ip has some extra output which can be confusing:

kreedy@Kevins-MacBook-Pro-2:~/Projects/docker-loadbalancer/nginx-official$ curl http://`boot2docker ip`:8500/v1/catalog/services

The VM's Host only interface IP address is:

{"app":["production"],"consul":[],"consul-53":["udp"],"consul-8300":[],"consul-8400":[],"consul-8500":[],"nginxofficial_lb-80":[]}

As for the TODO section, will we need Vagrant anymore once we have fig?

[shanesveller]

It looks like if I redirect stderr I can clean up the output, although the command itself becomes even more ugly:

$ curl http://`boot2docker ip 2>/dev/null`:8500/v1/catalog/services
{"app":["production"],"consul":[],"consul-53":["udp"],"consul-8300":[],"consul-8400":[],"consul-8500":[],"web_lb":[]}

I still get some kind of odd variant of a % symbol at the end in my particular shell environment.

For Vagrant, my thought process there is to try to make this also work in a CoreOS VM to get closer to our present production environment.

[kevinreedy]

Yea, that is pretty ugly. In the one-liner we could do something like export $OMG_IP=boot2docker ip. Not sure it's worth the trouble though.

[kevinreedy]

As for Vagrant, I don't think it matters too much in this example. When it comes to dif for napa services we may want to drop Vagrant for simplicity's sake. We can cross that bridge when we get there.

[shanesveller]

@bellycard/infrastructure Ready for final review. Particular attention towards open-sourcing this as-is appreciated!

[shanesveller]

If we're going to OS this repo as-is, thoughts on moving pretty much everything into the root?

[kevinreedy]

:+1: moving to root sounds like a good plan