I'm marking this as invalid. It was mostly user error on my part.
I've got an improved version of the script here at
https://gist.github.com/1169889
** Changed in: nova (Ubuntu)
Status: New = Invalid
--
You received this bug notification because you are a member of Ubuntu
Server
** Changed in: nova (Ubuntu)
Importance: Undecided = Medium
--
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to nova in Ubuntu.
https://bugs.launchpad.net/bugs/812548
Title:
bridge not set up correctly with LXC and all-in-one system
--
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to nova in Ubuntu.
https://bugs.launchpad.net/bugs/812548
Title:
bridge not set up correctly with LXC and all-in-one system
To manage notifications about this bug go to:
** Description changed:
I'm attempting to demo/use LXC backend for nova in EC2, all on a single
system.
- When doing so, I get the following trace:
+ When doing so, I get the trace below. It appears that we can get further by
doing:
+ $ sudo brctl addbr br0
+ $ sudo ifconfig br0 up
+ $
I'm adding an attachment with all of the setup that I did.
The commands were run on a m1.large instance of latest oneiric.
us-east-1 ami-3d965154 ebs/ubuntu-oneiric-daily-amd64-server-20110718
** Attachment added: commands to setup and show failure
Scott-
There is no network manager defined in nova.conf, so nova-network is
defaulting to the VLAN manager which, IIRC, requires a separate physical
interface to be available on which it builds bridges and VLANs, as well
as some config flags in nova.conf. I've attached a modified version of
your
