How to allocate floating IP addresses

How-to · Updated Jun 2026

Coming from another cloud?

▸AWS·Elastic IP addresses

Elastic IP addresseshigh

AWS charges idle EIPs.
OpenStack floating IPs free/pool-limited.
AWS regional instance/ENI.
OpenStack project port.

AWS docs ↗

▸Azure·Public IP addresses

Public IP addresseshigh

Public IP is a dedicated ARM resource with SKUs (Basic/Standard); IPv4 billed, IPv6 free ().
Static/dynamic allocation (Standard static only); zone-redundant option (Standard v2).
Associated directly to NIC/LB/gateway vs via router DNAT in OpenStack.
Dynamic outbound uses ephemeral IPs even without assoc; no pool allocation like Neutron external nets.

Azure docs ↗

▸DigitalOcean·Reserved IPs (formerly Floating IPs)

Reserved IPs (formerly Floating IPs)medium

Naming/API surface: DigitalOcean renamed Floating IPs to Reserved IPs; endpoints and fields change from `floating_ips` to `reserved_ips` (while legacy endpoints existed until a stated deprecation window), whereas OpenStack retains the “floatingip” resource in Neutron APIs ().
Identity model: DigitalOcean’s resource identifier in the API path is the IP address itself (`/v2/reserved_ips/{reserved_ip}` where `{reserved_ip}` is an IPv4 address), whereas OpenStack commonly uses UUID identifiers for Neutron resources like floating IPs and ports ().
Attachment model: creation requires either `droplet_id` or `region` and reassignment is conceptually “map to a Droplet”; OpenStack associates floating IPs to Neutron ports (and thus can be used with more complex networking constructs like routers), which is a different mental model for migrating users ().
Region binding: DigitalOcean Reserved IPs are explicitly bound to a region, while OpenStack floating IP pools are usually defined per external network and can be consumed wherever that external network is reachable (implementation-specific) ().

DigitalOcean docs ↗

▸Google Cloud·Static External IP

Static External IPhigh

GCP static IPs are regional or global resources, with unassociated IPs metered per-hour; OpenStack floating IPs are pool-based. See the GCP pricing page for current rates.
GCP supports both ephemeral (auto-released on stop) and static IPs; OpenStack floating IPs are always explicit.
GCP global static IPs used with global load balancers only; no direct OpenStack equivalent.

Google Cloud docs ↗

▸Hetzner·Floating IPs

Floating IPshigh

Flat monthly billing €3/IPv4 or hourly equivalent, not usage-based per hour ().
Locked to specific location/zone, cannot move across datacenters unlike global pools in OpenStack ().
Hot-reassign without server reboot but requires manual OS config (e.g., ifupdown/netplan) post-change ().
Limits: 10/account default, 20/server max; single assignment at a time ().

Hetzner docs ↗

How to allocate floating IP addresses

Floating IPs are public IP addresses that you can assign to instances on private networks. Allocate a floating IP from the public pool, then associate it with an instance to make it reachable from the internet.

Prerequisites

ConsoleLogged in to the Quake AI console
CLIOpenStack CLI installed and authenticated (clouds.yaml or openrc sourced)
APIAPI token generated with $OS_TOKEN and service endpoint variables set
TerraformOpenTofu installed with Quake AI provider configured

Windows: CLI examples use bash. Set up a Linux CLI environment on Windows before proceeding.

You need an instance on a private network with a router connected to the PublicStatic external network.

Allocate a floating IP#

Select Network > Floating IPs > Allocate IP.
In the Allocate IP dialog, choose the source pool from the Network dropdown (for example, PublicStatic).
After you choose a Network, an optional Owned Subnet dropdown appears. Leave it blank to allocate from the network's default pool, or select a subnet to constrain which subnet inside the chosen network the floating IP comes from.
Optionally toggle Batch Allocate on to allocate multiple IPs at once. When the toggle is on, a required Count field appears; enter the number of floating IPs to allocate.
Optionally enter a Description.
Select OK to allocate.

Associate the floating IP with an instance#

Go to Compute > Instances.
Find your instance. The row exposes five action icons (Console, Instance Status, Volumes, Networking, Settings). Open the Networking icon dropdown and select Associate Floating IP.
In the Instance IP table, select the radio button next to the private IP listed for the instance. The Floating IP Address table populates only after you select an instance IP.
In the Floating IP Address table, select the radio button next to the floating IP you allocated. To allocate a new IP from this dialog instead, select + Allocate IP.
Select OK.

Verify the result#

Navigate to Network > Floating IPs. The floating IP row shows its associated Fixed IP (the instance's private IP) and Associated Port UUID, with Status moving from Down to Active. The list does not show the instance name. To see it, open Compute > Instances, where the floating IP appears under the instance's Floating IP column.

Usage Guidelines

The sample code, software libraries, command line tools, proofs of concept, templates, and other related technology on this page (including any of the foregoing that is provided by Quake AI personnel) is provided to you as Quake AI Content under the Quake AI Customer Agreement, or the relevant written agreement between you and Quake AI (whichever applies). Do not use this Quake AI Content in your production accounts, or on production or other critical data. You are responsible for testing, securing, and optimizing the Quake AI Content (such as sample code) as appropriate for production grade use based on your specific quality control practices and standards. Deploying Quake AI Content may incur Quake AI charges for creating or using Quake AI chargeable resources, such as running Compute instances or storing data in Object Storage. Your use is also subject to the Acceptable Use Policy.

For the full policy, see Usage Guidelines.

Last validated: 04.06.2026

Was this page helpful?

How to allocate floating IP addresses

How to allocate floating IP addresses

Allocate a floating IP#

Associate the floating IP with an instance#

Verify the result#

See also#

Usage Guidelines

See Also