[openstack-dev] [Neutron][LBaaS][Octavia] Should subnet be optional on member create?
SamuelB at Radware.com
Sun Jan 17 08:14:02 UTC 2016
Subnet should be mandatory
The only thing this makes supporting load balancing servers which are not running in the cloud more challenging to support.
But I do not see this as a huge user story (lb in cloud load balancing IPs outside the cloud)
From: Brandon Logan [mailto:brandon.logan at RACKSPACE.COM]
Sent: Saturday, January 16, 2016 6:56 AM
To: openstack-dev at lists.openstack.org
Subject: [openstack-dev] [Neutron][LBaaS][Octavia] Should subnet be optional on member create?
I filed a bug  a while ago that subnet_id should be an optional parameter for member creation. Currently it is required. Review  is makes it optional.
The original thinking was that if the load balancer is ever connected to that same subnet, be it by another member on that subnet or the vip on that subnet, then the user does not need to specify the subnet for new member if that new member is on one of those subnets.
At the midcycle we discussed it and we had an informal agreement that it required too many assumptions on the part of the end user, neutron lbaas, and driver.
If anyone wants to voice their opinion on this matter, do so on the bug report, review, or in response to this thread. Otherwise, it'll probably be abandoned and not done at some point.
OpenStack Development Mailing List (not for usage questions)
Unsubscribe: OpenStack-dev-request at lists.openstack.org?subject:unsubscribe
More information about the OpenStack-dev