[Bug 1453791] [NEW] Lbaas Pool and Members from Different SubNets

[Launchpad Bug Tracker]

You have been subscribed to a public bug:


There is no definite mapping between Pool Subnet ID and Its Members.

It is possible to Assign another Subnet with different IP for Pool and
its members.

For E.g

A pool is created with subnet 135.254.189.0/24, and its members from
Instances assigned to Another Subnet (172.21.184.0/24).

Under the following reference,

https://etherpad.openstack.org/p/neutron-lbaas-api-proposals

For Create-Pool,

Request
POST /pools.json
{
    'pool': {
        'tenant_id': 'someid',
        'name': 'some name',
        'subnet_id': 'id-of-subnet-where-members-reside',      -------> The Subnet must be defined as per the instances Subnet
        'protocol': 'HTTP',
        'lb_method': 'ROUND_ROBIN'
        'admin_state_up': True,
    }
}


Validation needs to be done such that the instances ( Members ) are created for the Pool of the same Subnet.

** Affects: neutron-lbaas (Ubuntu)
     Importance: Undecided
         Status: New

-- 
Lbaas Pool and Members from Different SubNets
https://bugs.launchpad.net/bugs/1453791
You received this bug notification because you are a member of Ubuntu Server Team, which is subscribed to neutron-lbaas in Ubuntu.