Thanks Dan for bringing up the areas that are confusing - esp with specific links. I'll try to address below.<br><br><div class="gmail_quote">On Mon, Oct 1, 2012 at 11:31 AM, <span dir="ltr"><<a href="mailto:dyocum@redhat.com" target="_blank">dyocum@redhat.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>
<br>
I'm noticing that different places in the docs assign either a bridge<br>
interface or a physical interface when referring to the<br>
"public_interface" configuration option. To wit, on this page in 2<br>
separate example nova.conf files public_interface is set to eth0 and<br>
br100:<br>
<br>
<a href="http://docs.openstack.org/trunk/openstack-compute/admin/content/sample-nova-configuration-files.html" target="_blank">http://docs.openstack.org/trunk/openstack-compute/admin/content/sample-nova-configuration-files.html</a><br>
<br></blockquote><div><br>These are very specific examples from Mediawiki and Rackspace and are only examples. These nova.conf files result in a very specific networking/hypervisor configuration described in text above the nova.conf files themselves. <br>
</div><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">
On this page it refers to vlan100 which, I'm told, is the name of a<br>
physical nic.<br>
<br>
<a href="http://docs.openstack.org/trunk/openstack-compute/admin/content/associating-public-ip.html" target="_blank">http://docs.openstack.org/trunk/openstack-compute/admin/content/associating-public-ip.html</a><br>
<br>
</blockquote><div><br>On this page, yes I believe that is a physical nic.<br> </div><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">The description of public_interface on the nova.conf reference page is<br>
unhelpful in this regard, too (although the default appear to be eth0,<br>
which should be a good clue):<br>
<br>
<a href="http://docs.openstack.org/trunk/openstack-compute/admin/content/compute-options-reference.html" target="_blank">http://docs.openstack.org/trunk/openstack-compute/admin/content/compute-options-reference.html</a><br>
<br>
So, what should it be? The bridge interface configured/built by<br>
openstack or the physical device name?<br>
<br></blockquote><div><br>It depends on the type of networking you put into nova.conf. VLAN is the default.<br><a href="http://docs.openstack.org/trunk/openstack-compute/admin/content/networking-options.html">http://docs.openstack.org/trunk/openstack-compute/admin/content/networking-options.html</a><br>
For VLAN mode, Compute creates a VLAN and bridge for each project<br>For Flat Networking, br100 is set in nova.conf (the name br100) and nova sets up the bridge.<br>In <span class="bold"><strong>Flat DHCP Mode</strong></span>, OpenStack starts a DHCP server
(dnsmasq) to pass out IP addresses to VM instances from the specified subnet in addition
to manually configuring the networking bridge. IP addresses for VM instances are grabbed
from a subnet specified by the network administrator. <br><br>Flat networking is also slightly different depending on your hypervisor, see <br><a href="http://docs.openstack.org/trunk/openstack-compute/admin/content/libvirt-flat-networking.html">http://docs.openstack.org/trunk/openstack-compute/admin/content/libvirt-flat-networking.html</a>. There are diagrams in this page that should be useful as well. <br>
<br>I realize networking is further complicated with the introduction of Quantum this release. All the above examples show nova.conf when using nova-network. If you want to use Quantum for virtual network configuration, see <a href="http://docs.openstack.org/trunk/openstack-network/admin/content/">http://docs.openstack.org/trunk/openstack-network/admin/content/</a>.<br>
<br>Thanks for your questions, these help us improve the docs, a constant goal.<br><br>Anne<br><br> </div><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">
Thanks,<br>
Dan<br>
<span class="HOEnZb"><font color="#888888"><br>
--<br>
Dan Yocum<br>
Sr. Systems Engineer<br>
OpenShift | PaaS by Red Hat<br>
<a href="mailto:dyocum@redhat.com">dyocum@redhat.com</a><br>
<br>
_______________________________________________<br>
Openstack-docs mailing list<br>
<a href="mailto:Openstack-docs@lists.openstack.org">Openstack-docs@lists.openstack.org</a><br>
<a href="http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-docs" target="_blank">http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-docs</a><br>
</font></span></blockquote></div><br>