Update my mailmap

Using new email address.

Change-Id: I95269ca0f937c7950a1ab6f159a2d6bab4c92c06
Updates the documentation for nova unit tests

unit_tests.rst is outdated and does not reflect the recent changes
in the run_tests.sh script. Fix required an update of the usage
output of run_tests.sh as well as changes to some references.
Nova now uses testrepository and flake8.

There were also changes to the examples shown in the section
"Running a subset of tests". All the updated examples were tested.

Removes white spaces at the of end 3 lines.

Change-Id: I3fa040d5682ad94d861cef2a64b19b4da947318b
Closes-Bug: #1219040
Merge "Update my mailmap"
Adds upper bound checking for flavor create parameters

The flavor-create API does validation that root_gb and
other integer values are positive integers but it doesn't
do an upper bounds check to make sure they aren't longs.
If a user tries to create a flavor with an integer value
that is bigger than an int, the python int() method
(used in the validation) will just convert it to a long but
the database model for InstanceTypes defines the column as
an Integer (not a BigInteger) and then the database has
to handle the value.

This changeset adds upperbounds checking for memory_mb,
vcpus, root_gb, ephemeral_gb and swap.

Also adds missing testcase for ephermal_gb validity

Change-Id: I63ef42e6befeff1edb81bc9caded2df2a4654b8c
Closes-Bug: 1243195
Merge "consoleauth: retain havana rpc client compat"
Merge "Remove consoleauth 1.X rpc api"
Merge "Adds upper bound checking for flavor create parameters"
Add V2 rpc api for console

Add support for the 2.0 console rpc API.  This commit retains compatibility
with the older 1.X API to allow continuous deployment without any downtime.

The v2 rev of this API is really simple.  It removes the
get_backdoor_port() method, which was moved to the base rpc API common
to all services in havana.  It also removes some unused parameters.

UpgradeImpact - Deployments doing continuous deployment should follow this
process to upgrade without any downtime with the consoleauth service:

1) Set [upgrade_levels] console=havana in your config.

2) Upgrade to this commit.

3) Once everything has been upgraded, remove the entry in
[upgrade_levels] so that all clients start sending the new 2.0 messages.

Part of blueprint rpc-major-version-updates-icehouse

Change-Id: If05d041c5104b7f4e2e6b035de33cdd695c7a1ae
Remove console 1.X rpc api

A previous change adding support for the 2.x rpc interface but retained
compatibility with 1.x as a transition point.  This commit removes the
old API from the server side.

UpgradeImpact

Part of blueprint rpc-major-version-updates-icehouse

Change-Id: I8a5c4c45baaf237f5be38f6024d5338c8183d1a6
Add V2 rpc api for cert

Add support for the 2.0 cert rpc API.  This commit retains compatibility
with the older 1.X API to allow continuous deployment without any downtime.

The v2 rev of this API is really simple.  It removes the
get_backdoor_port() method, which was moved to the base rpc API common
to all services in havana.

UpgradeImpact - Deployments doing continuous deployment should follow this
process to upgrade without any downtime with the consoleauth service:

1) Set [upgrade_levels] cert=havana in your config.

2) Upgrade to this commit.

3) Once everything has been upgraded, remove the entry in
[upgrade_levels] so that all clients start sending the new 2.0 messages.

Part of blueprint rpc-major-version-updates-icehouse

Change-Id: Icab0d5f380f43c454c166fa3479dacda74d89a02
Remove cert 1.X rpc api

A previous change adding support for the 2.x rpc interface but retained
compatibility with 1.x as a transition point.  This commit removes the
old API from the server side.

UpgradeImpact

Part of blueprint rpc-major-version-updates-icehouse

Change-Id: I0a5d14fc3cbf374744049269883fc14a4850f597
Add V2 rpc api for conductor

Add support for the 2.0 conductor rpc API.  This commit retains compatibility
with the older 1.X API to allow continuous deployment without any downtime.

The v2 rev of this API was determined primarily by copying the current API
in nova.conductor.rpcapi.  That class always reflects the latest rev of the
API that is actually being used.

UpgradeImpact - Deployments doing continuous deployment should follow this
process to upgrade without any downtime with the consoleauth service:

1) Set [upgrade_levels] conductor=havana in your config.

2) Upgrade to this commit.

3) Once everything has been upgraded, remove the entry in
[upgrade_levels] so that all clients start sending the new 2.0 messages.

Part of blueprint rpc-major-version-updates-icehouse

Change-Id: I99a01338fdad4de408ff01dce18268916369783a
Remove conductor 1.X rpc api

A previous change adding support for the 2.x rpc interface but retained
compatibility with 1.x as a transition point.  This commit removes the
old API from the server side.

UpgradeImpact

Part of blueprint rpc-major-version-updates-icehouse

Change-Id: I0cf2a1c21990342ca41ddd2e11e373508a5e67c8
Add v3 of compute rpc API

Add support for the 3.0 compute rpc API.  This commit retains compatibility
with the older 2.X API to allow continuous deployment without any downtime.

The v3 rev of this API was determined primarily by copying the current API
in nova.compute.rpcapi.  That class always reflects the latest rev of the
API that is actually being used.

UpgradeImpact - Deployments doing continuous deployment should follow this
process to upgrade without any downtime with the consoleauth service:

1) Set [upgrade_levels] compute=havana in your config.

2) Upgrade to this commit.

3) Once everything has been upgraded, remove the entry in [upgrade_levels] so
that all clients start sending the new 3.0 messages.

Part of blueprint rpc-major-version-updates-icehouse

Change-Id: I5d303445ded2342a54d8319b79df172ce50fa716
WIP: remove v2 compute rpc api

Change-Id: I31c21055163e94b712d337568b16b9b7a224b52f