Re: [Openstack-operators] Octavia LBaaS - networking requirements

2018-02-06 Thread Flint WALRUS
Thank you very much for this cristal clear statement, in the meantime I watched the sidney Octavia session and had answers on side questions. The Openstack community is really kickass, thanks everyone! Le mar. 6 févr. 2018 à 17:52, Michael Johnson a écrit : > No issue with using an L2 network fo

Re: [Openstack-operators] Octavia LBaaS - networking requirements

2018-02-06 Thread Michael Johnson
No issue with using an L2 network for the lb-mgmt-net. It only requires the following: Controllers can reach amphora-agent IPs on the TCP bind_port (default 9443) Amphora-agents can reach the controllers in the controller_ip_port_list via UDP (default ) This can be via an L2 lb-mgmt-net (prov

Re: [Openstack-operators] Octavia LBaaS - networking requirements

2018-02-06 Thread Flint WALRUS
Ok, that’s what I was understanding from the documentation but as I couldn’t find any information related to the L3 specifics I prefer to have another check that mine only x) I’ll have to install and operate Octavia within an unusual L2 only network and I would like to be sure I’ll not push myself

Re: [Openstack-operators] Octavia LBaaS - networking requirements

2018-02-06 Thread Volodymyr Litovka
Hi Flint, I think, Octavia expects reachibility between components over management network, regardless of network's technology. On 2/6/18 11:41 AM, Flint WALRUS wrote: Hi guys, I’m wondering if the Octavia lb-mgmt-net can be a L2 provider network instead of a neutron L3 vxlan ? Is Octavia s