Merge "Handle deleted instance types." into grizzly/1.3
Merge 'Handle deleted instance types (OS-250)' into grizzly/1.4

Conflicts:
	cobalt/nova/api.py

Change-Id: Ib91bb20b7560c074c7ba2020b4a9d34abeeec343
Allowing networks to be specified at launch in the dashboard

OS-252

Adds support for specifying the networks to attach to the launched
instance in the dashboard. Note: similar to the boot workflow, a
network must be specified when using the dashboard. This also only
applies when Quantum/Neutron is used for networking.

Change-Id: I5f4dec4d7baf25de6ff697d6829d5efab4f6a2f7
Merge "Allowing networks to be specified at launch in the dashboard" into grizzly/1.4
Empty merge to harmonize grizzly/1.3 with grizzly/1.4

Change-Id: I64da24dae946d5275810f8a50de4ba854c1c9f1f
Merge 'Networks specified at launch time (OS-252)' into havana/1.4

Change-Id: Ide6f2f647fd96dee2564c75540695902c56fc00b
Merge 'Specify networks in dashboard for launch (OS-252)' into havana/1.4

Conflicts:
	.gitreview
	cobalt/nova/api.py

Change-Id: If49133ed95f682718acc56708e84affca7fb1b7a
Exclusively use fully-loaded instance objects

Fixes OS-261

Ensure that only instance objects are used throughout the manager
and renamed "instance_ref" to "instance" to help reflect this.
This ensure that cobalt uses a consistent type throughout.

When passing an instance object through an RPC call it will get
serialized into a dictionary format. Any fields that were not
loaded will not be present in serialized dictionary. This will
cause errors when the RPC method expects the data to exists.

When loading the intial instance object we explicit ask for all of
the default fields to also be loaded (e.g. metadata). In this way
we do not need to worry about what fields are loaded before making
an RPC request.

Change-Id: I3e8c8bb107c3a9f737543ff979631eb30a4a171a
Use instance_type information stored in instance's system_metadata

Fixes OS-250

The instance_type/flavor is not a reliable source of information
because it can be deleted after an instance has been created from
it. However, all of the instance_type/flavor information is stored
in an instance's system_metadata. The core nova-compute process
uses the system_metadata to reconstruct the instance_type/flavor
when required.

Now cobalt-compute also uses the instance's system_metadata.

Change-Id: I541aa30b845cb1e752e439ec267bc89dbe55d9e6
Merge 'Use flavor information stored in system_metadata (OS-250)' into havana/1.4

Conflicts:
	bin/cobalt-compute
	cobalt/nova/api.py
	cobalt/tests/test_manager.py
	cobalt/tests/utils.py

Change-Id: I57f5a94cd9327b3263af44f55486c81a60c07ba8
Merge branch 'havana/1.4' into havana/1.5

Conflicts:
	.gitreview
	cobalt/nova/extension/manager.py

Change-Id: Idd3f87b5b38c67ea121a99d899fa644163337f70