gabrtv

17 ms·

121.
by gabrtv 13y ago
I find the name pretty funny myself... Speaking on behalf the the Deis team, it's nice to see another public PaaS getting an open source implementation. We're obviously bigger fans of the Heroku model than the GAE model, but that
122.
by gabrtv 13y ago
I'm a long time Boulder resident (10 years with a 3 year stint in NYC). I'm also co-founder and CTO at OpDemand. Our office is on the Pearl Street Mall in downtown Boulder. AMA. ;) Boulder is a fantastic place for startups, but
123.
by gabrtv 13y ago
Actually they're removing AuFS because it has awkward kernel dependencies and prevents Docker from running across all Linux distros. The move to device-mapper layers means Docker no longer requires a 3.8 kernel or an AuFS patch.
124.
by gabrtv 13y ago
Contrary to what you might think, those of us working on http://deis.io/ are excited by the Red Hat / Docker partnership and its implications on interoperability. Why? Because there will never be a one-size-fits-all
125.
by gabrtv 13y ago
To be clear you can use Openstack today, you just can't automatically provision Openstack instances. You have to construct your formation manually. However, you still get most of the platform benefits. :)
126.
Deis open source PaaS now ready for dev, test apps(deis.io)
29 points by gabrtv 13y ago|4 comments
127.
by gabrtv 13y ago
You beat me to posting this. Kudos. I'm Gabriel Monroy, creator of the Deis project. Happy to answer any questions on our 0.1.0 release. We're really excited about where the project stands today.
128.
by gabrtv 13y ago
As a founder and employer of a small team I can tell you that this is more complicated than it may look from the employee side. Consider that health care costs, equipment costs, office space, etc.. don't go down by 20% even though you
129.
by gabrtv 13y ago
I think the combination of Docker style LXC containers and kernel level MAC (i.e. SELinux) is a great approach and helps build upon the "high security" goals of OpenShift. I was also happy to hear about the resources you're p
130.
by gabrtv 13y ago
http://deis.io/ is based on Docker, Chef and Heroku Buildpacks. You can think of it as a private Heroku. It also has some similarity to OpsWorks in that you can configure and scale custom Chef layers. Best part -- it&#x2
131.
by gabrtv 13y ago
With http://deis.io/ we tried GitFlow as well as HubFlow ( http://datasift.github.io/gitflow/ ) which adds better GitHub integration. After a few release cycles, we decided to switch back to simple featu
132.
by gabrtv 13y ago
What I meant was "lost their possessions". Many of my friends had cell service right up until the flash flooding hit. A warning to evacuate based on drone imagery would have gone a long way.
133.
by gabrtv 13y ago
As a Boulder resident I'm incensed by this. The drone imagery in question would have provided us with more real-time data during a period where overflights were not possible by conventional aircraft/helos. Had I known what was ha
134.
by gabrtv 13y ago
If you need deeper control of your application platform infrastructure, you should check out something like http://deis.io/ . You can run a private Heroku in any EC2 region, zones, etc. Running your own PaaS is not for the
135.
by gabrtv 13y ago
I would say Deis's perceived value is: 1. Built using DevOps tools widely in use (i.e. Chef) so it integrates easily into most environments and is an easier sell to conservative Ops teams 2. Implemented with Django, Celery and other co
136.
by gabrtv 13y ago
peterwaller got it right, but let me try and give a little more color. Deis is provides a private Heroku-like platform powered by Docker & Chef. Once Deis is up and running, developers deploy with `git push deis master` and they automa
137.
by gabrtv 13y ago
Gabriel Monroy, creator of the Deis project here.. > I do wish more people would throw in with the Docker-based PaaSes that already have some momentum (Dokku, Flynn, etc.), rather than making their own. We at OpDemand have been working o
138.
by gabrtv 13y ago
We started the Azure integration and got hung up with their Python SDK. We're actively working with the Microsoft guys on it, but I wouldn't expect anything usable for a few months.
139.
by gabrtv 13y ago
Very nice work. I look forward to seeing native Docker support in other hypervisors.
140.
by gabrtv 13y ago
Log aggregation and admin commands were two of our biggest requested features. We're proud to have shipped these in v0.0.6. Lots more to come in the next few releases starting with new providers (RackSpace & Digital Ocean) and enh
141.
by gabrtv 13y ago
Absolutely. We will be outlining our paid support options soon.
142.
by gabrtv 13y ago
No question it's a high bar. Then again, I would have never predicted the rate at which Docker has matured already. Color me optimistic.
143.
by gabrtv 13y ago
We follow the twelve factor build/release/run model (see Concepts in our docs), so most deploy issues are caught during the build stage which occurs in the foreground of a git push. The run stage is a simple Chef run which pulls
144.
by gabrtv 13y ago
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 us
145.
by gabrtv 13y ago
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 Pa
146.
by gabrtv 13y ago
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
147.
by gabrtv 13y ago
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 r
148.
by gabrtv 13y ago
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
149.
by gabrtv 13y ago
Well firstly, I believe we're the first distributed Docker-based PaaS to be released. We are using Buildstep for Heroku Buildpack integration, which is part of Dokku. And we've been talking with the Flynn crew about how we can c
150.
by gabrtv 13y ago
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

More ›