Hey Sagar,<div><br></div><div>It does sound like you need to use eth1 for FLAT_INTERFACE - but note this parameter is used when your network is first created with nova-manage, so if you change this you will need to re-run stack.sh (it isn't enough to update your nova.conf), which is probably best to do after a reboot in this case, to reset your network to its original state.</div>
<div><br></div><div>My guess is that your instance network is working on the first server because it is running nova-network, and is the gateway machine for the instances. Thus instances on that host don't have to go to the wire to get dhcp addresses, hit the gateway, etc.</div>
<div><br></div><div>It seems likely that nova-net gave the gateway address 192.168.3.1 to br100 on your master node, and then connected eth0 to br100. On the second host, nova probably created br100 for instances and then added the eth0 flat_interface to it (which is not connected to any network). So yeah, it doesn't seem like there would be a way for instances on the second host to talk to their gateway, which would explain the lack of connectivity for the instances on the second host. Making the instance bridges plug into eth1 (as FLAT_INTERFACE) looks like it may allow the instance-gateway communication.</div>
<div><font class="Apple-style-span" color="#222222" face="arial, sans-serif"><span class="Apple-style-span" style="border-collapse:collapse"><br></span></font></div><div><span style="font-family:arial,sans-serif;font-size:13px;border-collapse:collapse;color:rgb(34,34,34)">Some other things to check while you are working through this:</span></div>
<div><span style="font-family:arial,sans-serif;font-size:13px;border-collapse:collapse;color:rgb(34,34,34)"><br></span></div><div><span style="font-family:arial,sans-serif;font-size:13px;border-collapse:collapse;color:rgb(34,34,34)">* Are your instances getting ip addresses?</span></div>
<div><span style="font-family:arial,sans-serif;font-size:13px;border-collapse:collapse;color:rgb(34,34,34)">* Can your instances ping their gateway 192.168.3.1?</span></div><div><span style="font-family:arial,sans-serif;font-size:13px;border-collapse:collapse;color:rgb(34,34,34)">* Can you ping the instances from the master/network host?</span></div>
<div><span style="font-family:arial,sans-serif;font-size:13px;border-collapse:collapse;color:rgb(34,34,34)"><br></span></div><div><span style="font-family:arial,sans-serif;font-size:13px;border-collapse:collapse;color:rgb(34,34,34)">tcpdump is very useful here, so you can see where ping/dhcp protocols are breaking.</span></div>
<div><span style="font-family:arial,sans-serif;font-size:13px;border-collapse:collapse;color:rgb(34,34,34)"><br></span></div><div><font color="#222222" face="arial, sans-serif"><span style="border-collapse:collapse"><span style="font-size:13px">PUBLIC_INTERFACE seems right as eth0, but won't matter till you start playing with floating addresses. You shouldn't need </span></span></font><span style="font-family:arial,sans-serif;font-size:13px;border-collapse:collapse;color:rgb(34,34,34)">VLAN_INTERFACE, but it doesn't hurt that it is there.</span></div>
<div><font class="Apple-style-span" color="#222222" face="arial, sans-serif"><span class="Apple-style-span" style="border-collapse:collapse"><br></span></font></div><div>Anthony</div><div><br></div><div><br></div><div><br>
</div><div><br></div><div><br></div><div><br></div><div><br></div><div><font color="#222222" face="arial, sans-serif"><span style="border-collapse:collapse"><br>
</span></font></div><div><font color="#222222" face="arial, sans-serif"><span style="border-collapse:collapse"><br></span></font></div><div><span style="font-family:arial,sans-serif;font-size:13px;border-collapse:collapse;color:rgb(34,34,34)"><br>
</span></div><div><span style="font-family:arial,sans-serif;font-size:13px;border-collapse:collapse;color:rgb(34,34,34)"><br></span></div><div><br></div><div><div class="gmail_quote">On Thu, Dec 29, 2011 at 12:00 AM, Frost Dragon <span dir="ltr"><<a href="mailto:frostdragon777@gmail.com" target="_blank">frostdragon777@gmail.com</a>></span> wrote:<br>
<blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">Hi,<br>
<a href="http://192.168.3.0/24" target="_blank">192.168.3.0/24</a> is the fixed_range in my localrc for both nodes. My
second node doesn't have direct access to the public network. It has
only one interface (eth1) connected to the private network. It has an ip
of 192.168.2.2. Is there a way set this node up as a compute node
without connecting eth0 to the public network? I read that deploying
openstack is possible without 2 NICs. Also, would putting my vms in my
manage network help? Because the VMs on my master node work fine. Its
only on the compute nodes that I'm having issues. I was thinking that it
had something to do with all my nova.conf parameters pointing to an
unused eth0 interface on my compute node (please see my previous posts
for more details on my network setup)<br>
<br>
Thanks and regards,<br>
Sagar<div><div><br><br><div class="gmail_quote"><br>
<blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex"><div class="gmail_quote"><div>Is each machine configured with an address in the <a href="http://192.168.3.0/24" target="_blank">192.168.3.0/24</a>
range, and is that network otherwise configured? It sounds like you
have not fully configured the instance network. Typically for
deployments with FlatDHCP, there are at least 3 networks - one public,
one management, and one for instances. Each of these is usually on its
on physical network interface or vlan.</div>
<div><br></div><div>If this is just for testing, you can also try putting your vms inside your manage-net (say the upper part of <a href="http://192.168.2.128/25" target="_blank">192.168.2.128/25</a>, which can be convenient for testing but not generally a good idea.</div>
<span><font color="#888888">
<div><br></div><div>Anthony</div></font></span><br>
</div></blockquote></div>
</div></div></blockquote></div><br></div>