Skip to main content

Overview

A pool is a collection of backend member instances that receive traffic from a listener. Pools define how traffic is distributed across members (algorithm), whether sessions are sticky (persistence), and which protocol the pool uses internally. Each listener has a default pool; additional pools can be used for L7 policy-based routing.
Prerequisites
  • An active Xloud account with appropriate permissions
  • Access to the Xloud Dashboard (https://connect.<your-domain>) or CLI configured with credentials
  • API credentials sourced (source admin-openrc.sh)

Distribution Algorithms

AlgorithmDescriptionBest For
ROUND_ROBINDistributes requests evenly across all UP membersStateless applications with equal capacity members
LEAST_CONNECTIONSSends new requests to the member with fewest active connectionsLong-lived connections with variable request duration
SOURCE_IPRoutes requests from the same client IP to the same memberStateful applications without cookie-based persistence
SOURCE_IP_PORTRoutes based on client IP + port combinationSymmetric NAT environments requiring deterministic mapping

Create a Pool

Navigate to Pools tab

Open your load balancer in Project → Network → Load Balancers and select the Pools tab. Click Create Pool.

Configure the pool

FieldDescription
NamePool display name
ProtocolMust match or be compatible with the listener protocol
AlgorithmTraffic distribution method
Session PersistenceSticky session configuration (optional)

Add members

After pool creation, select the pool and click the Members sub-tab. Click Add Member to register backend instances.
FieldDescription
IP AddressBackend instance IP
Protocol PortPort your application listens on
WeightRelative traffic weight (default: 1)
Monitor Address/PortOverride health check target if different from member address

Manage Pool Members

Navigate to your pool and click the Members sub-tab. Use Add Member to register instances and Delete to remove members that are decommissioned.

Session Persistence

Session persistence routes subsequent requests from the same client to the same backend member, enabling stateful applications to work behind the load balancer.

Update Pool Settings

Change distribution algorithm
openstack loadbalancer pool set pool-http \
  --lb-algorithm LEAST_CONNECTIONS
Remove session persistence
openstack loadbalancer pool set pool-http \
  --no-session-persistence

Next Steps

Health Monitors

Configure health probes to automatically remove unhealthy members from pools.

Listeners

Configure the listeners that route traffic to your pools.

Create Load Balancer

Full walkthrough for creating a load balancer with pool and health monitor.

Troubleshooting

Resolve member OFFLINE status and pool connectivity issues.