Open Stack

The one downside of using the veth method vs a vlan tagged interface on the host is making it persistent after reboot.  It's possible, but it's far more of a faff than just using a standard tagged interface.
________________________________
From: Satish Patel <satish.txt at gmail.com>
Sent: 06 September 2023 13:59
To: Oliver Weinmann <oliver.weinmann at me.com>
Cc: OpenStack Discuss <openstack-discuss at lists.openstack.org>
Subject: Re: [kolla-ansible][octavia] octavia management network setup for vlan provider


CAUTION: This email originates from outside THG

________________________________
Hi Oliver,

Thank you for your reply, That is an awesome blog and we should add multiple scenarios or examples to kolla-ansible official doc page to help out people :)

By the way, Last night I figured out how to handle veth and wire up with lb-mgmt-net and soon I will create a blog to make it easier for others to understand the logic behind it.

On Wed, Sep 6, 2023 at 12:31 AM Oliver Weinmann <oliver.weinmann at me.com<mailto:oliver.weinmann at me.com>> wrote:
Hi Satish,

I got stuck at the very same issue when I first set up Octavia. The control. Does need to have an interface on VLAN 41, since they need to communicate with the amphora instances. So you need to create a VLAN 41 interface on all control nodes with an IP of the LB-MGMT-NET outside of your defined allocation pool. If you have a free interface in your control nodes use that, if not you can try to create VETH interfaces as explained in the following article:


*https://cloudbase.it/openstack-on-arm64-lbaas/*<https://cloudbase.it/openstack-on-arm64-lbaas/>


Cheers,

Oliver

Von meinem iPhone gesendet

Am 06.09.2023 um 00:52 schrieb Satish Patel <satish.txt at gmail.com<mailto:satish.txt at gmail.com>>:


Folks,

I have setup kolla-ansible and configured octavia using the o-hm0 interface with the tenant and it works. For production I think I should use VLAN based provider for octavia management network so this is what I did

I have created a bond0.41 dedicated interface on all 3 controller nodes and created vlan 41 on all network switches.

This is what my global.yml looks like

## Octivia
enable_octavia: "yes"
octavia_network_interface: "bond0.41"

octavia_amp_flavor:
  name: "amphora"
  is_public: no
  vcpus: 2
  ram: 2048
  disk: 5

octavia_amp_network:
  name: lb-mgmt-net
  provider_network_type: vlan
  provider_segmentation_id: 41
  provider_physical_network: physnet1
  external: false
  shared: false
  subnet:
    name: lb-mgmt-subnet
    cidr: "192.168.41.0/24<http://192.168.41.0/24>"
    allocation_pool_start: "192.168.41.100"
    allocation_pool_end: "192.168.41.200"
    enable_dhcp: yes

After running the playbook all get setup as per document. When I create loadbalancer it just get stuck in PENDING status.

[1] Document saying make sure your octavia_network_interface is connected to openvswitch. Do I need to connect manually or will kolla-ansible do that for me?  If I am going to do that then on which bridge I should attach br-ex or br-int ?

[1] https://docs.openstack.org/kolla-ansible/latest/reference/networking/octavia.html<https://docs.openstack.org/kolla-ansible/latest/reference/networking/octavia.html>


-------------- next part --------------
An HTML attachment was scrubbed...
URL: <https://lists.openstack.org/pipermail/openstack-discuss/attachments/20230906/cf123079/attachment.htm>