4455759f45
Create loadbalancer accepts either a vip_subnet_id
or vip_network_id. If vip_network_id is provided the
vip port is created on that network using the default
neutron behavior. If neutron assigns multiple fixed ips,
an ipv4 addresses is chosen as the vip in preference to
ipv6 addresses.
-----
Who would use the feature?
LBaaS users on a network with multiple subnets
Why use the feature?
Large deployments may have many subnets to allocate
vip addresses. Many of these subnets might have
no addresses remaining to allocate. Creating a
loadbalancer by network selects a subnet with an
available address.
What is the exact usage for the feature?
POST /lbaas/loadbalancers
Host: lbaas-service.cloudX.com:8651
Content-Type: application/json
Accept: application/json
X-Auth-Token:887665443383838
{
"loadbalancer": {
"name": "loadbalancer1",
"description": "simple lb",
"tenant_id": "b7c1a69e88bf4b21a8148f787aef2081",
"vip_network_id": "a3847aea-fa6d-45bc-9bce-03d4472d209d",
"admin_state_up": true
}
}
DocImpact: 2.0 API Create a loadbalancer attributes
APIImpact
Closes-Bug: #1465758
Change-Id: I31f10581369343fde7f928ff0aeb1024eb752dc4
|
||
|---|---|---|
| .. | ||
| __init__.py | ||
| healthmonitor_max_retries_down.py | ||
| l7.py | ||
| lb_graph.py | ||
| lb_network_vip.py | ||
| lbaas_agentschedulerv2.py | ||
| loadbalancerv2.py | ||
| sharedpools.py | ||