For the Octavia Amphora provider, at present, it only supports "loadbalancer_topology" (SINGLE or ACTIVE_STANDBY). Would it be possible to add more flavor capabilities?, in this case the request is to add the capability were by we could select a specific nova-flavor. Some use cases for this feature: - If 90% of your Octavia LBs handle very little traffic, the could use a normal/small nova flavor, but the other 10% that handle lots of traffic and would need more resources, could use a nova flavor with higher CPU/RAM specs. - In some cases OSP is using Host Aggregates via nova flavors, for example Prod and Prepro and for segregation reasons you need to run the LB for each environment in the same hypervisors(HA) as their pool members. - If you had a case were you would like to deploy a small set of your loadbalancers with a specific configuration for example CPU-pinning, SR-IOV or DPDK for performance reasons, you would also make use of host aggregates and other flavor properties(mem_page_size, cpu_policy, etc).
Feature already implemented in upstream octavia, but tempest tests are needed for full support.