I was running Folsom on Quantal with nova-network using a
FlatDHCPManager and upgraded to Raring today, which upgrades to Grizzly.
After working through config files, trying to launch a 12.04.2 LTS
instance, the VM console log shows:
Begin: Running /scripts/init-bottom ... done.
[
On 04/13/2013 03:07 PM, Blair Zajac wrote:
The ci-info lines show it coming up with 192.168.1.2 but it should be
with 192.168.2.2. There's a router providing DHCP on the network that
the host is on, so maybe that's where it's getting the 192.168.1.2 address?
I disabled the DHCP server
On 04/13/2013 03:29 PM, Blair Zajac wrote:
On 04/13/2013 03:07 PM, Blair Zajac wrote:
The ci-info lines show it coming up with 192.168.1.2 but it should be
with 192.168.2.2. There's a router providing DHCP on the network that
the host is on, so maybe that's where it's getting the 192.168.1.2
release unless you intend to follow the ubuntu update cycle.
You'll end up suffering a great deal by not doing so.
=/
-Matt
On Wed, Jan 23, 2013 at 8:32 AM, Blair Zajac bl...@orcaware.com
mailto:bl...@orcaware.com wrote:
Thanks for the link. It appears that my case is not explicitly
I noticed that Grizzly-2 is in 13.04. I'd like to run them in 12.10 and not
update the entire OS.
What's the best and/or easiest way of doing this?
1) Get the source packages and build them in a PPA? If so, what is the
complete list of source packages and build order to do this correctly?
- check the Ubuntu wiki pages on it:
https://wiki.ubuntu.com/ServerTeam/CloudArchive
Regards,
Kev
On 23 January 2013 15:01, Blair Zajac bl...@orcaware.com wrote:
I noticed that Grizzly-2 is in 13.04. I'd like to run them in 12.10 and not
update the entire OS.
What's the best
I've set up a new Folsom instance on an Ubuntu 12.10 system. Trying to
launch a new instance booting from a volume snapshot, which failed with
the below stacktrace saying that nova-volumes cannot be found. This
suggests to me that nova is using nova-volumes instead of cinder, even
though
On 01/22/2013 12:42 PM, Vishvananda Ishaya wrote:
On Jan 22, 2013, at 12:32 PM, Blair Zajac bl...@orcaware.com wrote:
/usr/bin/nova-volume
The wrong bin is running. You should be running /usr/bin/cinder-volume if you
are using cinder.
It doesn't look like you have configured cinder
On 01/22/2013 01:01 PM, Blair Zajac wrote:
On 01/22/2013 12:42 PM, Vishvananda Ishaya wrote:
On Jan 22, 2013, at 12:32 PM, Blair Zajac bl...@orcaware.com wrote:
/usr/bin/nova-volume
So I don't know where it's picking up /usr/bin/nova-volume. The stack
is appearing in nova-volume.log
9 matches
Mail list logo
