<html><head><meta http-equiv="Content-Type" content="text/html charset=iso-8859-1"></head><body style="word-wrap: break-word; -webkit-nbsp-mode: space; -webkit-line-break: after-white-space; "><br><div><div>On Nov 6, 2012, at 4:10 AM, Daniel Oliveira <<a href="mailto:dvalbrand@gmail.com">dvalbrand@gmail.com</a>> wrote:</div><br class="Apple-interchange-newline"><blockquote type="cite">Hello.<div><br></div><div>I once had some problems with Openstack regarding network configuration, so I thought I needed to have a better understanding on the configuration possibilities. I'm no expert, though, and even after reading <a href="http://docs.openstack.org/essex/openstack-compute/admin/content/compute-options-reference.html">this link</a>, I couldn't fully understand the difference between the parameters <font face="courier new, monospace">public_interface</font>, <font face="courier new, monospace">flat_interface</font> and <font face="courier new, monospace">vlan_interface</font>. Could someone help me understand?</div>
</blockquote><br></div><div>public_interface == the interface where floating (natted) ips will be created.</div><div><br></div><div><br></div><div>In flatdhcp mode flat_interface is a physical interface that will get added in to br100 along with all the vm interfaces (see <a href="http://wiki.openstack.org/UnderstandingFlatNetworking">http://wiki.openstack.org/UnderstandingFlatNetworking</a>)</div><div><br></div><div>In vlan mode, you specify vlan_interface instead of flat_interface. In this case a separate is created on the interface for each tenant in the system. Vms for each tenant are bridged into their own vlan.</div><div><br></div><div>Vish</div><br></body></html>