Ask Your Question

Revision history [back]

click to hide/show revision 1
initial version

Neutron DVR - Different external network for Compute and Network nodes

I have the following setup: controller: l3-agent (dvr_snat mode), ovs-plugin, dhcp-agent, metadata-agent compute1: l3-agent (dvr mode), ovs-plugin, metadata-agent

Each node has eth0 (public nics), and eth1 (private nics in the same VLAN).

From my hosting provider I am able to route a subnet to a node (but not a subnet to multiple nodes). So for instance I've assigned a subnet like 1.1.1.0/29 to the compute1 node.

When I create a virtual machine, there are namespaces "snat-xxxx" "qdhcp-xxxx" in the controller node having interfaces with IPs assigned from the 1.1.1.0/29 subnet. I suppose those namespaces are intended to do SNAT. Being that 1.1.1.0/29 is assigned to compute1, the SNAT won't work.

Is it possible to assign another subnet to the controller node only for SNAT ? So I can use my 1.1.1.0/29 for floating IPs.

Neutron DVR - Different external network for Compute and Network nodes

I have the following setup: setup:

controller: l3-agent (dvr_snat mode), ovs-plugin, dhcp-agent, metadata-agent metadata-agent

compute1: l3-agent (dvr mode), ovs-plugin, metadata-agent

Each node has eth0 (public nics), and eth1 (private nics in the same VLAN).

From my hosting provider I am able to route a subnet to a node (but not a subnet to multiple nodes). So for instance I've assigned a subnet like 1.1.1.0/29 to the compute1 node.

When I create a virtual machine, there are namespaces "snat-xxxx" "qdhcp-xxxx" in the controller node having interfaces with IPs assigned from the 1.1.1.0/29 subnet. I suppose those namespaces are intended to do SNAT. Being that 1.1.1.0/29 is assigned to compute1, the SNAT won't work.

Is it possible to assign another subnet to the controller node only for SNAT ? So I can use my 1.1.1.0/29 for floating IPs.

Neutron DVR - Different external network for Compute and Network nodes

I have the following setup:

  • controller: l3-agent (dvr_snat mode), mode), ovs-plugin, dhcp-agent, metadata-agent

    dhcp-agent, metadata-agent
  • compute1: l3-agent l3-agent (dvr mode), ovs-plugin, ovs-plugin, metadata-agent

Each node has eth0 (public nics), and eth1 (private nics in the same VLAN).

From my hosting provider I am able to route a subnet to a node (but not a subnet to multiple nodes). So for instance I've assigned a subnet like 1.1.1.0/29 to the compute1 node.

When I create a virtual machine, there are namespaces "snat-xxxx" "qdhcp-xxxx" in the controller node having interfaces with IPs assigned from the 1.1.1.0/29 subnet. I suppose those namespaces are intended to do SNAT. Being that 1.1.1.0/29 is assigned to compute1, the SNAT won't work.

Is it possible to assign another subnet to the controller node only for SNAT ? So I can use my 1.1.1.0/29 for floating IPs.