7 ms·
Flynn still needs to do a much better job on the documentation front. It's entirely unclear how to use Flynn. Instead of just having vague architecture/philosop
by morgante 12y ago
Flynn still needs to do a much better job on the documentation front. It's entirely unclear how to use Flynn. Instead of just having vague architecture/philosophy discussions, they need very clear explanations.
From the demo/documentation they do have, it's unclear why Flynn is better than Deis, Heroku, etc.[1]
I had hoped that Flynn was/would be a tool for orchestrating complicated multi-container apps, not just deploying Procfiles. I don't need Procfiles, I need something which will let me integrate and orchestrate multiple Docker containers across multiple nodes. Most/many significant apps don't fit into the simplicity of Procfiles (we have over a dozen different services, some with relatively customize environments, all communicating with RabbitMQ middleware). At least for development, Docker containers have proven to be an ideal way to manage these services. As of yet, there doesn't seem to be a good tool for deploying them to production. I wish Flynn would tackle that head on (and document it!), instead of being yet another generic PaaS.
[1] https://github.com/flynn/flynn/tree/master/demo https://github.com/flynn/flynn/tree/master/demo
- Titanous 12y agoWhile Flynn is capable of a lot more, as evidenced by its architecture, leading up to the first production release we're focused on solving some of the simpler use cases really well. A solid "private Heroku" was the primary desire of a lot of our early sponsors, and we want to make sure we deliver on that promise. Once Flynn is stable, we can focus on the more complex use cases which, frankly, are what really excites our team.
- neom 12y agoIs private heroku still the right thing to build? I don't know the answer, it just sounded like you're building it because you said you would, but along the way have you found other/better use cases?
- SEJeff 12y agoTake a look at Fedora's atomic host. Heck, if all you need is orchestration of multiple hosts with docker containers, you only need a single bit from project atomic, geard[1]. [1] http://openshift.github.io/geard/ http://openshift.github.io/geard/
- bacongobbler 12y agoFWIW, 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 support deploying from both Dockerfiles and pulling images bit-for-bit from an in-house registry or from DockerHub. We have documentation, but ASCIIcasts seem to show this workflow better. Check it out! http://deis.io/demo-deis-pull-in-action/ http://deis.io/demo-deis-pull-in-action/
- eropple 12y agoI dig what Deis is doing here, but for me it's no good until it can run under Mesos (which is coming, I gather). I have more than just Deis needing to grab resources in my cluster.
- bacongobbler 12y agoIt's on the roadmap :)
- wiremine 12y ago> It's entirely unclear how to use Flynn I'll go a step further: it's unclear _what_ Flynn is. I read the homepage and was still confused.
- auvi 12y agoI am standing at the same step as you. It is confusing what is Flynn. Maybe it is CLU (Codified Likeness Utility) created by Kevin Flynn of TRON.
- venomsnake 12y agoSame here. How it is possible nowadays to have fronpage that is impossible to understand what your flagship product do.
- imdsm 12y agoI know what it is only from being around since it's inception. If I was new to it, I'd probably be confused too.
- corobo 12y agoI've been around since its inception and I've no idea what it does. It could do with the "explain like I'm 5" version - can I put wordpress on it and have it auto scale over my servers? Is that even a valid use case for this, does Flynn even do that sort of thing? Like I say I've realised I actually have no idea what Flynn does
- zmmmmm 12y ago> Flynn still needs to do a much better job on the documentation front. It's entirely unclear how to use Flynn. Yes. I mean nothing bad about the people behind it in saying this, but this is kind of a red flag to me for this kind of project - ie: when you're talking about basic infrastructure I look to see that the people behind it have a culture of continuous and rigorous documentation. Features shouldn't be allowed to be released in any form unless the documentation for them is included. If the product is as far along as it claims to be (a beta available), yet there is still almost zero documentation (at least, as evidenced on their site), then it's in a seriously bad situation. I'd urge them to do some reflection about this and institute some policies that ensure that documentation is emerging as a natural part of their process and not an afterthought that they plan to address later.