<html xmlns:v="urn:schemas-microsoft-com:vml" xmlns:o="urn:schemas-microsoft-com:office:office" xmlns:w="urn:schemas-microsoft-com:office:word" xmlns:m="http://schemas.microsoft.com/office/2004/12/omml" xmlns="http://www.w3.org/TR/REC-html40">
<head>
<meta http-equiv="Content-Type" content="text/html; charset=us-ascii">
<meta name="Generator" content="Microsoft Word 15 (filtered medium)">
<style><!--
/* Font Definitions */
@font-face
{font-family:"Cambria Math";
panose-1:2 4 5 3 5 4 6 3 2 4;}
@font-face
{font-family:Calibri;
panose-1:2 15 5 2 2 2 4 3 2 4;}
/* Style Definitions */
p.MsoNormal, li.MsoNormal, div.MsoNormal
{margin:0cm;
margin-bottom:.0001pt;
font-size:12.0pt;
font-family:"Times New Roman","serif";}
a:link, span.MsoHyperlink
{mso-style-priority:99;
color:blue;
text-decoration:underline;}
a:visited, span.MsoHyperlinkFollowed
{mso-style-priority:99;
color:purple;
text-decoration:underline;}
span.EmailStyle17
{mso-style-type:personal-reply;
font-family:"Calibri","sans-serif";
color:#1F497D;}
.MsoChpDefault
{mso-style-type:export-only;
font-family:"Calibri","sans-serif";
mso-fareast-language:EN-US;}
@page WordSection1
{size:612.0pt 792.0pt;
margin:72.0pt 72.0pt 72.0pt 72.0pt;}
div.WordSection1
{page:WordSection1;}
--></style><!--[if gte mso 9]><xml>
<o:shapedefaults v:ext="edit" spidmax="1026" />
</xml><![endif]--><!--[if gte mso 9]><xml>
<o:shapelayout v:ext="edit">
<o:idmap v:ext="edit" data="1" />
</o:shapelayout></xml><![endif]-->
</head>
<body lang="EN-GB" link="blue" vlink="purple">
<div class="WordSection1">
<p class="MsoNormal"><span style="font-size:11.0pt;font-family:"Calibri","sans-serif";color:#1F497D;mso-fareast-language:EN-US"><o:p> </o:p></span></p>
<p class="MsoNormal"><span style="font-size:11.0pt;font-family:"Calibri","sans-serif";color:#1F497D;mso-fareast-language:EN-US">The additional information would be great to add to the docs since they currently do not seem to cover the combination of use cases.<o:p></o:p></span></p>
<p class="MsoNormal"><span style="font-size:11.0pt;font-family:"Calibri","sans-serif";color:#1F497D;mso-fareast-language:EN-US"><o:p> </o:p></span></p>
<p class="MsoNormal"><span style="font-size:11.0pt;font-family:"Calibri","sans-serif";color:#1F497D;mso-fareast-language:EN-US">How about a bug report on that page ?<o:p></o:p></span></p>
<p class="MsoNormal"><span style="font-size:11.0pt;font-family:"Calibri","sans-serif";color:#1F497D;mso-fareast-language:EN-US"><o:p> </o:p></span></p>
<p class="MsoNormal"><span style="font-size:11.0pt;font-family:"Calibri","sans-serif";color:#1F497D;mso-fareast-language:EN-US">Tim<o:p></o:p></span></p>
<p class="MsoNormal"><span style="font-size:11.0pt;font-family:"Calibri","sans-serif";color:#1F497D;mso-fareast-language:EN-US"><o:p> </o:p></span></p>
<div style="border:none;border-left:solid blue 1.5pt;padding:0cm 0cm 0cm 4.0pt">
<div>
<div style="border:none;border-top:solid #E1E1E1 1.0pt;padding:3.0pt 0cm 0cm 0cm">
<p class="MsoNormal"><b><span lang="EN-US" style="font-size:11.0pt;font-family:"Calibri","sans-serif"">From:</span></b><span lang="EN-US" style="font-size:11.0pt;font-family:"Calibri","sans-serif""> Lorin Hochstein [mailto:lorin@nimbisservices.com]
<br>
<b>Sent:</b> 02 January 2014 18:17<br>
<b>To:</b> Narayan Desai<br>
<b>Cc:</b> openstack-operators@lists.openstack.org<br>
<b>Subject:</b> Re: [Openstack-operators] Problem configuring openvswitch br-ex<o:p></o:p></span></p>
</div>
</div>
<p class="MsoNormal"><o:p> </o:p></p>
<div>
<div>
<p class="MsoNormal">For more details on this, here's the relevant text from the openvswitch FAQ:<o:p></o:p></p>
</div>
<div>
<div>
<p class="MsoNormal"><o:p> </o:p></p>
</div>
<div>
<p class="MsoNormal"><<a href="http://git.openvswitch.org/cgi-bin/gitweb.cgi?p=openvswitch;a=blob_plain;f=FAQ;hb=HEAD">http://git.openvswitch.org/cgi-bin/gitweb.cgi?p=openvswitch;a=blob_plain;f=FAQ;hb=HEAD</a>><o:p></o:p></p>
</div>
<div>
<p class="MsoNormal"><o:p> </o:p></p>
</div>
<div>
<div>
<p class="MsoNormal">Q: I created a bridge and added my Ethernet port to it, using commands<o:p></o:p></p>
</div>
<div>
<p class="MsoNormal"> like these:<o:p></o:p></p>
</div>
<div>
<p class="MsoNormal"><o:p> </o:p></p>
</div>
<div>
<p class="MsoNormal"> ovs-vsctl add-br br0<o:p></o:p></p>
</div>
<div>
<p class="MsoNormal"> ovs-vsctl add-port br0 eth0<o:p></o:p></p>
</div>
<div>
<p class="MsoNormal"><o:p> </o:p></p>
</div>
<div>
<p class="MsoNormal"> and as soon as I ran the "add-port" command I lost all connectivity<o:p></o:p></p>
</div>
<div>
<p class="MsoNormal"> through eth0. Help!<o:p></o:p></p>
</div>
<div>
<p class="MsoNormal"><o:p> </o:p></p>
</div>
<div>
<p class="MsoNormal">A: A physical Ethernet device that is part of an Open vSwitch bridge<o:p></o:p></p>
</div>
<div>
<p class="MsoNormal"> should not have an IP address. If one does, then that IP address<o:p></o:p></p>
</div>
<div>
<p class="MsoNormal"> will not be fully functional.<o:p></o:p></p>
</div>
<div>
<p class="MsoNormal"><o:p> </o:p></p>
</div>
<div>
<p class="MsoNormal"> You can restore functionality by moving the IP address to an Open<o:p></o:p></p>
</div>
<div>
<p class="MsoNormal"> vSwitch "internal" device, such as the network device named after<o:p></o:p></p>
</div>
<div>
<p class="MsoNormal"> the bridge itself. For example, assuming that eth0's IP address is<o:p></o:p></p>
</div>
<div>
<p class="MsoNormal"> 192.168.128.5, you could run the commands below to fix up the<o:p></o:p></p>
</div>
<div>
<p class="MsoNormal"> situation:<o:p></o:p></p>
</div>
<div>
<p class="MsoNormal"><o:p> </o:p></p>
</div>
<div>
<p class="MsoNormal"> ifconfig eth0 0.0.0.0<o:p></o:p></p>
</div>
<div>
<p class="MsoNormal"> ifconfig br0 192.168.128.5<o:p></o:p></p>
</div>
<div>
<p class="MsoNormal"><o:p> </o:p></p>
</div>
<div>
<p class="MsoNormal"> (If your only connection to the machine running OVS is through the<o:p></o:p></p>
</div>
<div>
<p class="MsoNormal"> IP address in question, then you would want to run all of these<o:p></o:p></p>
</div>
<div>
<p class="MsoNormal"> commands on a single command line, or put them into a script.) If<o:p></o:p></p>
</div>
<div>
<p class="MsoNormal"> there were any additional routes assigned to eth0, then you would<o:p></o:p></p>
</div>
<div>
<p class="MsoNormal"> also want to use commands to adjust these routes to go through br0.<o:p></o:p></p>
</div>
<div>
<p class="MsoNormal"><o:p> </o:p></p>
</div>
<div>
<p class="MsoNormal"> If you use DHCP to obtain an IP address, then you should kill the<o:p></o:p></p>
</div>
<div>
<p class="MsoNormal"> DHCP client that was listening on the physical Ethernet interface<o:p></o:p></p>
</div>
<div>
<p class="MsoNormal"> (e.g. eth0) and start one listening on the internal interface<o:p></o:p></p>
</div>
<div>
<p class="MsoNormal"> (e.g. br0). You might still need to manually clear the IP address<o:p></o:p></p>
</div>
<div>
<p class="MsoNormal"> from the physical interface (e.g. with "ifconfig eth0 0.0.0.0").<o:p></o:p></p>
</div>
<div>
<p class="MsoNormal"><o:p> </o:p></p>
</div>
<div>
<p class="MsoNormal"> There is no compelling reason why Open vSwitch must work this way.<o:p></o:p></p>
</div>
<div>
<p class="MsoNormal"> However, this is the way that the Linux kernel bridge module has<o:p></o:p></p>
</div>
<div>
<p class="MsoNormal"> always worked, so it's a model that those accustomed to Linux<o:p></o:p></p>
</div>
<div>
<p class="MsoNormal"> bridging are already used to. Also, the model that most people<o:p></o:p></p>
</div>
<div>
<p class="MsoNormal"> expect is not implementable without kernel changes on all the<o:p></o:p></p>
</div>
<div>
<p class="MsoNormal"> versions of Linux that Open vSwitch supports.<o:p></o:p></p>
</div>
<div>
<p class="MsoNormal"><o:p> </o:p></p>
</div>
<div>
<p class="MsoNormal"> By the way, this issue is not specific to physical Ethernet<o:p></o:p></p>
</div>
<div>
<p class="MsoNormal"> devices. It applies to all network devices except Open vswitch<o:p></o:p></p>
</div>
<div>
<p class="MsoNormal"> "internal" devices.<o:p></o:p></p>
</div>
<div>
<p class="MsoNormal"><o:p> </o:p></p>
</div>
<div>
<p class="MsoNormal" style="margin-bottom:12.0pt"><o:p> </o:p></p>
<div>
<p class="MsoNormal">On Thu, Jan 2, 2014 at 9:45 AM, Narayan Desai <<a href="mailto:narayan.desai@gmail.com" target="_blank">narayan.desai@gmail.com</a>> wrote:<o:p></o:p></p>
<blockquote style="border:none;border-left:solid #CCCCCC 1.0pt;padding:0cm 0cm 0cm 6.0pt;margin-left:4.8pt;margin-right:0cm">
<div>
<p class="MsoNormal">I'm guessing that the installation instructions assume that you have different ethernet interfaces for the host and guests. <o:p></o:p></p>
<div>
<p class="MsoNormal"><o:p> </o:p></p>
</div>
<div>
<p class="MsoNormal">If you want the host to use the same interface that is in use as a bridge, you'll need to add a virtual interface to the bridge that has the host's IP. FWIW, this isn't an openstack issue; it is common to OVS and linux bridging, with even
without a hypervisor in the mix.<o:p></o:p></p>
</div>
<div>
<p class="MsoNormal"> -nld<o:p></o:p></p>
</div>
</div>
<div>
<p class="MsoNormal" style="margin-bottom:12.0pt"><o:p> </o:p></p>
<div>
<div>
<div>
<p class="MsoNormal">On Thu, Jan 2, 2014 at 8:24 AM, Alvise Dorigo <<a href="mailto:alvise.dorigo@pd.infn.it" target="_blank">alvise.dorigo@pd.infn.it</a>> wrote:<o:p></o:p></p>
</div>
</div>
<blockquote style="border:none;border-left:solid #CCCCCC 1.0pt;padding:0cm 0cm 0cm 6.0pt;margin-left:4.8pt;margin-right:0cm">
<div>
<div>
<div>
<p class="MsoNormal">Hi,<o:p></o:p></p>
<div>
<p class="MsoNormal">I'm configuring Neutron on a network node (a virtual machine) having two NICs:<o:p></o:p></p>
</div>
<div>
<p class="MsoNormal"><o:p> </o:p></p>
</div>
<div>
<p class="MsoNormal">eth0: 192.168.120.13<o:p></o:p></p>
</div>
<div>
<p class="MsoNormal">eth1: 10.0.0.13<o:p></o:p></p>
</div>
<div>
<p class="MsoNormal"><o:p> </o:p></p>
</div>
<div>
<p class="MsoNormal">I've followed the official Openstack guide:<o:p></o:p></p>
</div>
<div>
<p class="MsoNormal"><o:p> </o:p></p>
</div>
<div>
<p class="MsoNormal"><a href="http://docs.openstack.org/havana/install-guide/install/yum/content/install-neutron.install-plug-in.ovs.html" target="_blank">http://docs.openstack.org/havana/install-guide/install/yum/content/install-neutron.install-plug-in.ovs.html</a><o:p></o:p></p>
</div>
<div>
<p class="MsoNormal"><o:p> </o:p></p>
</div>
<div>
<p class="MsoNormal">When I issue the command (step 4)<o:p></o:p></p>
</div>
<div>
<p class="MsoNormal"><o:p> </o:p></p>
</div>
<div>
<p class="MsoNormal">ovs-vsctl add-port br-ex eth0<o:p></o:p></p>
</div>
<div>
<p class="MsoNormal"><o:p> </o:p></p>
</div>
<div>
<p class="MsoNormal">the terminal I'm working on freezes, and the connection to 192.168.120.13 is definitely lost, and I can't reconnect to it anymore from any other host.<o:p></o:p></p>
</div>
<div>
<p class="MsoNormal"><o:p> </o:p></p>
</div>
<div>
<p class="MsoNormal">I suspect there's some inaccuracy in the installation instructions, and in addition I'm not an expert on bridge and interfaces stuff.<o:p></o:p></p>
</div>
<div>
<p class="MsoNormal"><o:p> </o:p></p>
</div>
<div>
<p class="MsoNormal">Can someone explain me what's wrong and if there's a better documentation for a complete Neutron installation and configuration ?<o:p></o:p></p>
</div>
<div>
<p class="MsoNormal"><o:p> </o:p></p>
</div>
<div>
<p class="MsoNormal">thank you very much,<o:p></o:p></p>
</div>
<div>
<p class="MsoNormal"><o:p> </o:p></p>
</div>
<div>
<p class="MsoNormal">Alvise<o:p></o:p></p>
</div>
</div>
<p class="MsoNormal"><o:p> </o:p></p>
</div>
</div>
<p class="MsoNormal" style="margin-bottom:12.0pt">_______________________________________________<br>
OpenStack-operators mailing list<br>
<a href="mailto:OpenStack-operators@lists.openstack.org" target="_blank">OpenStack-operators@lists.openstack.org</a><br>
<a href="http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-operators" target="_blank">http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-operators</a><o:p></o:p></p>
</blockquote>
</div>
<p class="MsoNormal"><o:p> </o:p></p>
</div>
<p class="MsoNormal" style="margin-bottom:12.0pt"><br>
_______________________________________________<br>
OpenStack-operators mailing list<br>
<a href="mailto:OpenStack-operators@lists.openstack.org">OpenStack-operators@lists.openstack.org</a><br>
<a href="http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-operators" target="_blank">http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-operators</a><o:p></o:p></p>
</blockquote>
</div>
<p class="MsoNormal"><br>
<br clear="all">
<o:p></o:p></p>
<div>
<p class="MsoNormal"><o:p> </o:p></p>
</div>
<p class="MsoNormal">-- <o:p></o:p></p>
<div>
<p class="MsoNormal">Lorin Hochstein<o:p></o:p></p>
<div>
<p class="MsoNormal">Lead Architect - Cloud Services<o:p></o:p></p>
</div>
<div>
<p class="MsoNormal">Nimbis Services, Inc.<o:p></o:p></p>
</div>
<div>
<p class="MsoNormal"><a href="http://www.nimbisservices.com" target="_blank">www.nimbisservices.com</a><o:p></o:p></p>
</div>
</div>
</div>
</div>
</div>
</div>
</div>
</div>
</body>
</html>