bacongobbler

14 ms·

91.
Deis v1.1.0 – CoreOS Stable, Monthly Releases(deis.io)
4 points by bacongobbler 12y ago|0 comments
92.
by bacongobbler 12y ago
we have a bunch of sample applications which we run nightly integration tests against. As for application tutorials themselves, we have the buildpack[1] and the dockerfile[2] workflows. [1]: http://docs.deis.io/en/lates
93.
by bacongobbler 12y ago
yes, tcp support in the router is something we'd like to work on but is not there yet for v1.0.
94.
by 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&#
95.
by bacongobbler 12y ago
Just a quick note, Rackspace has been notoriously slow with getting CoreOS's latest images up, so we've had to work around that with noting that you have to update your machines first before deploying Deis. They just updated to v4
96.
by bacongobbler 12y ago
> Deis = heroku-like interface on top of your own private cloud There are a few things like Dockerfile deployments and a `deis pull` workflow for importing your docker images from either DockerHub or an in-house registry as an app, but f
97.
by 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 datab
98.
by bacongobbler 12y ago
I used to work on Cloud Foundry for a while. I eventually left the project and became a core maintainer of Deis and have never looked back. Why? The community is absolutely amazing here. I have had pleasant conversations with everyone from
99.
by bacongobbler 12y ago
this is more of a Docker than a Deis question, but a Docker image is composed of layers. Each tagged image keeps an ancestry list of all of the layers it requires. In your case, if you run 5 docker containers on the same host on top of ubun
100.
by bacongobbler 12y ago
From the outside, not much. Both model the Heroku-style workflow with application deployment. Asides from Deis being production-ready and tacking on a few extra features like `deis pull` and Dockerfile deployment workflows, we take a differ
101.
by bacongobbler 12y ago
We hear this conversation quite a bit. Kubernetes is not a competitor to Deis. Kubernetes is a container cluster manager; a scheduler, if you will. You give it a container and some desired state and it will schedule it out to a cluster of n
102.
by bacongobbler 12y ago
That's ancient documentation -- v0.3.0! That being said, we support any provider which runs CoreOS. Deis is just an platform which utilizes Fleet, Etcd and Docker. The best place to start would be to take a look at the Quick Start docu
103.
by 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 a
104.
by bacongobbler 12y ago
rancher is a bit different. It's based on lower-level APIs which allow your containers to hook into a certain cloud-provider features like Amazon's EBS, ELBs and VPCs. Deis uses the docker engine to ship and run applications, prov
105.
Deis Sponsors Dokku(deis.io)
7 points by bacongobbler 12y ago|0 comments
106.
by bacongobbler 12y ago
Just gonna leave this here... http://docs.deis.io/en/latest/using_deis/using-dockerfiles/
107.
by bacongobbler 12y ago
It's on the roadmap :)
108.
by bacongobbler 12y ago
Yep. It was because slugbuilder didn't lock buildpacks to a known working version when you ran a `docker build`. It always pulled master, which may or may not work. We fixed that up, and we're in sync with Heroku's buildpack
109.
by bacongobbler 12y ago
What download issues do you speak of? They work great in Deis' test infrastructure: http://ci.deis.io/view/example-apps/job/test-integration-rub...
110.
by bacongobbler 12y ago
Well, "open source Heroku" implies that they're compatible with Heroku's API. That means application release management, runtime configuration (config:set), application collaboration via "sharing"... From what
111.
by bacongobbler 12y ago
FWIW, Deis really wants to help orchestrate multiple containers across nodes. There's talk about scheduling/pinning apps to certain nodes (such as if you really need your workers on a machine with more CPU), and currently we also
112.
by bacongobbler 12y ago
If you need any help getting set up, we're quite receptive to questions on #deis! > I'm a huge fan of Dokku, and Deis seems to be a very similar project with the added bonus of handling scaling for you. Deis is built to be a di
113.
by bacongobbler 12y ago
FYI there are some really cool ways that you can recycle and re-use dockerfiles with ONBUILD commands. We actually do that for some of our containers as well, such as when you have multiple python projects. https://github.com&#x2
114.
by bacongobbler 12y ago
Still a work in progress. See https://github.com/dotcloud/docker/issues/4023
115.
by bacongobbler 12y ago
Indeed we do. Feel free to contribute to the conversation here: https://github.com/deis/deis/issues/231
116.
by bacongobbler 12y ago
Deis maintainer here. I'll be happy to answer any questions you may have either here or on twitter :) https://twitter.com/bacongobbler
117.
by bacongobbler 12y ago
You can handle database migrations the same way as you would on Heroku. Deploy the application, then do the migrations afterwards with `deis run`.
118.
by bacongobbler 12y ago
yes, it's still lxc-docker.
119.
by bacongobbler 12y ago
A small enhancement to your HOST_IP grepping, the host's public and private IP is available in /etc/environment. docker0 may or may not be present before a docker run as well due to socket activation, so your results may vary
120.
by bacongobbler 13y ago
We'll be updating the website in preparation for our next release. Most users are still on v0.7.0 or earlier. Once it's been released then our website should reflect the changes in master.

More ›