Additional IPv4 addresses

Quake AI concept: Floating IPs

• Linode does not model this as a separate Neutron floating IP pool resource. The canonical guide describes adding, deleting, transferring, and sharing IPs from a Linode's Network tab, rather than allocating a project-scoped floating address that can be associated independently of the server. Manage IP addresses on a Linode
• Additional IPv4 addresses require technical justification and may require opening a Support Ticket, which is not how OpenStack Neutron floating IPs are normally provisioned. The guide also says pricing for additional public IPv4 addresses may vary by region and that these addresses are limited by IPv4 exhaustion. Manage IP addresses on a Linode
• Linode public IPv4s are typically attached directly to a Linode at creation, and a Linode created with a VPC interface usually has no public IPv4 unless the user explicitly selects Assign a public IPv4 address. That differs from OpenStack's separate floating-IP association flow, where a server's fixed address and floating address are distinct resources. Manage IP addresses on a Linode
• Linode exposes IP Transfer and IP Sharing workflows for IPv4s. IP Transfer is limited to Linodes in the same data center, and IP Sharing can assign the same IP to two Linodes for failover, which is not the same lifecycle as OpenStack floating IP association and disassociation. Manage IP addresses on a Linode