Earlier quoted context omitted.
The 'cluster' is a group of nodes running the Docker + Flynn software. It can be anything from a single server to a fleet of EC2 instances to a rack of servers. It would be easy to make a tool that spawns instances running Flynn on your choice of public/private cloud.
Okay, thanks for clarifying. The next question then would be, if you do reach your stretch goals and implement auto-scaling, would you at that point have cloud/MaaS API integration?
Flynn - Open Source PaaS powered by Docker
21–30 of 155 posts
Re: Flynn - Open Source PaaS powered by Docker
#22So it's not open source yet?
Re: Flynn - Open Source PaaS powered by Docker
#23And this is why you shouldn't open source the core part of your business (looking at you DotCloud). Sure, Docker is good for the community. But it's also a key competitive advantage for DotCloud. By giving away that advantage, they create opportunities for viable competitors.
Indeed. I'm a bit curious as to why DotCloud released Docker? I mean, sure, someone was going to have an easy-to-use container system sooner or later, but for now that is one of the few defining features that DotCloud has going for them... although one of their competitors is successfully using a modified version of Cloud Foundry (AppFog).
Re: Flynn - Open Source PaaS powered by Docker
#24And this is why you shouldn't open source the core part of your business (looking at you DotCloud). Sure, Docker is good for the community. But it's also a key competitive advantage for DotCloud. By giving away that advantage, they create opportunities for viable competitors.
The dirty little secret of PaaS is that there is not, and will never be a single PaaS that fits everyone's needs. With docker we offer a foundation for many PaaSes to engage in a healthy competition while preserving interoperability.
So Shopify will always be free to mix and match Flynn's lego bricks with the bricks of other offerings - because they are all Docker-compatible. The authors of Flynn get that, which is why I believe their product will be good and I will be personally sponsoring it :)
Re: Flynn - Open Source PaaS powered by Docker
#25Re: Flynn - Open Source PaaS powered by Docker
#26So it's not open source yet?
It's still in the early stages of development. We're currently fundraising so that we can work on it full time. All code will be pushed to GitHub as we write it.
Re: Flynn - Open Source PaaS powered by Docker
#27My main problem with Docker is that container IP addresses and MACs are changed after every container reboot. This means I can't have a database in one container and a web app in another because I have no way for the web app to discover the address of the database server. Seems like this would be an issue for the host-only (private) network?
Docker is in very active development and issues like this get resolved every week. That said, it's not a problem because of the service discovery and routing that would be involved in the Flynn system.
Re: Flynn - Open Source PaaS powered by Docker
#28Re: Flynn - Open Source PaaS powered by Docker
#29And this is why you shouldn't open source the core part of your business (looking at you DotCloud). Sure, Docker is good for the community. But it's also a key competitive advantage for DotCloud. By giving away that advantage, they create opportunities for viable competitors.
Hi, I'm the founder of dotCloud and author of Docker. Projects like Flynn are the reason we opened Docker in the first place. They are a good thing for the docker ecosystem, and they are definitely good for dotCloud. The dirty little secret of PaaS is that there is not, and will never be a single PaaS that fits everyone's needs. With docker we offer a foundation for many PaaSes to engage in a healthy competition whil…