First time here? Check out the FAQ!
![]() | 1 | initial version |
Please,change sequence of steps
1. Setup Controller/Network + Compute ML2&OVS&VXLAN via standard answer-file
Three NICs on each node MGMT (eth0) , VTEPS (eth1), Ext Interface (eth2)
2. Tune cluster to work with External Network provider per RH' link ( you've mentioned)
Just in case I kept name of outgoing bridge "br-ex"
[root@ip-192-169-142-127 ~(keystone_admin)]# cat ifcfg-br-ex
DEVICE="br-ex"
NM_CONTROLLED="no"
ONBOOT="yes"
TYPE="OVSIntPort"
OVS_BRIDGE=br-ex
DEVICETYPE="ovs"
[root@ip-192-169-142-127 ~(keystone_admin)]# cat ifcfg-eth2
DEVICE="eth2"
ONBOOT="yes"
TYPE="OVSPort"
DEVICETYPE="ovs"
OVS_BRIDGE=br-ex
NM_CONTROLLED=no
IPV6INIT=no
When done tune DVR configs, restart nodes.
Make sure VXLAN tunnels are here. At this point you are ready to go
The point is to get fg-xxxxxx working via br-ex ( no matter this in this case br-ex
contains external neutron routers interface inside, not having visible IP like in bridged
external network )
[root@ip-192-169-142-137 ~]# ovs-vsctl show
6b29bb4b-b7e0-42d7-94ba-662cd321bf82
Bridge br-ex
Port "eth2"
Interface "eth2"
Port phy-br-ex
Interface phy-br-ex <=== veth pair
type: patch
options: {peer=int-br-ex}
Port br-ex
Interface br-ex
type: internal
Bridge br-int
fail_mode: secure
Port br-int
Interface br-int
type: internal
Port "qvo2be937c0-cc"
tag: 1
Interface "qvo2be937c0-cc"
Port int-br-ex
Interface int-br-ex <=== veth pair
type: patch
options: {peer=phy-br-ex}
Port "qr-98432f0d-0c"
tag: 1
Interface "qr-98432f0d-0c"
type: internal
Port patch-tun
Interface patch-tun
type: patch
options: {peer=patch-int}
Port "fg-a6949885-91" <== outgoing fip-namespace interface ( on br-int )
tag: 2
Interface "fg-a6949885-91"
type: internal
Port "qvo997b88c5-a8"
tag: 1
Interface "qvo997b88c5-a8"
Bridge br-tun
fail_mode: secure
Port br-tun
Interface br-tun
type: internal
Port patch-int
Interface patch-int
type: patch
options: {peer=patch-tun}
Port "vxlan-0c00007f"
Interface "vxlan-0c00007f"
type: vxlan
options: {df_default="true", in_key=flow, local_ip="12.0.0.137", out_key=flow, remote_ip="12.0.0.127"}
ovs_version: "2.4.0"
[root@ip-192-169-142-137 ~]# ip netns exec fip-bb5509d1-84a3-489e-847f-c07573b8f6a1 ifconfig | head -8
fg-a6949885-91: flags=4163<UP,BROADCAST,RUNNING,MULTICAST> mtu 1500
inet 10.10.10.102 netmask 255.255.255.0 broadcast 10.10.10.255
inet6 fe80::f816:3eff:fecf:84a5 prefixlen 64 scopeid 0x20<link>
ether fa:16:3e:cf:84:a5 txqueuelen 0 (Ethernet)
RX packets 138191 bytes 188105981 (179.3 MiB)
RX errors 0 dropped 0 overruns 0 frame 0
TX packets 58127 bytes 4630008 (4.4 MiB)
TX errors 0 dropped 0 overruns 0 carrier 0 collisions 0
![]() | 2 | No.2 Revision |
UPDATE
BTW, This is actually an answer for old question on forum:-
DVR + 2 external networks. Obliviously two DVR routers && Two bridges br-ex1 and br-ex2
END UPDATE
Please,change sequence of steps
1. Setup Controller/Network + Compute ML2&OVS&VXLAN via standard answer-file
Three NICs on each node MGMT (eth0) , VTEPS (eth1), Ext Interface (eth2)
2. Tune cluster to work with External Network provider per RH' link ( you've mentioned)
Just in case I kept name of outgoing bridge "br-ex"
[root@ip-192-169-142-127 ~(keystone_admin)]# cat ifcfg-br-ex
DEVICE="br-ex"
NM_CONTROLLED="no"
ONBOOT="yes"
TYPE="OVSIntPort"
OVS_BRIDGE=br-ex
DEVICETYPE="ovs"
[root@ip-192-169-142-127 ~(keystone_admin)]# cat ifcfg-eth2
DEVICE="eth2"
ONBOOT="yes"
TYPE="OVSPort"
DEVICETYPE="ovs"
OVS_BRIDGE=br-ex
NM_CONTROLLED=no
IPV6INIT=no
When done tune DVR configs, restart nodes.
Make sure VXLAN tunnels are here. At this point you are ready to go
The point is to get fg-xxxxxx working via br-ex ( no matter this in this case br-ex
contains external neutron routers interface inside, not having visible IP like in bridged
external network )
[root@ip-192-169-142-137 ~]# ovs-vsctl show
6b29bb4b-b7e0-42d7-94ba-662cd321bf82
Bridge br-ex
Port "eth2"
Interface "eth2"
Port phy-br-ex
Interface phy-br-ex <=== veth pair
type: patch
options: {peer=int-br-ex}
Port br-ex
Interface br-ex
type: internal
Bridge br-int
fail_mode: secure
Port br-int
Interface br-int
type: internal
Port "qvo2be937c0-cc"
tag: 1
Interface "qvo2be937c0-cc"
Port int-br-ex
Interface int-br-ex <=== veth pair
type: patch
options: {peer=phy-br-ex}
Port "qr-98432f0d-0c"
tag: 1
Interface "qr-98432f0d-0c"
type: internal
Port patch-tun
Interface patch-tun
type: patch
options: {peer=patch-int}
Port "fg-a6949885-91" <== outgoing fip-namespace interface ( on br-int )
tag: 2
Interface "fg-a6949885-91"
type: internal
Port "qvo997b88c5-a8"
tag: 1
Interface "qvo997b88c5-a8"
Bridge br-tun
fail_mode: secure
Port br-tun
Interface br-tun
type: internal
Port patch-int
Interface patch-int
type: patch
options: {peer=patch-tun}
Port "vxlan-0c00007f"
Interface "vxlan-0c00007f"
type: vxlan
options: {df_default="true", in_key=flow, local_ip="12.0.0.137", out_key=flow, remote_ip="12.0.0.127"}
ovs_version: "2.4.0"
[root@ip-192-169-142-137 ~]# ip netns exec fip-bb5509d1-84a3-489e-847f-c07573b8f6a1 ifconfig | head -8
fg-a6949885-91: flags=4163<UP,BROADCAST,RUNNING,MULTICAST> mtu 1500
inet 10.10.10.102 netmask 255.255.255.0 broadcast 10.10.10.255
inet6 fe80::f816:3eff:fecf:84a5 prefixlen 64 scopeid 0x20<link>
ether fa:16:3e:cf:84:a5 txqueuelen 0 (Ethernet)
RX packets 138191 bytes 188105981 (179.3 MiB)
RX errors 0 dropped 0 overruns 0 frame 0
TX packets 58127 bytes 4630008 (4.4 MiB)
TX errors 0 dropped 0 overruns 0 carrier 0 collisions 0
![]() | 3 | No.3 Revision |
UPDATEUPDATE 12/23/2015
BTW, This Final draft addressing your question is actually an answer for old question here
Running DVR with external network provider (flat) on forum:-CentOS 7.2 RDO Liberty
DVR + 2 external networks. Obliviously two DVR routers && Two bridges br-ex1 and br-ex2
END UPDATE
Please,change sequence of steps
1. Setup Controller/Network + Compute ML2&OVS&VXLAN via standard answer-file
Three NICs on each node MGMT (eth0) , VTEPS (eth1), Ext Interface (eth2)
2. Tune cluster to work with External Network provider per RH' link ( you've mentioned)
Just in case I kept name of outgoing bridge "br-ex"
[root@ip-192-169-142-127 ~(keystone_admin)]# cat ifcfg-br-ex
DEVICE="br-ex"
NM_CONTROLLED="no"
ONBOOT="yes"
TYPE="OVSIntPort"
OVS_BRIDGE=br-ex
DEVICETYPE="ovs"
[root@ip-192-169-142-127 ~(keystone_admin)]# cat ifcfg-eth2
DEVICE="eth2"
ONBOOT="yes"
TYPE="OVSPort"
DEVICETYPE="ovs"
OVS_BRIDGE=br-ex
NM_CONTROLLED=no
IPV6INIT=no
When done tune DVR configs, restart nodes.
Make sure VXLAN tunnels are here. At this point you are ready to go
The point is to get fg-xxxxxx working via br-ex ( no matter this in this case br-ex
contains external neutron routers interface inside, not having visible IP like in bridged
external network )
[root@ip-192-169-142-137 ~]# ovs-vsctl show
6b29bb4b-b7e0-42d7-94ba-662cd321bf82
Bridge br-ex
Port "eth2"
Interface "eth2"
Port phy-br-ex
Interface phy-br-ex <=== veth pair
type: patch
options: {peer=int-br-ex}
Port br-ex
Interface br-ex
type: internal
Bridge br-int
fail_mode: secure
Port br-int
Interface br-int
type: internal
Port "qvo2be937c0-cc"
tag: 1
Interface "qvo2be937c0-cc"
Port int-br-ex
Interface int-br-ex <=== veth pair
type: patch
options: {peer=phy-br-ex}
Port "qr-98432f0d-0c"
tag: 1
Interface "qr-98432f0d-0c"
type: internal
Port patch-tun
Interface patch-tun
type: patch
options: {peer=patch-int}
Port "fg-a6949885-91" <== outgoing fip-namespace interface ( on br-int )
tag: 2
Interface "fg-a6949885-91"
type: internal
Port "qvo997b88c5-a8"
tag: 1
Interface "qvo997b88c5-a8"
Bridge br-tun
fail_mode: secure
Port br-tun
Interface br-tun
type: internal
Port patch-int
Interface patch-int
type: patch
options: {peer=patch-tun}
Port "vxlan-0c00007f"
Interface "vxlan-0c00007f"
type: vxlan
options: {df_default="true", in_key=flow, local_ip="12.0.0.137", out_key=flow, remote_ip="12.0.0.127"}
ovs_version: "2.4.0"
[root@ip-192-169-142-137 ~]# ip netns exec fip-bb5509d1-84a3-489e-847f-c07573b8f6a1 ifconfig | head -8
fg-a6949885-91: flags=4163<UP,BROADCAST,RUNNING,MULTICAST> mtu 1500
inet 10.10.10.102 netmask 255.255.255.0 broadcast 10.10.10.255
inet6 fe80::f816:3eff:fecf:84a5 prefixlen 64 scopeid 0x20<link>
ether fa:16:3e:cf:84:a5 txqueuelen 0 (Ethernet)
RX packets 138191 bytes 188105981 (179.3 MiB)
RX errors 0 dropped 0 overruns 0 frame 0
TX packets 58127 bytes 4630008 (4.4 MiB)
TX errors 0 dropped 0 overruns 0 carrier 0 collisions 0