4 ms·

5. You can’t upload a custom image and assign a Floating IP to the Droplet, one of the most basic of the functionality of any cloud.

jakelazaroff 6y ago
Just double-checked my DO console — yes you can, I have a droplet with both. Edit: I'm wrong, see below.
- bithavoc 6y ago
  Maybe we're talking about different things, docs here[0] > You cannot assign a Floating IP to a Droplet created from a custom image. Edit: I wanted to double-check because this would make my life so much easier, but no, I still can't use Floating IP with Custom Images. I imported a FlatcarLinux image from a URL and created a droplet; once the droplet launched, I still see this: > Floating IP: Disabled > Public IPv6 Address: Not available with custom images. [0]https://www.digitalocean.com/docs/images/custom-images/ https://www.digitalocean.com/docs/images/custom-images/
  - jakelazaroff 6y ago
    Interesting — checked again and what I'm using is actually a snapshot. Not sure why that makes a difference, sorry for the confusion.
    - dstick 6y ago
      I guess that would be a slightly laborous work around? Install vanilla linux, configure as needed. Save snapshot. Treat it as a custom image :)
      - bithavoc 6y ago
        Yeah, Snapshots work quite well, you can even transfer them between accounts and copy them between regions in the same account, but it's a "transfer" meant to be used as a migration mechanism, not distribution.
closeparen 6y ago
It seems like Amazon et al have full-fledged SDNs while DigitalOcean is a little more primitive. Even customer-level VLANs are new. Prior to that, "private networking" was just a way to save on transit quota; you shared a LAN with everyone else in the datacenter. Speculating and recalling old memories here, but: floating IP is implemented as an additional IP on an existing interface. DHCP can't assign multiple IPs for the same MAC. So there's got to be some DigitalOcean magic in the base images to figure out that a floating IP is assigned and configure the interface for it. You might be able to replicate this yourself, they just don't want to be responsible for support. Perhaps over time they will grow a more complex network fabric that will enable floating IPs to be their own DHCP-enabled interfaces straight on VMs, instead of the "dumb" forwarding rules they appear to be today. But also perhaps the lack of such things is why DigitalOcean is cheaper than Amazon.

jakelazaroff 6y ago

Just double-checked my DO console — yes you can, I have a droplet with both. Edit: I'm wrong, see below.

bithavoc 6y ago
Maybe we're talking about different things, docs here[0] > You cannot assign a Floating IP to a Droplet created from a custom image. Edit: I wanted to double-check because this would make my life so much easier, but no, I still can't use Floating IP with Custom Images. I imported a FlatcarLinux image from a URL and created a droplet; once the droplet launched, I still see this: > Floating IP: Disabled > Public IPv6 Address: Not available with custom images. [0]https://www.digitalocean.com/docs/images/custom-images/ https://www.digitalocean.com/docs/images/custom-images/
- jakelazaroff 6y ago
  Interesting — checked again and what I'm using is actually a snapshot. Not sure why that makes a difference, sorry for the confusion.
  - dstick 6y ago
    I guess that would be a slightly laborous work around? Install vanilla linux, configure as needed. Save snapshot. Treat it as a custom image :)
    - bithavoc 6y ago
      Yeah, Snapshots work quite well, you can even transfer them between accounts and copy them between regions in the same account, but it's a "transfer" meant to be used as a migration mechanism, not distribution.

closeparen 6y ago

It seems like Amazon et al have full-fledged SDNs while DigitalOcean is a little more primitive. Even customer-level VLANs are new. Prior to that, "private networking" was just a way to save on transit quota; you shared a LAN with everyone else in the datacenter. Speculating and recalling old memories here, but: floating IP is implemented as an additional IP on an existing interface. DHCP can't assign multiple IPs for the same MAC. So there's got to be some DigitalOcean magic in the base images to figure out that a floating IP is assigned and configure the interface for it. You might be able to replicate this yourself, they just don't want to be responsible for support. Perhaps over time they will grow a more complex network fabric that will enable floating IPs to be their own DHCP-enabled interfaces straight on VMs, instead of the "dumb" forwarding rules they appear to be today. But also perhaps the lack of such things is why DigitalOcean is cheaper than Amazon.