Thanks Bharath for replying. But when I add members , I can successfully specify a member ip address from a different pool than the subnet when creating pool, hence the confusion. And theoretically, why would members for a pool have to belong to the same subnet?
Date: Tue, 28 Apr 2015 17:50:16 -0700 From: bharath.stac...@gmail.com To: openstack-dev@lists.openstack.org Subject: Re: [openstack-dev] [Neutron][LBaaS] Why do we need to select subnet when creating a pool? Hi Wanjing, As it's Juno, I assume you are using LBaaSv1. If that's the case, as Brandon pointed, there's no subnet-id switch in the "neutron lb-member-create" command. Having said that you still use the subnet-id in both the following commands:neutron lb-pool-createneutron lb-vip-create You should note that the subnet id in each of the above commands serve different purpose. In the case of "lb-pool-create", the subnet-id is provided to make sure that only members belonging to the specified subnet-id could be added to the pool. However, the subnet id in the "lb-vip-create" command specifies the network range from which an ip is chosen to be assigned as a vip. Thus, you could use different subnets for both the above commands and as long as you have route between those two, the load balancing works. Thanks,Bharath. On Tue, Apr 28, 2015 at 9:19 AM, Brandon Logan <brandon.lo...@rackspace.com> wrote: So someone pointed out that you were using lbaas for Juno, which would mean you aren't using LBaaS V2. So you're using V1. V1 member's do not take subnet_id as an attribute. Let me know how you are making your requests. Thanks, Brandon From: Brandon Logan <brandon.lo...@rackspace.com> Sent: Monday, April 27, 2015 8:40 PM To: OpenStack Development Mailing List not for usage questions Subject: Re: [openstack-dev] [Neutron][LBaaS] Why do we need to select subnet when creating a pool? I'm assuming you are using LBaaS V2. With that assumption, I'm not sure how you are having to select subnet on the pool. It's not supposed to be a field at all on the pool object. subnet_id is required on the member object right now, but that's something I and others think should just be optional, and if not specified then it's assumed that member can be reached with whatever has already been setup. Another option is pool could get a subnet_id field in the future and all members that are created without subnet_id are assumed to be on the pool's subnet_id, but I'm getting ahead of myself and this has no bearing on your current issue. Could you tell me how you are making your requests? CLI? REST directly? From: Wanjing Xu <wanjing...@hotmail.com> Sent: Monday, April 27, 2015 12:57 PM To: OpenStack Development Mailing List not for usage questions Subject: [openstack-dev] [Neutron][LBaaS] Why do we need to select subnet when creating a pool? So when I use Haproxy for LBaaS for Juno, there is a subnet mandatary field that I need to fill in when creating a pool, and later on when I add members, I can use a different subnet(or simply just enter the ip of the member), when adding vip, I can still select a third subnet. So what is the usage of the first subnet that I used to create pool? There is no port created for this pool subnet. I can see that a port is created for the vip subnet that the loadbalancer instance is binding to. Regards! Wanjing Xu __________________________________________________________________________ OpenStack Development Mailing List (not for usage questions) Unsubscribe: openstack-dev-requ...@lists.openstack.org?subject:unsubscribe http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev __________________________________________________________________________ OpenStack Development Mailing List (not for usage questions) Unsubscribe: openstack-dev-requ...@lists.openstack.org?subject:unsubscribe http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev
__________________________________________________________________________ OpenStack Development Mailing List (not for usage questions) Unsubscribe: openstack-dev-requ...@lists.openstack.org?subject:unsubscribe http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev
