Live data from Hacker News

Flynn - Open Source PaaS powered by Docker

flynn.io

11–20 of 155 posts

Re: Flynn - Open Source PaaS powered by Docker

#11
post #8

Very cool! Been looking for something like this since Docker was announced. Basically Cloud Foundry is far too complex for what I/we need but this would fit the bill nicely. One question though, what is going to be 'the cluster' (The site says it distributes work across 'the cluster')? Basically, will it be capable of interfacing with cloud API's or will it just be you manually setting up a group of instances to host…

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.

Re: Flynn - Open Source PaaS powered by Docker

#12
My 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?

Re: Flynn - Open Source PaaS powered by Docker

#13
post #8

Very cool! Been looking for something like this since Docker was announced. Basically Cloud Foundry is far too complex for what I/we need but this would fit the bill nicely. One question though, what is going to be 'the cluster' (The site says it distributes work across 'the cluster')? Basically, will it be capable of interfacing with cloud API's or will it just be you manually setting up a group of instances to host…

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?

Re: Flynn - Open Source PaaS powered by Docker

#16

And 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.

Because it's better to have a small slice of a market that you can compete on than nothing on a market that is dominated by other players.

This supposed competitive advantage that they would have would mean nothing if they still had to work on top of other IaaS-providers. They would be undercut by the IaaS themselves. By changing the game, they get another angle to work from.

Re: Flynn - Open Source PaaS powered by Docker

#17
post #4

Earlier quoted context omitted.

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.

I don't see this in the FAQ: the magic that makes all of this happen (which you're integrating) is technology built by other developers. Why should we be supporting you to do this work rather than the other developers who broke ground and already did a majority of the heavy lifting?

Docker was a big piece of the puzzle. I worked with DotCloud to make Docker happen and we're involved in that community quite heavily. There's still a lot more work to do, otherwise we would not be bothering with a campaign like this.

Re: Flynn - Open Source PaaS powered by Docker

#20

My 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.
Post reply on HN