Can anyone from the Flynn project comment on this versus Deis? I've tried Dokku and thought that was pretty slick, but ultimately decided to move on to a Deis/Chef devops setup, because dokku was too lightweight for my needs and Flynn wasn't ready.
Flynn: first preview release
51–60 of 80 posts
Re: Flynn: first preview release
#52Can anyone from the Flynn project comment on this versus Deis? I've tried Dokku and thought that was pretty slick, but ultimately decided to move on to a Deis/Chef devops setup, because dokku was too lightweight for my needs and Flynn wasn't ready.
Flynn definitely isn't "ready" yet. This is a preview release, production grade stability is still a few months away.
I haven't looked closely at Deis in several months, but Flynn doesn't use Chef (or anything similar) anywhere and don't plan to.
Re: Flynn: first preview release
#53Earlier quoted context omitted.
One thing I've been wondering about with Flynn is data persistence. I have an app already running that I'd like to move to Flynn for deployment; will it be easy to bring over a populated database and have it persist, shared, across instances of the app?
Currently there is a very alpha Postgres appliance[0] (including automatic cluster orchestration and a database provisioning API) included with Flynn and we'll be standardizing the appliance model and adding more in the future. Flynn datastore appliances run inside of containers and are managed by Flynn just like everything else and will include support for backups, HA/replication, etc. out of the box with close to z…
Thanks. It's been pretty tough to wait for Flynn's release. Great job so far, can't wait for it to get to stability so I can migrate!
Re: Flynn: first preview release
#54Earlier quoted context omitted.
There is an ongoing conundrum in the downstream Debian/Ubuntu packaging of Docker. Our friends at Debian and Ubuntu are doing their best to solve it. In the meantime, you should either a) install the latest docker from the official docker APT repos http://docs.docker.io/installation/ or b) do something like ln /usr/bin/docker{.io,} In any case, don't leave your Docker install without a docker binary in your path. Tha…
Yeah, I went with the `ln -s` method. Thanks Solomon!
another thing to watch out for: downstream packages (the one you have installed) are out-of-date. The current version of Docker is 0.10.0, and ships a ton of improvements. For that reason alone you should consider installing from upstream repos, at least until downstream catches up. Just keep it in a separate file in /etc/apt/sources.list.d to easily remove it later.
Re: Flynn: first preview release
#55Can anyone from the Flynn project comment on this versus Deis? I've tried Dokku and thought that was pretty slick, but ultimately decided to move on to a Deis/Chef devops setup, because dokku was too lightweight for my needs and Flynn wasn't ready.
Flynn definitely isn't "ready" yet. This is a preview release, production grade stability is still a few months away. I haven't looked closely at Deis in several months, but Flynn doesn't use Chef (or anything similar) anywhere and don't plan to.
Deis dev here. We've removed the Chef dependency as of v0.7.0 in favour of CoreOS and fleet for container/machine job scheduling. That ship set sail only recently in master. :)
Re: Flynn: first preview release
#56Very nit-picky comment, but: Can you explain in one or two sentences what the value proposition is?
I might be dense, but it took me quite a bit of clicking around, reading HN comments, and poking at the Omega paper to understand what you want to do their. (Well, I think I understand. The "private Heroku" line points in the right direction, at least)
Re: Flynn: first preview release
#57Re: Flynn: first preview release
#58Very nit-picky comment, but: Can you explain in one or two sentences what the value proposition is? I might be dense, but it took me quite a bit of clicking around, reading HN comments, and poking at the Omega paper to understand what you want to do their. (Well, I think I understand. The "private Heroku" line points in the right direction, at least)
Flynn is the product ops should provide to developers.
Flynn is a single platform that runs all your services from databases to applications to individual Linux processes. With Flynn ops teams can stop being consultants and start providing a single product to their internal "customers". Basically you can deploy and scale whatever you want all in one place on any infrastructure without having to think about individual hosts.
Re: Flynn: first preview release
#59How does Flynn compare to OpenShift or Cloud Foundry? Is it trying to solve the same problems, perhaps leapfrogging them in some ways?
[Edit] I would also ask the same about Apache Mesos since that seems like it's coming up a lot in this discussion as well.
Re: Flynn: first preview release
#60I'm not a DevOps person. Can someone explain in less jargony terms what this is? Is it like Heroku? I have no idea.