Support IPv6 when booting instances

When nova uses neutron, IPv6 addresses may be allocated.  This ensures
those addresses are supported.the patch to modify nova is
https://review.openstack.org/#/c/74252/

Change-Id: I2468d3bcaca9122e5d3f9c98044d57f623630dc3
Closes-bug: #1267685
Sync with Oslo-Incubator

oslo-incubator HEAD was 2eab986ef3c43f8d1e25065e3cbc1307860c25c7

This change brings in a few minor updates to python3 and a bug fix
for deep copy failure in gettextutils.

Change-Id: Id360f3b43d1ad2f67b328206990dd6bdb53c1cd7
Allow admin user to get all tenant's floating IPs

When getting floatingips with Nova API, the results will be filtered
with the 'tenant_id'.
So, we can only get the floatingips belonging to the tenant of the current
context.
When ceilometer invokes novaclient to list floatingips, it will get an
empty list because the tenant is 'service'.
we should allow an admin user to index all tenants's floatingip by adding a
parameter 'all_tenants'.
This patch provides CLI support

Change-Id: I35a2155401247d49017bf3c03341b082cb87750d
Closes-bug: #1262124
Fix session handling in novaclient

Prior to this patch, novaclient was handling sessions in an inconsistent
manner.

Every time we created a client instance, it would use a global
connection pool, which made it difficult to use in a process that is
meant to be forked.

Obviously sessions like the ones provided by the requests library that
will automatically cause connections to be kept alive should not be
implicit. This patch moves the novaclient back to the age of a single
session-less request call by default, but also adds two more
resource-reuse friendly options that a user needs to be explicit about.

The first one is that both v1_1 and v3 clients can now be used as
context managers,. where the session will be kept open (and thus the
connection kept-alive) for the duration of the with block. This is far
more ideal for a web worker use-case as the session can be made
request-long.

The second one is the per-instance session. This is very similar to what
we had up until now, except it is not a global object so forking is
possible as long as each child instantiates it's own client. The session
once created will be kept open for the duration of the client object
lifetime.

Please note: client instances are not thread safe. As can be seen from
above forking example - if you wish to use threading/multiprocessing,
you *must not* share client instances.

DocImpact

Related-bug: #1247056
Closes-Bug: #1297796
Co-authored-by: Nikola Dipanov <ndipanov@redhat.com>
Change-Id: Id59e48f61bb3f3c6223302355c849e1e99673410
Updated from global requirements

Change-Id: I123a065193ea330d71afe2fd2ee3fdcbcbd4a88b
Merge "Fix session handling in novaclient"
Add service-delete subcommand to delete a service

In nova https://review.openstack.org/#/c/39998/ expose an API to delete
a service. Both in V1.1 and V3.

This patch make novaclient support it.

Change-Id: I4aaabc866b464c046b46eda68734f37223c6d6a0
Implements: blueprint support-delete-service
Fix name arg help for volume-type-create

Similar to change I10b1bd6d but for help on an argument rather than the
command itself.

Closes-Bug: #1304570

Change-Id: I4f08ffb6af248ccd7446012765d17c41567f4b38
Merge "Updated from global requirements"
Merge "Allow admin user to get all tenant's floating IPs"
Merge "Fix name arg help for volume-type-create"
Merge "Add service-delete subcommand to delete a service"
Merge "Support IPv6 when booting instances"
Merge "Sync with Oslo-Incubator"