cameronmaske / skipper

Build, deploy and orchestrate your application using Docker + CoreOS.
BSD 2-Clause "Simplified" License
12 stars 0 forks source link

Host Provisioning #11

Closed Jwpe closed 10 years ago

Jwpe commented 10 years ago

Hey, you know how we were talking about host provisioning the other day - whether you should have to define a set of hosts where each one represents a box, or whether you could just define the backend service that you use and then provision stuff programatically through their API? I was thinking a bit more about it, but I thought it would be good to discuss it on here. Here are some advantages of the second pattern that I can see:

I still think that skipper's brain should keep a record of hosts, so it knows which Docker containers to communicate with, but I think you could get away with generating those in the background as a result of your service definitions, instead of defining both sides.

cameronmaske commented 10 years ago

@Jwpe After hashing out some of the host setup stuff, communicating with the backend services (boto or digital ocean) seem to make more and more sense. You get a few key advantage to boot up a pre-existing, already configured image, ready to run Docker.

I think a step back and constructing a proof of concept with ec2 might be the best way to get a better idea of all the details.

This project I stumbled across a while back does something very similar. https://github.com/andreasjansson/head-in-the-clouds