3 ms·
Let me preface this by saying that I'm a huge fan of Deis and the team. I went through the process of setting up a cluster a few months ago and they were incred
by mmcclure 12y ago
Let me preface this by saying that I'm a huge fan of Deis and the team. I went through the process of setting up a cluster a few months ago and they were incredibly helpful and responsive in IRC. Highly suggest, would love to work with the project again.
That being said, I'm a little confused as to how Deis can be considered production ready when the underlying infrastructure (Etcd and Fleet from CoreOS) aren't. Both are making great progress, and I wouldn't worry too much about using them directly, but "production ready" abstractions on top of something maybe-not-so-production-ready makes me cringe a tiny bit.
https://github.com/coreos/etcd/blob/master/Documentation/production-ready.md https://github.com/coreos/etcd/blob/master/Documentation/pro...
- gabrtv 12y agoYour point is taken: some of the underlying technologies we use are still under active development. That said, we've worked with enough production Deis deployments to know that etcd and fleet (for example) run much better than some might think. As early adopters of these technologies, we have strong relationships (and often formal L3 support) with the teams involved. We are often the first to report issues as well as the first to test fixes. You can view this announcement as a vote of confidence in those projects and our ability to roll out fixes as bugs surface. Hope to see you back in the #deis channel soon!
- 23david 12y agoFrom reading the release notes, it looks like the current 1.0.0 release doesn't work with the latest stable docker 1.3.1 due to incompatibilities with the tls layer? https://github.com/deis/deis/releases https://github.com/boot2docker/boot2docker/issues/571 https://github.com/deis/deis/issues/2230 Why not wait until that is resolved before announcing production ready? :-(