[RFE] Add the ability to create lb vip and member with network_id

Assuming the new fields are optional, go for it.

Unless someone else is really wanting this, as the original requester for this, I don't think this is somethign that is necessary anymore. It leads down a rat hole that I am not prepared to go down. You can take it off mitaka-1 if you would like.

Ok, thanks for the feedback, much appreciated.

[Expired for neutron because there has been no activity for 60 days.]

I want this functionality as well. We have hardware load balancers that have 100's if not 1000's of vips. Trying to correctly guess the initial subnet size and then not being able to grow the subnet makes this highly impractical. Allowing us to specify the network_ID to use for the load balancer creation and then the plugin choosing the subnet that has available IP's is a much better route. It also aligns to how floating ip's work in neutron.

This allows us to add subnets to the lbaas network pool dynamically and eliminates people needing to know the capacity levels on each specific subnet. It also eliminates the confusion and frustration of trying multiple times with different subnets before they get an LB that can provision. Furthermore their is no API for people to be able to get subnet capacity, so in large deployments this becomes highly impractical and frustrating.

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:
* 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

Not sure why this didn't get auto-linked: https://review.openstack.org/#/c/363302/

Reviewed: https://review.openstack.org/363302
Committed: https://git.openstack.org/cgit/openstack/neutron-lbaas/commit/?id=4455759f4506a43d70f811a32ee60b13af6afd8d
Submitter: Jenkins
Branch: master

commit 4455759f4506a43d70f811a32ee60b13af6afd8d
Author: Cedric Shock <email address hidden>
Date: Mon Aug 29 23:46:55 2016 +0000

    Allow creating loadbalancer with network_id

    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

This issue was fixed in the openstack/neutron-lbaas 9.0.0.0rc1 release candidate.