3 ms·
I still don't get it. Cloud services are a recent thing, and they are bringing hundreds of servers online every day. This is prime territory for ipv6.
by gpvos 12y ago
I still don't get it. Cloud services are a recent thing, and they are bringing hundreds of servers online every day. This is prime territory for ipv6.
- Symbiote 12y agoI took my first look at Google's offering last week. You can set up a MySQL database, which has an IPv6 address by default. The documentation[1] says > Each instance has an IPv6 address that is free to use. To connect over IPv4, > you must explicitly assign an IPv4 addresss to your instance, which incurs a > charge per hour idle. IPv4 sounded like a hassle, so I tried to use the IPv6 address from my Google Compute Engine instance. But that doesn't support IPv6. It's the oldest outstanding feature request [2]. (Perhaps other parts of Google's cloud offering support IPv6, I haven't used much else so far.) [1] https://cloud.google.com/sql/docs/mysql-client#connect-ipv6 https://cloud.google.com/sql/docs/mysql-client#connect-ipv6 [2] https://code.google.com/p/google-compute-engine/issues/detail?id=8 https://code.google.com/p/google-compute-engine/issues/detai...
- toomuchtodo 12y ago> I still don't get it. Cost/benefit. Your internal virtual machines don't need IPv6 addresses, only where you're terminating to the outside world (usually ELBs, but sometimes public addresses). For the vast majority of AWS users, the status quo is sufficient.