I recently added update logic which had a severely faulty
assumption. That assumption was that an instnace object was
always going to be passed to update(). Since that is not the
case we'll have to revisit this logic.
Change-Id: Ib2303d8719d2f3f8b5c123168864c97d64881544
Add a check when creating the volume definition for the libvirt manager
to use the apporpiate driver for the disk, according to [1].
[1] http://libvirt.org/formatdomain.html#elementsDisks
Change-Id: I89cf3bb308cff28194de0beb36d69f0e32224cbe
Updated hostname sanitization method to more closely follow RFC-952
and RFC-1123. Also moved it to nova.utils, where it seems to fit
better.
Fixes bug 885374
(Patch Set 1) Updated hostname sanitization with more efficient and
[opinion] more readable implementation.
Change-Id: I60d7ee89867c05950bec1fd53b072a1c6247ebea
Removed contrib/nova.sh and any references to it in the RST docs.
removed refernece to old livecd that has nova circa 2010 on it.
.gitignore'ing some additional autogenerated doc files.
Change-Id: I7a07a58a9a6f1112fc7e486367a06f6916207784
part 1 of blueprint separate-nova-metadata
* adds api/metadata/ and moves code from ec2
* moves metadata into separate binary
* changes metadata forward to use metadata host and port
* moves the metadata accept rule to the metadata api
* adds nova-api-* to setup.py
Change-Id: I7f5d8e6cafc55b5c383cd88991f29c6059fb8d82
This is actually a bug in optparse itself, but luckily we can work
around it. I'll file it upstream when bugs.python.org's account
registration isn't broken.
Change-Id: I87c3271562caa4336c11fe445475650a9f16950c
With its 'append' action, optparse appends values to the supplied
default value. This leaves the user with no way of overriding the
default value. If you want to support overriding, you need to manually
handle setting the default value after parsing.
gflags supports overriding the default value so we must do the same.
Change-Id: I5810e16806e74876c7a310edbb6f8f27f0a3313b
Related to blueprint internal-uuids. This function also appeared to be
incomplete. It should actually work now.
Change-Id: I77ccd29c7ac5e0cbe60d52a4ff5a64ecdff6fa1a
Move openvswitch-nova to 23 in the boot order.
The openvswitch-nova init.d script used on XenServer has been set to run
at 96 in the boot order (i.e. very late). This is inconvenient, because it
means that it runs after the firstboot scripts, so if you want to do an
automated install of a compute VM, say, you can't rely on the Open vSwitch
rules being ready.
23 places it after the networking start up (9 through 14) and before the
firstboot scripts (24).
Change-Id: I5c4f2f02c78bd7b8ccc6cac4d6549209a6dcbdb0
Jenkins