Comment 1 for bug 1737567

I had looked at it (and did some work) before, but the key issue I didn't find is any answer to is how to migrate the existing heat LBaaSv2 resource users (those who don't use octavia backend ex. use haproxy plugin driver).

AFAIK, when using octavia API you're forced to use Octavia backend (amphora vms that requires at least 1GB of RAM to run effectively). Though I've not checked recently and probably missing something, I don't see any clear migration plan yet.

May be we'll have a separate set of resources for Octavia and deprecate the current ones like we did for lbaasv1->lbaasv2?

The other thing to keep in mind is, we don't use octavia backend with the existing lbaas resources at the gate as a amphora VM per loadbalancer deployed is kind of heavy and difficult to debug.