I didn't know current lbaas plugin has such limitation. Although I think the UI should not incur such limitation as the lbaas API definition does allow this, I'm fine with it.
Thanks, -Kaiwei ----- Original Message ----- From: "Eugene Nikanorov" <enikano...@mirantis.com> To: "OpenStack Development Mailing List" <openstack-dev@lists.openstack.org> Sent: Tuesday, September 24, 2013 2:00:33 AM Subject: Re: [openstack-dev] [LBaaS][Horizon] Subnet for VIP? Hi Fank, That looks like Horizon limitation that is bound to current reference implementation of lbaas service where VIP should be on a subnet where pool's memebers are. So it's not a bug. Expect this to change in Icehouse. Thanks, Eugene. On Tue, Sep 24, 2013 at 9:19 AM, < f...@vmware.com > wrote: Hi, When adding a VIP for this pool, we suppose to specify the subnet which the VIP will be on. However, the Horizon UI forces us to provide an IP address for the VIP from the subnet which we used to create the pool. That subnet for pool is supposed to be the subnet for pool's members, not the subnet for the VIP. This looks like a UI bug? Thanks, -Kaiwei _______________________________________________ OpenStack-dev mailing list OpenStack-dev@lists.openstack.org http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev _______________________________________________ OpenStack-dev mailing list OpenStack-dev@lists.openstack.org http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev
_______________________________________________ OpenStack-dev mailing list OpenStack-dev@lists.openstack.org http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev
