← Back to team overview

yahoo-eng-team team mailing list archive

[Bug 1453791] Re: Lbaas Pool and Members from Different SubNets

 

It's simple to add some limitation to ensure VIP and members are from
same subnet of pool. But I think it's not a good idea to do that.

I did a test, in my case, at first, I got VIP and some members from
pool's subnet, later I created a new subnet, connect it with previous
subnet by a router, and add members from the new subnet to pool. The
client can get response from both from previous members and new members.

So I think to limit members must from the same subnet is not a good
idea, and checking whether members' subnets are accessible to VIP will
make things complex.

** Changed in: neutron
       Status: New => Invalid

** Changed in: neutron
     Assignee: ZongKai LI (lzklibj) => (unassigned)

-- 
You received this bug notification because you are a member of Yahoo!
Engineering Team, which is subscribed to neutron.
https://bugs.launchpad.net/bugs/1453791

Title:
  Lbaas Pool and Members from Different SubNets

Status in OpenStack Neutron (virtual network service):
  Invalid

Bug description:
  
  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.

To manage notifications about this bug go to:
https://bugs.launchpad.net/neutron/+bug/1453791/+subscriptions