| felixhuettner[m] | Hi guesswhat, we are doing that. We are using a openstack port bound to a specific node. Then we manually assign an IP on the interface on this node and use that for the controller | 06:36 |
|---|---|---|
| guesswhat | Anyone is running Octavia with OpenVSwitch ? Seems its does not work by default and it can not, unless some provider external network is involved. Thanks | 08:58 |
| jrosser_ | guesswhat: it might be worth studying how openstack-ansible or kolla set up the networking for octavia | 09:08 |
| jrosser_ | there are lots of ways to do it | 09:08 |
| guesswhat | jrosser_ there isn any advice how to it, https://stackoverflow.com/questions/65885301/how-configure-octavia-in-o, for openvswitch is a problem and the octavia_network_type: "tenant" is not recommended for "production" ( https://docs.openstack.org/kolla-ansible/latest/reference/networking/octavia.html ), I have a clue to use external vlan network, | 09:10 |
| guesswhat | but only external networkg i have experience is wan, not sure how to create vlan without involving additional router | 09:10 |
| jrosser_ | for openstack-ansible (no openvswitch required) you'd do this https://satishdotpatel.github.io/openstack-ansible-octavia/ | 09:13 |
| jrosser_ | obviously it all depends on what choices you've made for your deployment | 09:13 |
| jrosser_ | but ultimately you need a neutron network on the compute nodes that somehow is connected L2 to the right part of the control plane | 09:13 |
| jrosser_ | that doesnt really need a router | 09:14 |
| *** rlandy|out is now known as rlandy | 10:20 | |
| *** rlandy_ is now known as rlandy | 10:52 | |
| *** rlandy is now known as rlandy|dr_appt | 17:09 | |
| *** jmcdade is now known as FlexibleToast | 18:13 | |
| *** rlandy|dr_appt is now known as rlandy | 19:56 | |
| *** rlandy is now known as rlandy|bbl | 22:04 | |
Generated by irclog2html.py 2.17.3 by Marius Gedminas - find it at https://mg.pov.lt/irclog2html/!