SoylentNews is people
SoylentNews
It seems weird that in this era of virtual everything that a number is hard to come by. The restrictions are real, however, because AWS restricts artificially the number of IP addresses you can bind to an interface on your VM. You have to buy a bigger VM to get more IP addresses, even if you don't need extra compute. Also, IPv6 is nowehre to be seen on the clouds, so addresses are more scarce than they need to be in the first place.
So the key problem is that you want to find a way to get tens or hundreds of IP addresses allocated to each VM.
Most workarounds to date have involved "overlay networking". You make a database in the cloud to track which IP address is attached to which container on each host VM. You then create tunnels between all the hosts so that everything can talk to everything. This works, kinda. It results in a mess of tunnels and much more complex routing than you would otherwise need. It also ruins performance for things like multicast and broadcast, because those are now exploding off through a myriad twisty tunnels, all looking the same.
The Fan is Canonical's answer to the container networking challenge.
Original Submission
(Score: 0) by Anonymous Coward on Wednesday June 24 2015, @05:06AM
The problem with AWS, and cloud anything for that matter, is that it has to be accessible remotely from anywhere. That is part of what makes it a cloud server. Private addressing moves it from PaaS to SaaS with a massive cut to what the server is worth.
(Score: 0) by Anonymous Coward on Thursday June 25 2015, @08:10AM
Right. 10.x.x.x can conflict. And it is not Internet accessible without a VPN. If you already have IPv6 in your home (this is not too uncommon these days), then you do not need the VPN.
People need VMs for serving IPv6 traffic. They can serve IPv4 traffic too, but if they do not have to, why bother giving them scarce IPv4 addresses.