Hi all, In our cloud we have a non Octavia LoadBalancer provided by vendor with no possibility to get it replaced with real Octavia. I see there is possibility to provide drivers for Octavia to operate other types of load balancers (https://docs.openstack.org/octavia/latest/contributor/guides/providers.html <https://docs.openstack.org/octavia/latest/contributor/guides/providers.html>), but there are still some issues/questions: - is it possible to make Octavia only expose it’s API and make the driver transpose calls into the internal LB - there is no need for any data persistency on the Octavia side, since there are other interfaces to operate LB what will cause inconsistences otherwise - can the driver have access to the API user data (user sends X-Auth-Token, it gets validated by keystonemiddleware, but I need to pass extra info to the underlaying internal LB API). Here I do not need anything special, it is more or less get access to the used token to pass it further. Ideally auth can be offloaded completely to the underlaying LB This all sounds like writing simple API convertor, but we really want service behaviour is 100% compatible to Octavia to avoid further issues (and perhaps convincing Octavia can replace other solution). Is this achievable? If yes I would really appreciate technical hints how this can be implemented. I feel like Octavia is already covering such use case (or at least intend to do so), but I am lost in docs. Thanks in advance, Artem