<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=utf-8"><meta name=Generator content="Microsoft Word 15 (filtered medium)"><style><!--
/* Font Definitions */
@font-face
{font-family:"ＭＳ 明朝";
panose-1:2 2 6 9 4 2 5 8 3 4;}
@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;}
@font-face
{font-family:"\@ＭＳ 明朝";
panose-1:2 2 6 9 4 2 5 8 3 4;}
/* Style Definitions */
p.MsoNormal, li.MsoNormal, div.MsoNormal
{margin:0in;
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;}
@page WordSection1
{size:8.5in 11.0in;
margin:99.25pt 85.05pt 85.05pt 85.05pt;}
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-US link=blue vlink=purple><div class=WordSection1><p class=MsoNormal><span style='font-size:11.0pt;font-family:"Calibri",sans-serif;color:#1F497D'>Yes, I followed your suggestion before you made it :)<o:p></o:p></span></p><p class=MsoNormal><span style='font-size:11.0pt;font-family:"Calibri",sans-serif;color:#1F497D'>I couldn’t resist modifying the OVS race condition workaround and created a test for OVS to be up. No more networking problems.<o:p></o:p></span></p><p class=MsoNormal><span style='font-size:11.0pt;font-family:"Calibri",sans-serif;color:#1F497D'>Expect a patch by Tuesday.<o:p></o:p></span></p><p class=MsoNormal><span style='font-size:11.0pt;font-family:"Calibri",sans-serif;color:#1F497D'><o:p> </o:p></span></p><p class=MsoNormal><span style='font-size:11.0pt;font-family:"Calibri",sans-serif;color:#1F497D'>Bernd<o:p></o:p></span></p><p class=MsoNormal><span style='font-size:11.0pt;font-family:"Calibri",sans-serif;color:#1F497D'><o:p> </o:p></span></p><p class=MsoNormal><b><span style='font-size:11.0pt;font-family:"Calibri",sans-serif'>From:</span></b><span style='font-size:11.0pt;font-family:"Calibri",sans-serif'> Pranav Salunke [mailto:dguitarbite@gmail.com] <br><b>Sent:</b> Monday, November 30, 2015 8:01 PM<br><b>To:</b> Bernd Bausch <berndbausch@gmail.com><br><b>Cc:</b> Roger Luethi <rl@patchworkscience.org>; openstack-docs@lists.openstack.org<br><b>Subject:</b> Re: [OpenStack-docs] [training-labs] Networking problems<o:p></o:p></span></p><p class=MsoNormal><o:p> </o:p></p><div><p class=MsoNormal>Hi Bernd,<o:p></o:p></p><div><p class=MsoNormal><o:p> </o:p></p></div><div><p class=MsoNormal>It seems that your KVM networks are interfering with the VirtualBox networks. Yes the networking in VirtualBox is carried out in a different way as w.r.t. KVM but at the same time you cannot use overlapping subnets!<o:p></o:p></p></div><div><p class=MsoNormal><o:p> </o:p></p></div><div><p class=MsoNormal>My suggestion for you is to de-activate (not delete) the KVM networks as and when required while running the VirtualBox setup.<o:p></o:p></p></div><div><p class=MsoNormal><o:p> </o:p></p></div><div><p class=MsoNormal>Regards,<br>Pranav<o:p></o:p></p></div></div><div><p class=MsoNormal><o:p> </o:p></p><div><p class=MsoNormal>On Mon, Nov 30, 2015 at 7:04 AM, Bernd Bausch <<a href="mailto:berndbausch@gmail.com" target="_blank">berndbausch@gmail.com</a>> wrote:<o:p></o:p></p><blockquote style='border:none;border-left:solid #CCCCCC 1.0pt;padding:0in 0in 0in 6.0pt;margin-left:4.8pt;margin-right:0in'><p class=MsoNormal><br><br>-----Original Message-----<br>From: Roger Luethi [mailto:<a href="mailto:rl@patchworkscience.org">rl@patchworkscience.org</a>]<br>Sent: Monday, November 30, 2015 12:40 AM<br>To: Bernd Bausch <<a href="mailto:berndbausch@gmail.com">berndbausch@gmail.com</a>><br>Cc: <a href="mailto:openstack-docs@lists.openstack.org">openstack-docs@lists.openstack.org</a><br>Subject: Re: [OpenStack-docs] [training-labs] Networking problems<br><br>(...snip...)<br><br>> Both times, the cause was a race condition. The script was moving too fast<br>for the system. If<br>> interfaces/bridge are not ready when the neutron-l3-agent comes up, it<br>marks them as down<br>> permanently and you'd have to manually fiddle with the database to fix it<br>(rebooting the services<br>> or the VMs won't help). I guess we could add a function to fix the<br>database if the race keeps<br>> hitting us, but I'd rather fix the race.<br><br>I remember you or Pranav mentioning it at the summit. That would be a nice<br>little project, but since the Liberty install guide is now using<br>LinuxBridge, perhaps not really worthwhile? I am sure there will be other<br>races :)<br><br>> osbash configures port forwarding for you. In order to log into the<br>controller node, use:<br>> $ ssh -p 2230 osbash@localhost<br>><br>> For network, it's port 2231, for compute, port 2232.<br>><br>> Alternatively (starting with VirtualBox 5), you can just open a console on<br>any running VM (in the<br>> VirtualBox GUI's VM context menu, select "Show").<br><br>Then the documentation (in this case, the README.rst) needs some fixing.<br>I'll file a bug and correct it.<o:p></o:p></p><div><div><p class=MsoNormal><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><o:p></o:p></p></div></div></blockquote></div><p class=MsoNormal><o:p> </o:p></p></div></div></body></html>