Thank you for the information, Because, I aim to manage it via dashboard and one more thing that if I use ACTIVE STANDBY topology, its IP is not sequential. Nguyen Huu Khoi
On Thu, Feb 9, 2023 at 1:48 PM Gregory Thiemonge gthiemonge@redhat.com wrote:
Hi,
If you're talking about the Amphorae instances, you can use the loadbalancer amphora API or CLI to get the IDs of the Octavia Amphorae:
For instance: $ openstack loadbalancer amphora list --loadbalancer lb1
+--------------------------------------+--------------------------------------+-----------+------------+---------------+-------------+ | id | loadbalancer_id | status | role | lb_network_ip | ha_ip |
+--------------------------------------+--------------------------------------+-----------+------------+---------------+-------------+ | 3973f489-4820-4c52-a506-4ebb5ea9d334 | 46eb4f44-9785-4090-9b1a-f8f390cc539e | ALLOCATED | STANDALONE | 192.168.0.148 | 172.24.4.96 |
+--------------------------------------+--------------------------------------+-----------+------------+---------------+-------------+
Here the amphora id is 3973f489-4820-4c52-a506-4ebb5ea9d334 Then it's easy to get the instance in Nova, its name is "amphora-<amphora_id>":
$ openstack server list --all | grep amphora | d5455ab1-fc67-48ca-bf66-0df4a248c74b | amphora-3973f489-4820-4c52-a506-4ebb5ea9d334 | ACTIVE | lb-mgmt-net=192.168.0.148; public=172.24.4.14 | amphora-centos-stream | m1.amphora |
Keep in mind that the lifecycle of those instances is managed by the Octavia services, it's not recommended to perform changes on them.
Greg
On Thu, Feb 9, 2023 at 6:52 AM Nguyễn Hữu Khôi nguyenhuukhoinw@gmail.com wrote:
Hello guys. I am using octavia but I see a problem with managing octavia instances, their name and their management ip are not useful to know which LB belongs to. I hope someone will give me some solutions. Nguyen Huu Khoi