Deis 0.9.0 – Dockerfiles, Domains, and HA Routing

http://deis.io/deis-0-9-0-dockerfiles-domains-and-ha-routing/

by rgarcia • 12 years ago

38 18 12 years ago

cardmagic• 12 years ago

I just interviewed Deis CTO Gabriel Monroy about Deis and how it works with CoreOS and how it differs from Flynn and Dokku. Great guy, great team, and awesome project.

https://www.youtube.com/watch?v=j5EI16DG1sg

bacongobbler2• 12 years ago

Deis maintainer here. I'll be happy to answer any questions you may have either here or on twitter :)

https://twitter.com/bacongobbler

cbsmith6• 12 years ago

So, looking at the architecture, it seems like you have some design components that overlap with pieces design components in CoreOS. I'm not clear as to what components are really application components vs. platform operations components, so maybe that's it. But the use of rsyslog in lieu of systemd seems like really going against the CoreOS grain. Is this really a function of trying to mirror Heroku as closely as possible?

shykes4• 12 years ago

My understanding of Deis's design goals is that they will pick and choose their favorite components from any number of sources (including but not limited to CoreOS), but don't plan on locking themselves into any particular distro. Instead they are relying on Docker itself as the point of interoperability.

As a maintainer of Docker I think it's a good thing that you preserve the freedom to run your platform on any number of distros, and are not stuck, for example with having to install systemd everywhere.

gabrtv2• 12 years ago

So, looking at the architecture, it seems like you have some design components that overlap with pieces design components in CoreOS. I'm not clear as to what components are really application components vs. platform operations components, so maybe that's it.

Deis was architected before the CoreOS integration. While we love CoreOS, architecturally we need to remain scheduler agnostic. Probably a good opportunity for a blog post...

the use of rsyslog in lieu of systemd seems like really going against the CoreOS grain

We view platform logging as separate from application-level logging. Aggregating logs through the systemd journal is possible, but it would tie us a little too closely to systemd. Using log sidekick containers (as we do) is more portable and easier to funnel to end developers.

tristanz• 12 years ago

Is there any story for persistent data / running database services?

bacongobbler2• 12 years ago

Indeed we do. Feel free to contribute to the conversation here: https://github.com/deis/deis/issues/231

benmccann• 12 years ago

What is Deis using for this new HA routing? HAProxy, ELB, homegrown?

andyshinn• 12 years ago

It is their own nginx HTTP / TCP router, which is backed by etcd and confd. You can check it out at https://github.com/deis/deis/tree/master/router. Essentially, you can fire up multiple of these instances, and Deis uses them to route application, controller, and git traffic to the proper container.

Deis 0.9.0 – Dockerfiles, Domains, and HA Routing

Related Stories