<html><head></head><body style="word-wrap: break-word; -webkit-nbsp-mode: space; -webkit-line-break: after-white-space; ">Below<div><br><div><div><div>On May 16, 2011, at 2:22 PM, Vladimir wrote:</div><br class="Apple-interchange-newline"><blockquote type="cite"><div bgcolor="#FFFFFF"><div>Hi Team,</div><div><br></div><div>Could you pleas help us with below questions.</div><div><br></div><div>Thanks,<br>-Vladimir<div><br></div></div><div><br>On May 16, 2011, at 8:50 PM, "Alex Lyakas" <<a href="mailto:alex@zadarastorage.com">alex@zadarastorage.com</a>> wrote:<br><br></div><div></div><blockquote type="cite"><div>
<div dir="ltr">
<div style="FONT-FAMILY: 'Verdana'; COLOR: #000000; FONT-SIZE: 10pt">
<div>I am trying to achieve a two-node nova installation using FlatDHCP network
manager. On node-A, I have two network interfaces: eth0 is connected to public
network, while eth1 is unconfigured (just as the administration manual
recommends). I start all nova services on node-A. I see that a br100 bridge is
created, eth1 is added to that bridge, and the bridge receives an IP address
within the project network (which is a part of a fixed range). When I spawn
instances on node-A, everything works fine: the instance receives an IP address
within the project network, I can ssh into it from within node-A. I can also
assign a floating IP within my public network to the instance. Then I am able to
ssh into the instance from anywhere.</div>
<div> </div>
<div>On node-B, I have only the nova-compute running. Node-B has also eth0 and
eth1 interfaces. Similar to node-A, eth0 has a public address and eth1 is
unconfigured. Whenever I spawn an instance on node-B, I see that br100 is also
created on node-B, and eth1 is added to it. However, I am unable to ssh into the
instance. I am able to connect to the instance via VNC. Then I see that it has
not received an IP address (the instance image is configured to use DHCP). I
understand that the instance should receive an address from nova-network via
DHCP.</div>
<div> </div>
<div>My questions are:</div>
<ul>
<li>How the br100 bridge on node-B should connect to br100 on Node-A? Should
nova-network connect them somehow, or do I need to do something manually?
</li></ul></div></div></div></blockquote></div></blockquote><div><br></div>as long as you have set --flat_interface=eth1 it should be enough.<br><blockquote type="cite"><div bgcolor="#FFFFFF"><blockquote type="cite"><div><div dir="ltr"><div style="FONT-FAMILY: 'Verdana'; COLOR: #000000; FONT-SIZE: 10pt"><ul><li>I assume that if br100s were connected on both nodes, things would have
worked, but perhaps I am wrong.
</li></ul></div></div></div></blockquote></div></blockquote><div><br></div>It should work<br><blockquote type="cite"><div bgcolor="#FFFFFF"><blockquote type="cite"><div><div dir="ltr"><div style="FONT-FAMILY: 'Verdana'; COLOR: #000000; FONT-SIZE: 10pt"><ul><li>Looking at the code of FlatDHCPManager, I see that in
setup_compute_network() method, ensure_bridge() is called without the
‘net_attrs’ parameter, and so the following code is not executed:</li></ul></div></div></div></blockquote></div></blockquote><div><br></div>This code is not supposed to run on the second host. Only nova-network needs an ip on the bridge. The compute host doesn't need an ip</div><div><br><blockquote type="cite"><div bgcolor="#FFFFFF"><blockquote type="cite"><div><div dir="ltr"><div style="FONT-FAMILY: 'Verdana'; COLOR: #000000; FONT-SIZE: 10pt">
<div><font face="Courier New">if net_attrs:</font></div>
<div><font face="Courier New"> # NOTE(vish): The ip for
dnsmasq has to be the first address on the</font></div>
<div><font face="Courier New">
# bridge
for it to respond to reqests properly</font></div>
<div><font face="Courier New"> suffix =
net_attrs['cidr'].rpartition('/')[2]</font></div>
<div><font face="Courier New"> out, err = _execute('sudo',
'ip', 'addr', 'add',</font></div>
<div><font face="Courier New">
"%s/%s" %</font></div>
<div><font face="Courier New">
(net_attrs['gateway'], suffix),</font></div>
<div><font face="Courier New">
'brd',</font></div>
<div><font face="Courier New">
net_attrs['broadcast'],</font></div>
<div><font face="Courier New">
'dev',</font></div>
<div><font face="Courier New">
bridge,</font></div>
<div><font face="Courier New">
check_exit_code=False)</font></div>
<div> </div>
<div>while on the node-A with nova-network, this code is executed, and an entry
added to the routing table. I tried to do this code manually on node-B, but
still I am unable to ssh into the instance.</div></div></div></div></blockquote></div></blockquote><div><br></div><div>Somehow your dhcp traffic is not working. It is hard to say what could be causing this. Generally what i do is use:</div><div><br></div><div>tcpdump -i eth1 -n port 67 and port 68</div><div><br></div><div>on all the interfaces and see if i can figure out which packet isn't making it correctly.</div><div><br></div><div>Also make sure that you have</div><div>--fixed_range=XXX</div><div><br></div><div>set properly and that the nova-network host has ip_forward set in syscontrol.</div><br><blockquote type="cite"><div bgcolor="#FFFFFF"><blockquote type="cite"><div><div dir="ltr"><div style="FONT-FAMILY: 'Verdana'; COLOR: #000000; FONT-SIZE: 10pt">
<div> </div></div></div>
</div></blockquote></div>_______________________________________________<br>Mailing list: <a href="https://launchpad.net/~openstack">https://launchpad.net/~openstack</a><br>Post to : <a href="mailto:openstack@lists.launchpad.net">openstack@lists.launchpad.net</a><br>Unsubscribe : <a href="https://launchpad.net/~openstack">https://launchpad.net/~openstack</a><br>More help : <a href="https://help.launchpad.net/ListHelp">https://help.launchpad.net/ListHelp</a><br></blockquote></div><br></div></div></body></html>