Compile BigInteger to INTEGER for sqlite

Ensure BigInteger does not map to BIGINT for an auto-created
sqlite registry DB, as this type is not supported by sqlite.

Refactoring a test to use generic unsupported column type

Fixes bug 1147879

Change-Id: I590c798dd470def286802bc6e00bb4b621332b8d
Fixes nbd device can't be released error

When the 'mount' operation is successful but stderr is not empty during
injecting key/file into image, there may be some warning messages output to
stderr, so we need to discard them and continue to inject files into image.

Fixes bug #1152519

Change-Id: Icc7d15196f3ee67674f9d815ddeef4378f363e2c
Remove instance['instance_type'] relationship from db api

This removes the entire relationship between an instance and the flavor
it was created from. As such, it removes two tests entirely which
examined the old behavior.

This is one change in a series aimed at removing the use of instance-linked
instance_type objects, in favor of the decoupled type data in
system_metadata. See bug 1140119 for more details.

Change-Id: I8b525a900bf2dc6b193e54aae35fc32248e4cff4
Rename LLC to Foundation

Looks like we missed one file

Change-Id: I556488923f892ce45334e18d3a089514fccd2d2d
Return XML message with objectserver 404.

Resolves bug 1076534 by adding a XML formatted message to HTTP
requests which result in a status of 404.

Change-Id: I4afbdc0f6bd5f3a78729351cee570c50952a6843
Force resource updates to update updated_at

When there's no changes in resources, compute_node_update (and other
DB update calls) won't modify 'updated_at'.

'updated_at' is what is used to invalidate the cache in the scheduler's
host_manager.  Because of a race with the compute manager, the scheduler
could be out of sync with the compute_nodes table but have a newer time
on its cache.

By always updating 'updated_at' on resource updates, the periodic task
will be sure to invalidate any bad cache the scheduler has.

Fixes bug 1153778

Change-Id: I19b51a5b84f472cd0f4de6460a4edb540cc62da2
Deprecate CONF.fixed_range, do dynamic setup

Do dynamic fixed_range setup by pulling the networks that should
exist on the host and making the appropriate calls to set up the NAT
entries for each network. This allows for non-contiguous subnets to
be configured in the fixed_ip space and only configures the NAT rules
as they are needed. This also restricts the NAT range to the smallest
range required preventing the NAT from impacting subnets that might
exist on the external network.

DocImpact: For backwards compatibility, Grizzly will still support
the CONF.fixed_range option and if set will perform the default logic
from Folsom and earlier releases. To use the new dynamic fixed_range
setup in Grizzly, set fixed_range='' in your nova.conf. The intention
is to remove the CONF.fixed_range option entirely early in the Havana
cycle and use the dynamic fixed_range setup from Havana going
forward.

Change-Id: I4ec111079f7a1d253190e6a6008048f992a53f68
Fixes: bug #741626 bug #966175
Merge "Return XML message with objectserver 404."
Merge "Rename LLC to Foundation"
Merge "Deprecate CONF.fixed_range, do dynamic setup"
Merge "Remove instance['instance_type'] relationship from db api"
Merge "Force resource updates to update updated_at"
Merge "Fixes nbd device can't be released error"
websockify 0.4 is busted

This was just released and it is broken, stalling our gates.  When
attempting to install it, we get:

"error: can't copy 'include/util.js': doesn't exist or not a regular
file"

Change-Id: I9d93bff92cc4a9d837382acce78bff587f52fb99
Merge "websockify 0.4 is busted"
Merge "Compile BigInteger to INTEGER for sqlite"