Hacker News Board Hacker News, browsed like a classic message board
Live data from Hacker News

Deis: Open Source PaaS based on Docker, Chef, and Heroku Buildpacks

deis.io

Post reply on HN
Print view View original

11–20 of 29 posts

Re: Deis: Open Source PaaS based on Docker, Chef, and Heroku Buildpacks

#11

Post by fizx »

gabrtv wrote: post #9
alperakgun wrote: post #8

is there a public paas deis server where i can deploy some test apps? or do u or does anyone plan a commercial heroku or dotcloud clone?

Deis is designed for running your own PaaS. You can use public or private clouds, but we still require you run your own controller. If you're looking for a public PaaS solution, we recommend you take a look at dotCloud or Heroku. With regard to a commercial offering, OpDemand (the company behind Deis) plans on offering paid support and professional services for Deis deployments once the project reaches stability.

ProTip: If you are building anything that you expect users to run themselves, copy/steal FoundationDB's AWS CloudFormation setup. One click and a couple form fields to setup, one click to tear down.

Edit: http://foundationdb.com/documentation/beta1/getting-started-...

Re: Deis: Open Source PaaS based on Docker, Chef, and Heroku Buildpacks

#12

Post by gabrtv »

fizx wrote: post #11
gabrtv wrote: post #9

Earlier quoted context omitted.

Deis is designed for running your own PaaS. You can use public or private clouds, but we still require you run your own controller. If you're looking for a public PaaS solution, we recommend you take a look at dotCloud or Heroku. With regard to a commercial offering, OpDemand (the company behind Deis) plans on offering paid support and professional services for Deis deployments once the project reaches stability.

ProTip: If you are building anything that you expect users to run themselves, copy/steal FoundationDB's AWS CloudFormation setup. One click and a couple form fields to setup, one click to tear down. Edit: http://foundationdb.com/documentation/beta1/getting-started-...

Many of the companies interested in using Deis want a private cloud deployment, so we have intentionally avoided tying ourselves exclusively to AWS/EC2. That said, we can certainly make the installation process a bit easier in future releases. CloudFormation could be part of that.

Re: Deis: Open Source PaaS based on Docker, Chef, and Heroku Buildpacks

#13

Post by mwcampbell »

gabrtv wrote: post #2

Gabriel Monroy here, creator of the Deis project. I'll be answering questions here and on Twitter (@gabrtv). I want to give a big shout out to the Docker crew for their support. I should also mention the release notes (which explain what's next) can be found here: http://deis.io/deis-0-0-5-public-beta/

How do you plan to support private-cloud deployments? In particular, I'd like to deploy this on bare-metal servers, using containers (presumably via Docker) but not VMs.

Re: Deis: Open Source PaaS based on Docker, Chef, and Heroku Buildpacks

#14

Post by gabrtv »

mwcampbell wrote: post #13
gabrtv wrote: post #2

Gabriel Monroy here, creator of the Deis project. I'll be answering questions here and on Twitter (@gabrtv). I want to give a big shout out to the Docker crew for their support. I should also mention the release notes (which explain what's next) can be found here: http://deis.io/deis-0-0-5-public-beta/

How do you plan to support private-cloud deployments? In particular, I'd like to deploy this on bare-metal servers, using containers (presumably via Docker) but not VMs.

Deis was designed with private cloud in mind. The only trick with bare-metal is that we need a provisioning API so the controller can scale nodes up and down. Check out our EC2 provider plugin to see the 5 Celery tasks you'd need to implement to get Deis working on bare metal: https://github.com/opdemand/deis/blob/master/celerytasks/ec2...

Re: Deis: Open Source PaaS based on Docker, Chef, and Heroku Buildpacks

#15

Post by chourobin »

gabrtv wrote: post #2

Gabriel Monroy here, creator of the Deis project. I'll be answering questions here and on Twitter (@gabrtv). I want to give a big shout out to the Docker crew for their support. I should also mention the release notes (which explain what's next) can be found here: http://deis.io/deis-0-0-5-public-beta/

Awesome work, this project looks great. Do you plan to add support for Amazon's ELB to serve as proxy?

Re: Deis: Open Source PaaS based on Docker, Chef, and Heroku Buildpacks

#16

Post by gabrtv »

chourobin wrote: post #15
gabrtv wrote: post #2

Gabriel Monroy here, creator of the Deis project. I'll be answering questions here and on Twitter (@gabrtv). I want to give a big shout out to the Docker crew for their support. I should also mention the release notes (which explain what's next) can be found here: http://deis.io/deis-0-0-5-public-beta/

Awesome work, this project looks great. Do you plan to add support for Amazon's ELB to serve as proxy?

It's certainly possible to implement ELB as a proxy. We'd be open to a pull request for that.

However our focus on private cloud means we must use Nodes/Instances/VMs for every component. This is how we decouple the PaaS from the underlying cloud provider.

Re: Deis: Open Source PaaS based on Docker, Chef, and Heroku Buildpacks

#18

Post by pdeuchler »

This is really exciting, I've been waiting for someone to combine all of the various deployment technologies like this for a while.

However... If I set up my servers manually, or even through chef, I have pretty intimate knowledge of how my apps are being deployed. I know the various pipes data goes through, software versions, what services are running, etc. In other words, I have a pretty reasonable mental model of my deployment architecture. This is especially helpful when troubleshooting. However while the magic of Deis looks like a godsend, I am very caution about upgrading my technical debt from "managing my app servers, load balancer, and db servers" to "managing a PaaS that I happen to run my app on". I'm not trying to do ops for a Heroku clone, I'm just looking for an easier way to streamline my deployment process. What happens when I run "git push deis master" on a new release and everything breaks? The last thing I want to be doing is searching through the Deis github repo for error strings while my site is down.

Can anyone from the project assuage my fears? I realize this is kind of an open ended question, but a little assurance can go a long way.

Related: What are the planned price ranges for support on this?

Re: Deis: Open Source PaaS based on Docker, Chef, and Heroku Buildpacks

#20

Post by gabrtv »

pdeuchler wrote: post #18

This is really exciting, I've been waiting for someone to combine all of the various deployment technologies like this for a while. However... If I set up my servers manually, or even through chef, I have pretty intimate knowledge of how my apps are being deployed. I know the various pipes data goes through, software versions, what services are running, etc. In other words, I have a pretty reasonable mental model of…

I understand the concern about potential black box on the deployment side. Few points 1) this is an open-source project with a relatively small code-base and few moving parts 2) Chef does most of the heavy lifting on the deployment side using Databags and traditional Chef runs and 3) the build/release/run workflow is described here: http://docs.deis.io/en/latest/gettingstarted/concepts/#build...

With regard to support, OpDemand (creator/maintainer of Deis) will be launching paid support and professional services once the project stabilizes. Price points are not set yet. How would you like to see it priced?

Post reply on HN