Open Stack

Yes, I followed your suggestion before you made it :)

I couldn’t resist modifying the OVS race condition workaround and created a test for OVS to be up. No more networking problems.

Expect a patch by Tuesday.

 

Bernd

 

From: Pranav Salunke [mailto:dguitarbite at gmail.com] 
Sent: Monday, November 30, 2015 8:01 PM
To: Bernd Bausch <berndbausch at gmail.com>
Cc: Roger Luethi <rl at patchworkscience.org>; openstack-docs at lists.openstack.org
Subject: Re: [OpenStack-docs] [training-labs] Networking problems

 

Hi Bernd,

 

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!

 

My suggestion for you is to de-activate (not delete) the KVM networks as and when required while running the VirtualBox setup.

 

Regards,
Pranav

 

On Mon, Nov 30, 2015 at 7:04 AM, Bernd Bausch <berndbausch at gmail.com <mailto:berndbausch at gmail.com> > wrote:



-----Original Message-----
From: Roger Luethi [mailto:rl at patchworkscience.org <mailto:rl at patchworkscience.org> ]
Sent: Monday, November 30, 2015 12:40 AM
To: Bernd Bausch <berndbausch at gmail.com <mailto:berndbausch at gmail.com> >
Cc: openstack-docs at lists.openstack.org <mailto:openstack-docs at lists.openstack.org> 
Subject: Re: [OpenStack-docs] [training-labs] Networking problems

(...snip...)

> Both times, the cause was a race condition. The script was moving too fast
for the system. If
> interfaces/bridge are not ready when the neutron-l3-agent comes up, it
marks them as down
> permanently and you'd have to manually fiddle with the database to fix it
(rebooting the services
> or the VMs won't help). I guess we could add a function to fix the
database if the race keeps
> hitting us, but I'd rather fix the race.

I remember you or Pranav mentioning it at the summit. That would be a nice
little project, but since the Liberty install guide is now using
LinuxBridge, perhaps not really worthwhile? I am sure there will be other
races :)

> osbash configures port forwarding for you. In order to log into the
controller node, use:
> $ ssh -p 2230 osbash at localhost
>
> For network, it's port 2231, for compute, port 2232.
>
> Alternatively (starting with VirtualBox 5), you can just open a console on
any running VM (in the
> VirtualBox GUI's VM context menu, select "Show").

Then the documentation (in this case, the README.rst) needs some fixing.
I'll file a bug and correct it.



_______________________________________________
OpenStack-docs mailing list
OpenStack-docs at lists.openstack.org <mailto:OpenStack-docs at lists.openstack.org> 
http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-docs

 

-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.openstack.org/pipermail/openstack-docs/attachments/20151130/31850c17/attachment.html>