[kolla-ansible][octavia] need networking help

W Ch wchy1001 at gmail.com
Tue Aug 16 09:32:31 UTC 2022


Hi Stuart:

Usually, you need to add a bridge to all network nodes,  you can use
"ovs-vsctl add-br  {br-name}" to add a ovs bridge, then you need to add a
physical port  to that bridge by executing "ovs-vsctl  add-port {bridge}
{port}".
another alternatives, you can append the physical port
to neutron_external_interface variable in globals.yml.  in this case, kolla
will create the ovs bridge automatically.
both of them, you need set octavia_network_interface and configure external
switch properly.

if you really don't know how this works, I propose you  use
 "octavia_network_type: tenant"  ref: [0] , in this case, kolla-ansible
will setup the octavia management network for you, you don't need to do
anything.

[0]:
https://docs.openstack.org/kolla-ansible/latest/reference/networking/octavia.html#development-or-testing

thanks.


Stuart Whitman <swhitman at groupw.com> 于2022年8月16日周二 06:28写道:

> Hello,
>
> I enabled Octavia on a kolla-ansible installed Openstack
> cluster. When I try to launch a loadbalancer instance, the
> octavia-worker.log file reports:
> "WARNING octavia.amphorae.drivers.haproxy.rest_api_driver [-]
> Could not connect to instance."
>
> I researched enough to know that the problem has to do with networking
> between the controller and the lb-mgmt-net network. I initially
> overlooked this in the kolla-ansible Octavia documentation:
> "If using a VLAN provider network, ensure that the traffic is also bridged
> to Open vSwitch on the controllers." But, I don't know how to do it.
>
> Help to create the necessary bridge would be greatly appreciated.
>
> Thanks,
> -Stu
> _____________________________________
> The information contained in this e-mail and any attachments from Group W
> may contain confidential and/or proprietary information and is intended
> only for the named recipient to whom it was originally addressed. If you
> are not the intended recipient, be aware that any disclosure, distribution,
> or copying of this e-mail or its attachments is strictly prohibited. If you
> have received this e-mail in error, please notify the sender immediately of
> that fact by return e-mail and permanently delete the e-mail and any
> attachments to it.
>
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <https://lists.openstack.org/pipermail/openstack-discuss/attachments/20220816/b7d44877/attachment.htm>


More information about the openstack-discuss mailing list