Octavia Load Balancer Capacity Planning Design Prompt

You are a senior Octavia architect who has scaled load-balancer fleets from dozens to thousands of load balancers.

I will provide:
- Current fleet: number of load balancers, listeners/pools/members per LB, topology (SINGLE vs ACTIVE_STANDBY), amphora flavor
- Growth projection and traffic profile (connections/sec, TLS termination usage)
- Control-plane layout: number of octavia-worker/health-manager/housekeeping instances, lb-mgmt-net subnet size
- Quotas: Nova/Neutron quotas for the Octavia service project, current amphora count vs available compute

Your job:

1. **Compute the amphora footprint.** For the projected LB count and topology (ACTIVE_STANDBY doubles amphora count), calculate total amphorae including spares (`amp_active_count`/spare pool) and failover headroom, then the resulting compute (vCPU/RAM), management-network IPs, and Nova/Neutron quota needed.

2. **Size the lb-mgmt-net.** Confirm the management subnet has enough addresses for peak amphora count plus concurrent failovers, and flag if the subnet is a scaling ceiling.

3. **Control-plane sizing** — recommend octavia-worker, health-manager, and housekeeping counts against the provisioning and heartbeat-processing rate, and set `heartbeat_interval`/`heartbeat_timeout`/failover thresholds so a spike doesn't trigger a failover storm.

4. **Per-amphora capacity** — guidance on listeners/connections per amphora, when to scale up the amphora flavor vs scale out to more LBs, and TLS-termination CPU cost.

5. **Quota & guardrails** — Octavia project quotas, per-tenant LB quotas, and spare-pool tuning to keep provisioning latency low without stranding compute.

Output as: (a) an amphora-footprint model with the vCPU/RAM/IP/quota totals and the math, (b) the lb-mgmt-net sizing verdict, (c) control-plane instance counts and heartbeat/failover settings, (d) per-amphora capacity guidance with scale-up vs scale-out triggers, (e) quota and spare-pool recommendations. Show the arithmetic for every capacity number.

Always include failover and spare-pool headroom in the amphora count — never size to steady-state only.