gabrtv

28 ms·

91.
by gabrtv 12y ago
Bog standard permalinks to the rescue: company.com/some-promotion
92.
by gabrtv 12y ago
Come find us in #deis on Freenode and we'll see if we can help.
93.
by gabrtv 12y ago
Top notch technical writeup. We've had our eyes on Vulcand for some time now, though we'd really like to see native TCP support.
94.
by gabrtv 12y ago
You can do everything you mentioned with Deis 0.8.0. - Process management is handled the same way it is on Heroku, with a `deis scale` command. The fleet scheduler ensures processes are automatically restarted on host failure. - How you se
95.
by gabrtv 12y ago
We are grateful for the Flynn project's emphasis on modular, reusable components that can be leveraged by those building platforms. I suspect we will collaborate more in the future :)
96.
by gabrtv 12y ago
I think the biggest difference is that Flynn is building a scheduler modeled after Google's Omega paper (what they call Layer-0) along with the Heroku-style platform components (which they call Layer-1) -- all written from scratch in G
97.
by gabrtv 12y ago
When we first released Deis, we were most interested in answering questions around workflow and how you should design a PaaS that leverages Docker from the ground up. We used node convergence and Chef databags because it worked and alterna
98.
by gabrtv 12y ago
Docker, etcd, fleet are powerful tools, but they don't magically solve problems for software teams the way a platform like Heroku does. Deis is designed to tie all of the above into a streamlined workflow for developers. Specifically,
99.
by gabrtv 12y ago
I speak for the whole Deis team when I say we're extra excited about this release as it lays the groundwork for our 1.0. Happy to answer any questions here.
100.
by gabrtv 12y ago
The idea behind PaaS is to abstract away underlying infrastructure. Here it seems users are managing servers, load balancers and interconnects directly. While very cool, this style of automation is a far cry from PaaS.
101.
by gabrtv 13y ago
Always happy to see shifts toward lighter-weight operating systems. Sadly this technology seems too tied to Red Hat to be of wider use to those of us building platforms. IMHO CoreOS provides much better primitives for building platforms in
102.
by gabrtv 13y ago
OpDemand -- Boulder, Colorado OpDemand makes Deis, the open source PaaS powered by Docker. Using Deis, software teams can deploy and manage applications and services on their own "private Heroku" that runs on public cloud, private
103.
by gabrtv 13y ago
The project is moving so fast it warps time. Hard to believe it's only been a year. Big congrats to the team.
104.
by gabrtv 13y ago
This is a big release for the project. Now that every Deis component is a Docker container we can start work on things like: * Removing the hard dependency on Chef * Integrating with an enterprise-grade scheduler (possibly Mesos) If you ha
105.
by gabrtv 13y ago
OpDemand -- Boulder, Colorado or Remote OpDemand makes Deis, the open source PaaS based on Docker, Chef and Heroku. Using Deis, software teams can deploy and manage applications and services on their own "private Heroku" that runs
106.
by gabrtv 13y ago
Impressive display of persistence, stringing together those vulnerabilities. I also see your English has gotten noticeably better :) Keep up the good work!
107.
by gabrtv 13y ago
This is really terrific. I think the best feature is the integrated search, which is significantly better than Google if you're looking for authoritative API docs. Questions: How did you source the docs? Can they go stale? What vers
108.
Deis open source PaaS adds Rollback & Enhanced Auditing(deis.io)
8 points by gabrtv 13y ago|0 comments
109.
Deis announces App Sharing and Docker 0.7.1(deis.io)
3 points by gabrtv 13y ago|0 comments
110.
by gabrtv 13y ago
If you're looking for a private Heroku that's multi-host, check out http://deis.io/ . We are about to announce our 0.3 release which features team support (e.g. deis sharing:add <user>)
111.
Deis open source PaaS now with full Vagrant support(deis.io)
1 points by gabrtv 13y ago|0 comments
112.
by gabrtv 13y ago
I agree this looks very cool. As far as http://deis.io/ is concerned, we're focused more on the "operate your own PaaS" capability, whereas this seems to be a pure hosted service -- which is great for lots o
113.
Deis open source PaaS now supports DigitalOcean(deis.io)
4 points by gabrtv 13y ago|0 comments
114.
by gabrtv 13y ago
Of course! I'm also on twitter @gabrtv or #deis on Freenode.
115.
by gabrtv 13y ago
Gabriel Monroy here, creator of Deis, one of the Docker PaaS's ( http://deis.io/overview/ ). I'd love to pick your brain about your current dilemma and see if we can help. Email me: gabriel _at_ opdemand.com.
116.
by gabrtv 13y ago
You can run Deis on anything including bare metal by constructing the application fabric manually. We have _automated_ provisioning for EC2 and Rackspace public cloud, with more on the way.
117.
by gabrtv 13y ago
We do have plans for a hosted version of Deis -- similar to Cloud 66 -- that eases the spin-up of the PaaS controller/brains.. and lets ops folks take it from there, scale their application fabric, hand it off to developers, etc. I&#x
118.
Deis, DevOps and the Future of Open PaaS(deis.io)
30 points by gabrtv 13y ago|4 comments
119.
by gabrtv 13y ago
Docker and Chef are not mutually exclusive. Case in point: http://deis.io/ is a PaaS that uses Chef extensively for orchestration of containers. There are other approaches that don't use CM (e.g. CoreOS) but they are
120.
by gabrtv 13y ago
email me: gabriel _ opdemand _ com and i'm happy to continue the discussion.

More ›