3 ms·
"Facebook’s private IP space conflicts with that of EC2" ^ That wouldn't've happened in GCE (i.e., they should have been acquired by Google).
by maceip 12y ago
"Facebook’s private IP space conflicts with that of EC2"
^ That wouldn't've happened in GCE (i.e., they should have been acquired by Google).
- cheeseprocedure 12y agoAre you sure? This document suggests GCE instances use the 10.x.x.x address space (just as AWS instances in EC2 Classic do): https://developers.google.com/compute/docs/instances-and-network https://developers.google.com/compute/docs/instances-and-net...
- maceip 12y ago""" Although Compute Engine doesn't allow creating an instance with a user-defined local IP address, you can use a combination of routes and an instance's ‑‑can_ip_forward ability to add local IP address as a network static address which then maps to your desired virtual machine instance. For example, if you want to assign 10.1.1.1 specifically as a network address to a virtual machine instance, you can create a static network route that sends traffic from 10.1.1.1 to your instance, even if the instance's network address assigned by Compute Engine doesn't match your desired network address. """ Meaning they could have avoided conflicts using this mechanism.
- cheeseprocedure 12y agoMaintaining thousands of forwarding/routing configs sounds just as nasty as implementing Neti. At any rate, Instagram's been around since 2010 and GCE didn't exist until June 2012 (and wasn't generally available until this past December).