[octavia] Routing between lb-mgmt-net and amphora

Paul Bourke paul.bourke at oracle.com
Thu Dec 6 18:41:43 UTC 2018


Hi,

This is mostly a follow on to the thread at[0], though due to the mailing list transition it was easier to start a new thread.

I've been attempting to get Octavia setup according to the dev-quick-start guide[1], but have been struggling with the following piece:

"Add appropriate routing to / from the ‘lb-mgmt-net’ such that egress is allowed, and the controller (to be created later) can talk to hosts on this network."

In mranga's reply, they say:

> -- Create an ovs port  on br-int
> -- Create a neutron port using the ovs port that you just created.
> -- Assign the ip address of the neutron port to the ovs port
> -- Use ip netns exec to assign a route in the router namespace of the LoadBalancer network.

I have enough of an understanding of Neutron/OVS for this to mostly make sense, but not enough to actually put it into practice it seems. My environment:

3 x control nodes
2 x network nodes
1 x compute

All nodes have two interfaces, eth0 being the management network - 192.168.5.0/24, and eth1 being used for the provider network. I then create the Octavia lb-mgmt-net on 172.18.2.0/24.

I've read the devstack script[2] and have the following questions:

* Should I add the OVS port to br-int on the compute, network nodes, or both?
* What is the purpose of creating a neutron port in this scenario

If anyone is able to explain this a bit further or can even point to some good material to flesh out the underlying concepts it would be much appreciated, I feel the 'Neutron 101' videos I've done so far are not quite getting me there :)

Cheers,
-Paul

[0] http://lists.openstack.org/pipermail/openstack-discuss/2018-December/000544.html
[1] https://docs.openstack.org/octavia/latest/contributor/guides/dev-quick-start.html
[2] https://github.com/openstack/octavia/blob/master/devstack/plugin.sh



More information about the openstack-discuss mailing list