Ask Your Question

Revision history [back]

I believe that 2 Compute Nodes in case of DVR cluster are needed to verify that East-West traffic will avoid routing via Network or Controller/Network Node , otherwise see sample bellow was tested on Two Node DVR cluster with External network flat provider (Controller/Network && Compute).
Running DVR with Two external networks via flat network provider on CentOS 7.2 RDO Liberty
https://www.linux.com/blog/running-dvr-two-external-networks-flat-network-provider-centos-72-rdo-liberty

image description

I believe that 2 Compute Nodes in case of DVR cluster are needed to verify that East-West traffic will avoid routing via Network or Controller/Network Node , otherwise see sample bellow bellow, which was tested on Two Node DVR cluster with External network flat provider (Controller/Network && Compute).
Running DVR with Two external networks via flat network provider on CentOS 7.2 RDO Liberty
https://www.linux.com/blog/running-dvr-two-external-networks-flat-network-provider-centos-72-rdo-liberty

image description

I believe that 2 Compute Nodes in case of DVR cluster are needed to verify that East-West traffic will avoid routing via Network or Controller/Network Node , otherwise see sample bellow, which was might be tested on Two Node DVR cluster with External network flat provider (Controller/Network && Compute).
Running DVR with Two external networks via flat network provider on CentOS 7.2 RDO Liberty
https://www.linux.com/blog/running-dvr-two-external-networks-flat-network-provider-centos-72-rdo-liberty

image description

I believe that 2 Compute Nodes in case of DVR cluster are needed to verify that East-West traffic will avoid routing via Network or Controller/Network Node , otherwise see sample bellow, which might be tested on Two Node DVR cluster with External network flat provider (Controller/Network && Compute).
Running DVR with Two external networks via flat network provider on CentOS 7.2 RDO Liberty
https://www.linux.com/blog/running-dvr-two-external-networks-flat-network-provider-centos-72-rdo-liberty

image description

Another sample with External vlan network provider, which might be tested on Two Node Cluster Controller/Network&&Compute.
RDO Mitaka & Several External Networks VLAN Provider Setup
https://www.linux.com/blog/rdo-mitaka-several-external-networks-vlan-provider-setup

UPDATE MSK 16:50

Relaying on already existing physical network infrastructure. They involve provider network (vlan) for creating networks connecting  Compute Nodes and Controller/Network Node. Thus this networks has IP address and MASK what requires  Router/Switch blocks like on pictures at mentioned link.Even though, if East/West traffic is not your major concern. One Compute Node might be enough.

The core target is :-

Provider networks lack the concept of fixed and floating IP addresses because they only handle layer-2 connectivity for instances.

So,they avoid traditional for Neutron L3 routing
END UPDATE

I believe that 2 Compute Nodes in case of DVR cluster are needed to verify that East-West traffic will avoid routing via Network or Controller/Network Node , otherwise see sample bellow, which might be tested on Two Node DVR cluster with External network flat provider (Controller/Network && Compute).
Running DVR with Two external networks via flat network provider on CentOS 7.2 RDO Liberty
https://www.linux.com/blog/running-dvr-two-external-networks-flat-network-provider-centos-72-rdo-liberty

image description

Another sample with External vlan network provider, which might be tested on Two Node Cluster Controller/Network&&Compute.
RDO Mitaka & Several External Networks VLAN Provider Setup
https://www.linux.com/blog/rdo-mitaka-several-external-networks-vlan-provider-setup

UPDATE MSK 16:50

Relaying on already existing physical network infrastructure. They involve provider network (vlan) for creating networks connecting  Compute Nodes and Controller/Network Node. Thus this networks has IP address and MASK what requires  Router/Switch blocks like on pictures at mentioned link.Even though, if East/West traffic is not your major concern. One Compute Node might be enough.

The core target is :-

Provider networks lack the concept of fixed and floating IP addresses because they only handle layer-2 connectivity for instances.

So,they avoid traditional for Neutron L3 routing
Snapshots bellow from mentioned link is a fair for suggested design

image description

image description

My original answer is irrelevant to question. It presumes Neutron L3 routing in both cases. However, all qg-xxxx outgoing interfaces from qrouter-namespaces would be attached to br-int. Un-bridged external routing would come into play due to External network providers involvement.
END UPDATE

I believe that 2 Compute Nodes in case of DVR cluster are needed to verify that East-West traffic will avoid routing via Network or Controller/Network Node , otherwise see sample bellow, which might be tested on Two Node DVR cluster with External network flat provider (Controller/Network && Compute).
Running DVR with Two external networks via flat network provider on CentOS 7.2 RDO Liberty
https://www.linux.com/blog/running-dvr-two-external-networks-flat-network-provider-centos-72-rdo-liberty

image description

Another sample with External vlan network provider, which might be tested on Two Node Cluster Controller/Network&&Compute.
RDO Mitaka & Several External Networks VLAN Provider Setup
https://www.linux.com/blog/rdo-mitaka-several-external-networks-vlan-provider-setup

UPDATE MSK 16:5017:50 05/16/2016

Relaying on already existing physical network infrastructure. They involve provider network (vlan) for creating networks connecting  Compute Nodes and Controller/Network Node. Thus this networks has IP address and MASK what requires  Router/Switch blocks like on pictures at mentioned link.Even though, if East/West traffic is not your major concern. One Compute Node might be enough.

The core target is :-

Provider networks lack the concept of fixed and floating IP addresses because they only handle layer-2 connectivity for instances.

So,they avoid traditional for Neutron L3 routing
Snapshots bellow from mentioned link is a fair for suggested design

image description

image description

My original answer is irrelevant to question. It presumes Neutron L3 routing in both cases. However, all fg-xxxx (Link 1) and qg-xxxx outgoing outgoing interfaces from qrouter-namespaces (Link 2) would be attached to br-int. Un-bridged external routing would come into play due to External network providers involvement.
END UPDATE

I believe that 2 Compute Nodes in case of DVR cluster are needed to verify that East-West traffic will avoid routing via Network or Controller/Network Node , otherwise see sample bellow, which might be tested on Two Node DVR cluster with External network flat provider (Controller/Network && Compute).
Running DVR with Two external networks via flat network provider on CentOS 7.2 RDO Liberty
https://www.linux.com/blog/running-dvr-two-external-networks-flat-network-provider-centos-72-rdo-liberty
Another sample with External vlan network provider, which might be tested on Two Node Cluster Controller/Network&&Compute.
RDO Mitaka & Several External Networks VLAN Provider Setup
https://www.linux.com/blog/rdo-mitaka-several-external-networks-vlan-provider-setup

UPDATE MSK 17:50 05/16/2016

Relaying on already existing physical network infrastructure. They involve provider network (vlan) for creating networks connecting  Compute Nodes and Controller/Network Node. Thus this networks has IP address and MASK what requires  Router/Switch blocks like on pictures at mentioned link.Even though, if East/West traffic is not your major concern. One Compute Node might be enough.

The core target is :-

Provider networks lack the concept of fixed and floating IP addresses because they only handle layer-2 connectivity for instances.

So,they avoid traditional for Neutron L3 routing
Snapshots bellow from mentioned link is a fair for suggested design

image description

image description

I might be missing something , but http://docs.openstack.org/liberty/networking-guide/scenario_provider_ovs.html
is silently skipping the problem with cloud VMs requests to Nova Metadata Server.

I  am talking about "isolated_metadata=True" in dhcp_agent.ini.

My original answer is irrelevant to question. It presumes Neutron L3 routing in both cases. However, all fg-xxxx (Link 1) and qg-xxxx outgoing interfaces from qrouter-namespaces (Link 2) would be attached to br-int. Un-bridged external routing would come into play due to External network providers involvement.
END UPDATE

I believe that 2 Compute Nodes in case of DVR cluster are needed to verify that East-West traffic will avoid routing via Network or Controller/Network Node , otherwise see sample bellow, which might be tested on Two Node DVR cluster with External network flat provider (Controller/Network && Compute).
Running DVR with Two external networks via flat network provider on CentOS 7.2 RDO Liberty
https://www.linux.com/blog/running-dvr-two-external-networks-flat-network-provider-centos-72-rdo-liberty
Another sample with External vlan network provider, which might be tested on Two Node Cluster Controller/Network&&Compute.
RDO Mitaka & Several External Networks VLAN Provider Setup
https://www.linux.com/blog/rdo-mitaka-several-external-networks-vlan-provider-setup

UPDATE MSK 17:50 05/16/2016

Relaying on already existing physical network infrastructure. They involve provider network (vlan) for creating networks connecting  Compute Nodes and Controller/Network Node. Thus this networks has IP address and MASK what requires  Router/Switch blocks like on pictures at mentioned link.Even though, if East/West traffic is not your major concern. One Compute Node might be enough.

The core target is :-

Provider networks lack the concept of fixed and floating IP addresses because they only handle layer-2 connectivity for instances.

So,they avoid traditional for Neutron L3 routing
Snapshots bellow from mentioned link is a fair for suggested design

image description

image description

I might be missing something , but http://docs.openstack.org/liberty/networking-guide/scenario_provider_ovs.html
is silently skipping the problem with cloud VMs requests to Nova Metadata Server.

I  am talking about "isolated_metadata=True" in dhcp_agent.ini.

My original answer is irrelevant to question. It presumes Neutron L3 routing in both cases. cases. However, all fg-xxxx (Link 1) from fip-namespaces and qg-xxxx outgoing interfaces from qrouter-namespaces (Link 2) would be attached to br-int. Un-bridged external routing would come into play due to External network providers involvement.
END UPDATE

I believe that 2 Compute Nodes in case of DVR cluster are needed to verify that East-West traffic will avoid routing via Network or Controller/Network Node , otherwise see sample bellow, which might be tested on Two Node DVR cluster with External network flat provider (Controller/Network && Compute).
Running DVR with Two external networks via flat network provider on CentOS 7.2 RDO Liberty
https://www.linux.com/blog/running-dvr-two-external-networks-flat-network-provider-centos-72-rdo-liberty
Another sample with External vlan network provider, which might be tested on Two Node Cluster Controller/Network&&Compute.
RDO Mitaka & Several External Networks VLAN Provider Setup
https://www.linux.com/blog/rdo-mitaka-several-external-networks-vlan-provider-setup