LBaaS v2 lack of migration

[changzhi]

===== Problem Description =====
Currently, many users used haproxy driver based LBaaS v2 in real production. LBaaS network traffic will break down if LBaaS v2 agent is dead. So we need migration of LBaaS instance.

===== How to resolve =====
We can add create / delete method in LBaaS agent schedule. And we need to record device driver which LBaaS instance used. So, we can migrate LBaaS instance to another LBaaS agent when one of LBaaS agent is dead.

[Nir Magnezi (nmagnezi)]

I suspect this was already handled by https://bugs.launchpad.net/octavia/+bug/1565511

[changzhi (changzhi)]

In our real production, we need to turn off the networks nodes where LBaaS agents run. In such scenario, we need to migrate LBaaS instance from one network node to another, just like L3 routers. In https://bugs.launchpad.net/octavia/+bug/1565511 , loadbalancers will be rescheduled from one network node to another when network node goes offline. I think that this is a passive method. We need a positive method, isn't it?

[changzhi (changzhi)]

Sometimes we need to reschedule loadbalancers manually when we need to maintain network nodes.

[OpenStack Infra (hudson-openstack)]

Change abandoned by Zhi Chang (<email address hidden>) on branch: master
Review: https://review.openstack.org/447177

[Gregory Thiemonge (gthiemonge)]

Abandoned after re-enabling the Octavia launchpad.