Baremetal driver: remove unused states

NULL and INIT were not used since commit c20110d15be37948ddd9ef5f38001328aabf5b1d

Change-Id: I25c34872b100807d691e7e15f7b70be7ad1912b9
Add support for user_id based authentication with Neutron

Keystone v3 supports non-unique project/user names, so until
the Neutron client provides support for the V3 API and domain
based authentication Nova should allow user ID for admin
authentication.

Change-Id: Idad27ff4206d6ba0bb9aedbbff5172c3144ad3c6
DocImpact: Adds new flag, neutron.admin_user_id
Commit quota when deallocate floating ip

It seems that when you allocate a floating-ip in a tenant with nova-network,
its quota is never returned after calling 'nova floating-ip-delete'
even though 'nova floating-ip-list' shows it gone.
This behavior applies to each tenant individually. The gate tests are passing
because they all run with tenant isolation.

The root cause of the problem is cooperation between
commit 23a27e47 and cbbb9de5. db layer code return floatingip_ref
but object layer didn't. This patch fixed the problem by adding return
value from object layer.

Change-Id: Ide1a338b6c33676311028e8738150e146324a8ee
Closes-Bug: #1347156
Live migration is broken for NFS shared storage

One of the new checks, introduced in
I2755c59b4db736151000dae351fd776d3c15ca39
is missing a check against filebased shared storage,
leading to live migration being broken.

Closes-Bug: #1346385
Change-Id: I096ecd6eadc3b13ef918ca1e6c98acdd01556c0d
Remove useless check in _add_retry_host

In populate_retry, the code already check the case with force_hosts
and force_nodes. (https://github.com/openstack/nova/blob/418398dcca5
52497c8488dbbf54a06e21202b295/nova/scheduler/utils.py#L134)
If the retry is disable, populate_retry won't add retry info into
filter_properties.

_add_retry_host is called later than populate_retry. It also check
the force_hosts and force_nodes, that is useless. (https://github.com
/openstack/nova/blob/418398dcca552497c8488dbbf54a06e21202b295/nova/
scheduler/utils.py#L193) It only need check whether retry info exist
in filter_properties or not.

Change-Id: I1f83b4b584d36aa6f894180d43aee24f096b4f78
Update scheduler after instance delete

Previously deleting an instance would update the scheduler resources
fairly quickly. There is now a delay when deleting an instance until the
scheduler makes the resources available again. This appears to be due to
the fact that the delete code path used to call resource tracker to
update the compute_node record but this no longer happens.

Closes-Bug: 1336080
Change-Id: I837b70ce06843ff83481d4985c9c08b74d20cab0
EndpointNotFound deleting volume backend instance

When there is some error in volume creating on booting from volume,
we may get the EndpointNotFound exception when deleting the error instance.
Then we can never delete the instance successfully. The exception should
be ignored.

Change-Id: Ia92b648eb18c70996747d361e227de771f33ee9c
Closes-bug: 1346866
docs - Add an index for the command line utilities

Change-Id: I03376a9159c3ef6c2b65cce417a217db68e8c246
docs - Prevent eventlet exception during docs generation

build_sphinx has a lot of spurious tracebacks, We don't
really need this check for document generation

Change-Id: Id9442c5902918592c4c242cc66975062cf9f2461
docs - Fix indentation for RPC API's

Fix ERROR(s) and WARNING(s) during docs generation because of
bad indentation, spaces etc.

Change-Id: I450e929fbc8e148491b8b0a96a8c6d2aff605ab4
Handle NetworkAmbiguous error when booting a new instance with v3 api

Catch exception.NetworkAmbiguous error and map it to exc.HttpConflict when
using v3 api to create a new instance.

Change-Id: I18b6b9f0d8612a3757f6489dada41b5cd8eca758
Closes-Bug: 1350800
Remove instance_info_cache_delete() from conductor

This was not used in v2.0 of the RPC API, so we can remove it
outright without deprecating it in conductor manager.

Related to blueprint compute-manager-objects-juno

Change-Id: I68068c1d0ef8f346406fe3ccb341a8d0a2474bdd
Handle MacAddressInUseClient exception from Neutron when creating port

This adds exception handling for the new MacAddressInUseClient exception
from python-neutronclient-2.3.6 when trying to create a port with a
specific MAC address.

The PortInUse exception is used so that the build will be rescheduled if
this error is encountered.

Also, the servers API already handles PortInUse and translates it to an
HTTPConflict response.

Closes-Bug: #1347778

Change-Id: I929b5f9d79bcb7e60e8b3482e5ee1ca2fababed1
Revert "Deallocate the network if rescheduling for

Revert "Deallocate the network if rescheduling for Ironic"

This reverts commit 963ad71af4750e28745b6de262da11816b403801.

The original fix, targeted towards Nova BM and Ironic tests
is actually making us have more test failures. Lets go
back to the original race... and then we can have a bit
more time to test a proper fix.

Closes-bug #1346424

Change-Id: Icbbe16ffef69132177165d21c727d791b62a232f
Merge "Revert "Deallocate the network if rescheduling for"
Merge "EndpointNotFound deleting volume backend instance"
Merge "docs - Add an index for the command line utilities"
Merge "docs - Prevent eventlet exception during docs generation"
Merge "Remove useless check in _add_retry_host"
Merge "Handle MacAddressInUseClient exception from Neutron when creating port"