OpenStack Compute (nova)

OpenStack VMs are unable to communicate with Outer World

Asked by Amogh Patel

Hello!

I'm trying to implement OpenStack solution in my environment ( bunch of Mac Minis) with one NIC card limitation. So far, I was able to setup a Controller and two Compute Nodes and created several VMs in compute nodes.

My host (Controller/Compute) are in 10.x.x.x series and I've setup the br100 private network for VMs in 192.168.100.x series per document. So, both Host and VMs have different gateway.

Problem : My Hosts (Controller/Compute) can communicate (ping/SSH) to their VMs but other server from same network (10.x.x.x) are unable to communicate to VMs. Vice versa, VMs are unable to communicate to other Hosts of the 10.x.x.x network except controller & compute nodes and also to the outer world.

What could be possible solution for this? Any help would be really appreciated. Please let me know, what information/files should I provide to diagnose it further.

Thanks in advance.

Question information

Language:
English Edit question
Status:
Solved
For:
OpenStack Compute (nova) Edit question
Assignee:
No assignee Edit question
Solved by:
Xiang Hui
Solved:
Last query:
Last reply:
Revision history for this message
Amogh Patel (amoghpatel4u) said : 		#1

Can we do any kind of NATing or iptables rules in OpenStack like VMWare provides . By the way, I'm using FlatDHCPManager mode.

Revision history for this message
Xiang Hui (xianghui) said : 		#2

what the network type? flat, vlan, local, which one did you created?

Revision history for this message
Amogh Patel (amoghpatel4u) said : 		#3

Hi Xiang,

I've used the FlatDHCP (nova.conf -> network_manager=nova.network.manager.FlatDHCPManager). I've created my network with below command:

nova network-create private --fixed-range-v4=192.168.100.1/24 --bridge-interface=br100

My Controller & Compute Hosts are in 10 series gateway and Virtual Instances are in 192.168 series. So my VM can ping its gateway and its Host but not other hosts of same 10 series network and vice versa.

Revision history for this message
Best Xiang Hui (xianghui) said : 		#4

Hi Amogh,

  Sorry, I have misunderstood your question before.

  So your Controller & Compute Hosts which in 10 series can ping its vms which in 192.168 series, but other 10 series server cann't , right? and you want other servers can ping these vms each other.

  There's two way:
    1. If the other servers in 10 series are in the same switch with your Controller & Compute Hosts, you can just simply assign these other servers an 192.168 series ip to the ethernet card , then you can ping the vms of our Controller & Compute Hosts.

    2. assign a floating ip to the vms, of course, the ip is 10 series, which means, the vms have two ips, one is in 192.168.x, another is 10.x, and I don't know if nova-network can support the floating ip fuction, but quantum(neutron) have supported this floating ip feature by using quantum-l3-agent.

Revision history for this message
Matt Mao (maoliping455) said : 		#5

nova-network support floating ip, and floating ip will help you solve this issue.

Revision history for this message
Amogh Patel (amoghpatel4u) said : 		#6

Thanks everyone. I got it solved by making my virtual network in Host network itself.

Revision history for this message
Amogh Patel (amoghpatel4u) said : 		#7

Thanks Xiang Hui, that solved my question.