Hi Pshem You need to make use of the neutron-openvswitch charm - this is a subordinate charm that's deployed with nova-compute, and manages the neutron configuration and agents on compute nodes.
In the same way that you provide ext-port to neutron-gateway, you'll need todo the same with neutron-openvswitch when using dvr mode - this port is used for north/south traffic for instances on each compute node where they have floating IP's - instances which don't have floating ip's will still go via the neutron gateway. Hope that helps! On Thu, Nov 5, 2015 at 12:29 AM, Pshem Kowalczyk <[email protected]> wrote: > Hi, > > I'm trying to figure out if it's possible to setup distributed routing (as > per http://docs.openstack.org/networking-guide/scenario_dvr_ovs.html ). > > Using fairly basic config: > > nova-cloud-controller: > openstack-origin: cloud:trusty-liberty > network-manager: Neutron > neutron-external-network: "ext-net" > console-access-protocol: vnc > > nova-compute: > openstack-origin: cloud:trusty-liberty > > neutron-api: > openstack-origin: cloud:trusty-liberty > neutron-external-network: "ext-net" > neutron-security-groups: true > enable-dvr: true > overlay-network-type: vxlan > > neutron-gateway: > openstack-origin: cloud:trusty-liberty > ext-port: eth1 > > > and deploying nova-cloud-controller and neutron api into lxc containers on > node 0, neutron-gateway into native node 0, and nova compute into nodes 1 > and 2. > > After I done that I ended up with 'default' configuration for neutron on > nodes 1 and 2. > I was told that neutron-gateway and nova-compute can not be collocated, so > I wonder which charm should claim the ownership of the neutron > configuration in that scenario? > > kind regards > Pshem > > > -- > Juju mailing list > [email protected] > Modify settings or unsubscribe at: > https://lists.ubuntu.com/mailman/listinfo/juju > >
-- Juju mailing list [email protected] Modify settings or unsubscribe at: https://lists.ubuntu.com/mailman/listinfo/juju
