4 ms·

Project creator here. It's been a fun 16 months getting to this point. Happy to answer questions.

by gabrtv 12y ago

willcodeforfoo 12y ago
Great work! I played around with deis a few months ago and it was the first PaaS I was able to get up and running and actually, you know, deploy an app to! Couple questions: 1. What about storage? I know you use ceph for the Docker registry, etc. Is that exposed so that apps can somehow use it? 2. When I tried it, performance was kind of lacking (for things like pushing apps and making config changes). Was this just a limitation of my setup (I used 3x2GB DigitalOcean nodes) or something you guys are working out? Thanks again!
- bacongobbler 12y ago
  Hi, I'm also a maintainer :) to answer your questions: 1) we expose ceph in the router, so your apps could use it. This will have to be managed by you however as we don't have a user story for plugging apps into backing services asides from `deis config:set`[1]... Yet. 2) Performance is still something we're working on. When you deploy an application using a Heroku buildpack[2], your app is compiled into a container which sits on top of Heroku's cedar stack, which is around 800MB[3]. It's a beefy stack so fleet will take some time deploying that image. This should only occur the first time it's scheduled onto a new host as future images will just use the cache for that image, significantly speeding up deployment times. If you deploy an app using a Dockerfile and it's been optimized correctly (we have an app sitting under 5MB for test purposes)[4], deployment times should be very speedy. Hope that answers your question! [1]: https://github.com/deis/deis/issues/231 https://github.com/deis/deis/issues/231 [2]: http://docs.deis.io/en/latest/using_deis/using-buildpacks/ http://docs.deis.io/en/latest/using_deis/using-buildpacks/ [3]: https://github.com/progrium/cedarish https://github.com/progrium/cedarish [4]: https://registry.hub.docker.com/u/deis/example-go/ https://registry.hub.docker.com/u/deis/example-go/
avtar 12y ago
I'm not a huge Drupal or Wordpress fan but I can see how people would want to deploy either of those CMS options. I would be interested in hearing your thoughts regarding this discussion: https://github.com/deis/deis/issues/448 https://github.com/deis/deis/issues/448
- bacongobbler 12y ago
  This is one of the general problems about PaaS. One of the tenets of 12 factor is that "12 factor processes are stateless and share nothing. Any data that needs to persist must be stored in a stateful backing service, typically a database"[1] which is why we want to avoid persisting state in the container. Content Management Systems like Drupal or Wordpress typically store file uploads or configuration files directly onto the filesystem. With Deis or any other PaaS, this filesystem is ephemeral unless there is a shared filesystem mounted inside the container, typically via SSHFS[2] or some other remote filesystem. We want to tackle this problem with a service gateway[3] for apps to attach backing services like a shared filesystem, but for the moment there's always S3 :) [1]: http://12factor.net/processes http://12factor.net/processes [2]: http://fuse.sourceforge.net/sshfs.html http://fuse.sourceforge.net/sshfs.html [3]: https://github.com/deis/deis/issues/231 https://github.com/deis/deis/issues/231
simi_ 12y ago
I'll skip abstract questions and jump right to our concrete situation. We have a bunch of services (Go app, RethinkDB, redis, haraka MTA, server for an Angular app) running in Docker containers on Hetzner servers. Is Deis compatible with our use case?
- mstade 12y ago
  Since the router only does http right now (or so it seems) it probably isn't a good fit for you, or at least not for all services. I'd be really keen on trying Deis with RethinkDB if it got TCP support.
  - simi_ 12y ago
    Thank you!
quantisan 12y ago
What does Deis do about app logs? This is a main problem I have with Dokku at the moment.
- bacongobbler 12y ago
  application logs are aggregated and shipped to a logger component[1]. if you scale processes and run `deis logs`, you'll see the log output of every running process for that app. [1]: https://github.com/deis/deis/tree/master/logger https://github.com/deis/deis/tree/master/logger

Project creator here. It's been a fun 16 months getting to this point. Happy to answer questions.

by gabrtv 12y ago

Project creator here. It's been a fun 16 months getting to this point. Happy to answer questions.

Great work! I played around with deis a few months ago and it was the first PaaS I was able to get up and running and actually, you know, deploy an app to! Couple questions: 1. What about storage? I know you use ceph for the Docker registry, etc. Is that exposed so that apps can somehow use it? 2. When I tried it, performance was kind of lacking (for things like pushing apps and making config changes). Was this just a limitation of my setup (I used 3x2GB DigitalOcean nodes) or something you guys are working out? Thanks again!

bacongobbler 12y ago
Hi, I'm also a maintainer :) to answer your questions: 1) we expose ceph in the router, so your apps could use it. This will have to be managed by you however as we don't have a user story for plugging apps into backing services asides from `deis config:set`[1]... Yet. 2) Performance is still something we're working on. When you deploy an application using a Heroku buildpack[2], your app is compiled into a container which sits on top of Heroku's cedar stack, which is around 800MB[3]. It's a beefy stack so fleet will take some time deploying that image. This should only occur the first time it's scheduled onto a new host as future images will just use the cache for that image, significantly speeding up deployment times. If you deploy an app using a Dockerfile and it's been optimized correctly (we have an app sitting under 5MB for test purposes)[4], deployment times should be very speedy. Hope that answers your question! [1]: https://github.com/deis/deis/issues/231 https://github.com/deis/deis/issues/231 [2]: http://docs.deis.io/en/latest/using_deis/using-buildpacks/ http://docs.deis.io/en/latest/using_deis/using-buildpacks/ [3]: https://github.com/progrium/cedarish https://github.com/progrium/cedarish [4]: https://registry.hub.docker.com/u/deis/example-go/ https://registry.hub.docker.com/u/deis/example-go/

avtar 12y ago

I'm not a huge Drupal or Wordpress fan but I can see how people would want to deploy either of those CMS options. I would be interested in hearing your thoughts regarding this discussion: https://github.com/deis/deis/issues/448 https://github.com/deis/deis/issues/448

bacongobbler 12y ago
This is one of the general problems about PaaS. One of the tenets of 12 factor is that "12 factor processes are stateless and share nothing. Any data that needs to persist must be stored in a stateful backing service, typically a database"[1] which is why we want to avoid persisting state in the container. Content Management Systems like Drupal or Wordpress typically store file uploads or configuration files directly onto the filesystem. With Deis or any other PaaS, this filesystem is ephemeral unless there is a shared filesystem mounted inside the container, typically via SSHFS[2] or some other remote filesystem. We want to tackle this problem with a service gateway[3] for apps to attach backing services like a shared filesystem, but for the moment there's always S3 :) [1]: http://12factor.net/processes http://12factor.net/processes [2]: http://fuse.sourceforge.net/sshfs.html http://fuse.sourceforge.net/sshfs.html [3]: https://github.com/deis/deis/issues/231 https://github.com/deis/deis/issues/231

simi_ 12y ago

I'll skip abstract questions and jump right to our concrete situation. We have a bunch of services (Go app, RethinkDB, redis, haraka MTA, server for an Angular app) running in Docker containers on Hetzner servers. Is Deis compatible with our use case?

mstade 12y ago
Since the router only does http right now (or so it seems) it probably isn't a good fit for you, or at least not for all services. I'd be really keen on trying Deis with RethinkDB if it got TCP support.
- simi_ 12y ago
  Thank you!

quantisan 12y ago

What does Deis do about app logs? This is a main problem I have with Dokku at the moment.

bacongobbler 12y ago
application logs are aggregated and shipped to a logger component[1]. if you scale processes and run `deis logs`, you'll see the log output of every running process for that app. [1]: https://github.com/deis/deis/tree/master/logger https://github.com/deis/deis/tree/master/logger