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.
Cheers, Lubosz On Mar 16, 2017, at 5:39 AM, zhi <changzhi1...@gmail.com<mailto:changzhi1...@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, loadbalancer_id): self._unschedule_loadbalancer(context, loadbalancer_id, agent_id) The question is, how do I notify LBaaS agent? Hope for your reply. Thanks Zhi Chang __________________________________________________________________________ OpenStack Development Mailing List (not for usage questions) Unsubscribe: openstack-dev-requ...@lists.openstack.org<mailto: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
