Ask Your Question

Revision history [back]

Is there any way to use DVR with external network provider (flat) ?

As far as I can see DVR requires external bridging networking, attempt to set "external_network_bridge = " in l3_agent.ini won't work with DVR. If I am wrong here, please , advise. I was able reproduce http://dbaxps.blogspot.com/2015/10/rdo-liberty-rc-dvr-deployment.html
Then I added interface to another public network ( supposed to be declared as external flat network via external network provider). Attempted to update neutron.conf and neutron OVS,L3 agent *.ini and ml2_conf.ini files, added neutron-metadata-agent service ( followed by openstack-service restart neutron ) resulted disappearing of VXLAN tunnels. Neutron flow on DVR compute node, as follows from several manuals, is not supposed to return back to br-int before forwarding outside. But external network provider vs bridging external networking does require neutron flow to be back on br-int before sending packets out.

Is there any way to use DVR with external network provider (flat) ?

As far as I can see DVR requires external bridging networking, attempt to set "external_network_bridge = " in l3_agent.ini won't work with DVR. If I am wrong here, please , advise. I was able reproduce http://dbaxps.blogspot.com/2015/10/rdo-liberty-rc-dvr-deployment.html
Then I added interface to another public network ( supposed to be declared as external flat network via external network provider). Attempted to update neutron.conf and neutron OVS,L3 agent *.ini and ml2_conf.ini files, added neutron-metadata-agent service ( followed by openstack-service , files ifcfg-br-eth2 and ifcfg-eth2 for added interface were properly configured as OVS bridge and OVS port. Neutron-openvswitch-agent has been restarted OK during "openstack-service restart neutron ) neutron". This steps resulted disappearing of VXLAN tunnels. Neutron flow on DVR compute node, as follows from several manuals, is not supposed to return back to br-int before forwarding outside. But external network provider vs bridging external networking does require neutron flow to be back on br-int before sending packets out.

Is there any way to use DVR with external network provider (flat) ?

As far as I can see DVR requires external bridging networking, attempt to set "external_network_bridge = " in l3_agent.ini won't work with DVR. If I am wrong here, please , advise. I was able reproduce http://dbaxps.blogspot.com/2015/10/rdo-liberty-rc-dvr-deployment.html
Then I added interface to another public network ( supposed to be declared as external flat network via external network provider). Attempted to update neutron.conf and neutron OVS,L3 agent *.ini and ml2_conf.ini files, added neutron-metadata-agent service , files ifcfg-br-eth2 and ifcfg-eth2 for added interface were properly configured as OVS bridge and OVS port. Neutron-openvswitch-agent has been restarted OK during "openstack-service restart neutron". This steps resulted disappearing of VXLAN tunnels. Neutron flow on DVR compute node, as follows from several manuals, is not supposed to return back to br-int before forwarding outside. But external network provider vs bridging external networking does require neutron flow to be back on br-int before sending packets out.


ml2_conf.ini (all nodes )

type_drivers = vxlan,flat
flat_networks = physnet2

Creating network.

neutron net-create public --provider:network_type flat --provider:physical_network physnet2 --router:external
neutron subnet-create --gateway 10.10.10.1 --allocation-pool start=10.10.10.100,end=10.10.10.150 --disable-dhcp --name public_subnet public 10.10.10.0/24

Then

ovs-vsctl add-br br-eth2
ovs-vsctl add-port br-eth2 eth2
plus creating ifcfg-br-eth2 and ifcfg-eth2  files  for OVS bridge and OVS port

Then

Update openvswitch-agent.ini
bridge_mappings physnet2:br-eth2

Then

opernstack-service restart ( all nodes)