The scenario might go something like this:
* Define a network for the hardware load balancers (as Kris mentioned above).
* Add and define subnets for this network as demand necessitates.
* Either refactor or craft lbaas API that takes network ID.
* Call the /v2.0/network_ip_availability/{lbaas-network-id} to get availability for our lbaas network
* Iterate the availability subnet children and choose the subnet with the greatest capacity
* Use that for the subnet_id
This might become more practical if/when network_ ip_availability API releases: https:/ /review. openstack. org/#/c/ 212955
The scenario might go something like this: ip_availability /{lbaas- network- id} to get availability for our lbaas network
* Define a network for the hardware load balancers (as Kris mentioned above).
* Add and define subnets for this network as demand necessitates.
* Either refactor or craft lbaas API that takes network ID.
* Call the /v2.0/network_
* Iterate the availability subnet children and choose the subnet with the greatest capacity
* Use that for the subnet_id