[openstack-dev] [neutron][lbaasv2] Migrate LBaaS instance
German.Eichberger at rackspace.com
Tue Mar 21 00:15:13 UTC 2017
We completely understand that operators are still on older versions of OpenStack and we are executing against the OpenStack release series
 and we adhere to the support phases as outlined in . So any new features will only be added to Pike whereas bug fixes will be carried back right now Ocata and Newton will only see Security Patches. If this doesn’t meet your needs I would encourage you to get those guidelines changed. We also frequently seek input from operators on new features and/or pain points. I am curious what the use case is for a non-scalable/non-HA load balancer like the namespace/haproxy driver in production.
Us deprecating LBaaS V2 won’t relieve us from our obligation to provide bug fixes and security fixes to the previous versions - furthermore we learned from the LBaaS V1 migration and we are committed to providing migration scripts for Octavia and potentially the namespace driver. We might need to do a better job articulating our migration strategy.
On 3/17/17, 7:54 AM, "Saverio Proto" <saverio.proto at switch.ch> wrote:
I am just back from the Ops Midcycle where Heidi Joy Tretheway reported
some data from the user survey.
So if we look at deployments with more than 100 servers NO ONE IS USING
NEWTON yet. And I scream this loud. Everyone is still in Liberty or Mitaka.
I am just struggling to upgrade to LBaaSv2 to hear that is already going
into deprecation. The feature Zhi is proposing is important also for me
once I go to production.
I would encourage devs to listen more to operators feedback. Also you
devs cant just ignore that users are running still Liberty/Mitaka so you
need to change something in this way of working or all the users will
On 16/03/17 16:26, Kosnik, Lubosz wrote:
> Hello Zhi,
> Just one small information. Yesterday on Octavia weekly meeting we
> decided that we’re gonna add new features to LBaaSv2 till Pike-1 so the
> windows is very small.
> This decision was made as LBaaSv2 is currently Octavia delivery, not
> Neutron anymore and this project is going into deprecations stage.
>> On Mar 16, 2017, at 5:39 AM, zhi <changzhi1990 at gmail.com
>> <mailto:changzhi1990 at gmail.com>> wrote:
>> Hi, all
>> Currently, LBaaS v2 doesn't support migration. Just like router
>> instances, we can remove a router instance from one L3 agent and add
>> it to another L3 agent.
>> So, there is a single point failure in LBaaS agent. As far as I know,
>> LBaaS supports " allow_automatic_lbaas_agent_failover ". But in many
>> cases, we want to migrate LBaaS instances manually. Do we plan to do this?
>> I'm doing this right now. But I meet a question. I define a function
>> in agent_scheduler.py like this:
>> def remove_loadbalancer_from_lbaas_agent(self, context, agent_id,
>> self._unschedule_loadbalancer(context, loadbalancer_id, agent_id)
>> The question is, how do I notify LBaaS agent?
>> Hope for your reply.
>> Zhi Chang
>> OpenStack Development Mailing List (not for usage questions)
>> Unsubscribe: OpenStack-dev-request at lists.openstack.org
>> <mailto:OpenStack-dev-request at lists.openstack.org>?subject:unsubscribe
> OpenStack Development Mailing List (not for usage questions)
> Unsubscribe: OpenStack-dev-request at lists.openstack.org?subject:unsubscribe
Saverio Proto, Peta Solutions
Werdstrasse 2, P.O. Box, 8021 Zurich, Switzerland
phone +41 44 268 15 15, direct +41 44 268 1573
saverio.proto at switch.ch, http://www.switch.ch
OpenStack Development Mailing List (not for usage questions)
Unsubscribe: OpenStack-dev-request at lists.openstack.org?subject:unsubscribe
More information about the OpenStack-dev