[OpenStack-docs] [training-labs] Networking problems
Bernd Bausch
berndbausch at gmail.com
Mon Nov 30 06:04:42 UTC 2015
-----Original Message-----
From: Roger Luethi [mailto:rl at patchworkscience.org]
Sent: Monday, November 30, 2015 12:40 AM
To: Bernd Bausch <berndbausch at gmail.com>
Cc: 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.
More information about the OpenStack-docs
mailing list