[octavia] Octavia management IP fragment
Gregory Thiemonge
gthiemonge at redhat.com
Thu Feb 9 06:48:11 UTC 2023
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 at 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
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <https://lists.openstack.org/pipermail/openstack-discuss/attachments/20230209/0bf6e958/attachment.htm>
More information about the openstack-discuss
mailing list