Hi Mihaela, Welcome to the Octavia club!
In an Ocata release you are correct that there is no API way to identify amphora related to a given load balancer. In the queens release we have introduced a new administrator API for amphora that provides the functionality you are looking for: https://developer.openstack.org/api-ref/load-balancer/v2/index.html#list-amphora By using the filter capabilities of our Octavia v2 API you can query the API for a list of amphora that are associated to a load balancer ID. Michael On Fri, Oct 13, 2017 at 1:51 AM, <mihaela.ba...@orange.com> wrote: > Hi, > > > > We are about to deploy Octavia (Ocata) in a multi-tenant Openstack > environment. All amphoras (for all tenants) will be spawned in a “service” > tenant. What is the easiest way to list the amphora instances of a certain > load balancer? As far as I could see, there is no API call returning such > result. The best way I can do it is by checking the security group > associated to the amphora port: the security group name includes the load > balancer ID. > > > > Thank you, > > Mihaela > > _________________________________________________________________________________________________________________________ > > Ce message et ses pieces jointes peuvent contenir des informations > confidentielles ou privilegiees et ne doivent donc > pas etre diffuses, exploites ou copies sans autorisation. Si vous avez recu > ce message par erreur, veuillez le signaler > a l'expediteur et le detruire ainsi que les pieces jointes. Les messages > electroniques etant susceptibles d'alteration, > Orange decline toute responsabilite si ce message a ete altere, deforme ou > falsifie. Merci. > > This message and its attachments may contain confidential or privileged > information that may be protected by law; > they should not be distributed, used or copied without authorisation. > If you have received this email in error, please notify the sender and > delete this message and its attachments. > As emails may be altered, Orange is not liable for messages that have been > modified, changed or falsified. > Thank you. > > > __________________________________________________________________________ > 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 > __________________________________________________________________________ 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
