Skip to main content

​
Overview

Flavor profiles define the compute capacity and topology configuration allocated to load balancing appliances. Administrators create named flavors that users select at load balancer provisioning time. Flavors abstract provider-specific settings into human-readable capacity tiers — e.g., standard, ha, and high-performance.
Administrator Access Required — This operation requires the admin role. Contact your Xloud administrator if you do not have sufficient permissions.

​
Flavor Architecture

ConceptDescription
Flavor ProfileProvider-specific settings template (topology, compute class, etc.)
FlavorNamed, user-visible tier based on a flavor profile. Users select flavors at provisioning.
A flavor profile is always associated with a specific provider. Multiple flavors can reference the same profile.

​
Create a Flavor Profile

Create a flavor profile

A flavor profile wraps provider-specific settings:
Create standard single-topology profile
openstack loadbalancer flavorprofile create \
  --name standard-profile \
  --provider amphora \
  --flavor-data '{"loadbalancer_topology": "SINGLE"}'
Create HA active-standby profile
openstack loadbalancer flavorprofile create \
  --name ha-profile \
  --provider amphora \
  --flavor-data '{"loadbalancer_topology": "ACTIVE_STANDBY"}'

Create named flavors for users

Expose profiles as named flavors:
Create standard flavor
openstack loadbalancer flavor create \
  --name standard \
  --flavorprofile standard-profile \
  --description "Standard single-instance load balancer" \
  --enable
Create HA flavor
openstack loadbalancer flavor create \
  --name ha \
  --flavorprofile ha-profile \
  --description "High-availability active-standby load balancer" \
  --enable

Verify flavors are available

List available flavors
openstack loadbalancer flavor list
Flavors appear in the list with status enabled — you can now select them when creating a load balancer.

​
Flavor Profile Settings Reference

SettingProviderDescription
loadbalancer_topologyamphoraSINGLE or ACTIVE_STANDBY
compute_flavoramphoraNova flavor for the appliance instance
amp_image_tagamphoraTag identifying the appliance image in the Image Service
availability_zoneamphoraRestrict appliance placement to a specific AZ

​
Manage Flavors

openstack loadbalancer flavor list
Disabling a flavor prevents new load balancers from using it but does not affect existing load balancers. Deleting a flavor profile that is referenced by a flavor will fail — delete the flavor first.
For most production deployments, provide at least two flavors:
Flavor NameProfileUse Case
standardSingle topologyDevelopment, testing, non-critical workloads
haActive-standbyProduction workloads requiring high availability

​
Next Steps

Provider Drivers

Understand provider-specific flavor profile settings.

Quotas

Control how many load balancers projects can provision across all flavors.

Architecture

Understand how appliance topology affects data plane resilience.

Admin Troubleshooting

Diagnose flavor-related provisioning failures.