This commit removes the cloudpipe API from nova. This has been
deprecated since change I415760ff634dd85974f0c3f79e788e633852efb5 and no
longer works without nova-cert and the pending removal of the deprecated
nova-network.
Implements bp remove-nova-cert
Change-Id: Ifd1fb13a5953cc66f9cc2561d30a9efcd3f4c92e
Multi-provider networks are a combination of vxlan and vlan networks.
such a network has a special "segments" field that holds a list
of networks. Each element of this list has the same structure as the 'provider
network attributes'.
These attributes are:
- provider:network_type
- provider:physical_network
- provider:segmentation_id
This patch will retrieve the relevant physical network name from a
multi-provider network
Change-Id: Icb9a546e6fcbf399fcef3e9ea686b35ec3817cd5
Closes-Bug: #1659467
We're seeing a trace in gate jobs, for example:
UnicodeDecodeError: 'ascii' codec can't decode byte 0xc3 in position
402: ordinal not in range(128)
when attempting to log an Instance object with a unicode display name.
This resurfaced relatively recently because of the change in devstack
to use the new OSJournalHandler with use_journal=True which is
suspected of causing some deadlock issues [1] unrelated to this bug.
The problem occurs in code that logs an entire Instance object when
the object has a field with unicode characters in it (display_name).
When the object is sent to logging, the UnicodeDecodeError is raised
while formatting the log record here [2]. This implies an implicit
conversion attempt to unicode at this point.
I found that with the Instance object, the conversion to unicode fails
with the UnicodeDecodeError unless the encoding 'utf-8' is explicitly
specified to six.text_type(). And when specifying an encoding to
six.text_type(), the argument to convert must be a string, not an
Instance object, so this does the conversion in two steps as a utility
function:
1. Get the string representation of the Instance with repr()
2. Call six.text_type(instance_repr, 'utf-8') passing the encoding
if not six.PY3
Closes-Bug: #1580728
[1] https://review.openstack.org/#/c/462163
[2] https://github.com/python/cpython/blob/2e576f5/Lib/logging/__init__.py#L338
Change-Id: I0fc3ae02cb2e401b3240faf0d8b6aa5dc52b91fc
This commit fixes a small typo in the wsgi-applications release note,
it's mod_proxy_uwsgi not mod_proxy_uwsgx.
Change-Id: Ibbd6c19b41c0290ffeaa0371a8d084191f0919be
When any vm creation fails because of exceeding 'gigabytes',
'volumes', 'per_volume_gigabytes' quotas, the error message
generated is specific to 'volumes' quota which says
"Volume resource quota exceeded". Instead, the error message
should be specific to the quota which failed.
Change-Id: I9c1ac2cd4752d5aac20d06407792647b4549ad3d
Closes-Bug: 1680457
This patch adds server-metadata related routes by a plain list,
instead of using stevedore. After all the Nova API endpoints moves to the
plain routes list, the usage of stevedore for API loading will be removed
from Nova.
Partial-implement-blueprint api-no-more-extensions-pike
Change-Id: I88ca06d63016ffd1e38b61e6de0b75f88ecdb138
This provides a brief explanation of the new nova-api-wsgi [1] and
nova-metadata-wsgi [2] scripts in the Architecture section of the devref
with links to the new doc added to the man pages for the eventlet
scripts.
The nova-api.rst mentioned ec2 so figured best to fix that now
rather than forget about it, despite not being entirely germane.
There is also a reno note that indicates the availability of the new
scripts.
There is a devstack change which is testing the new wsgi scripts as
well as forcing grenade to not use them at
If2d7e363a6541854f2e30c03171bef7a41aff745
[1] I7c4acfaa6c50ac0e4d6de69eb62ec5bbad72ff85
[2] Icb35fe2b94ab02c0ba8ba8129ae18aae0f794756
Change-Id: I351b2af3b256d3031bd2a65feba0495e815f8427
Related-Bug: #1661360
Modify the wsgi application for the compute api so that it can be
used by different services and use it for the metadata service,
resulting in a wsgi script named nova-metadata-wsgi.
Change-Id: Icb35fe2b94ab02c0ba8ba8129ae18aae0f794756
The restart code for the live migration configure on the fly tests was
really really fragile clippings of old bits of devstack code that
barely worked (and assumed a very specific run environment).
Given that we're going to get rid of everything other than systemd in
devstack, just jump straight to using systemd primitives here. This
dramatically simplifies the code, and will ensure things actually
restart correctly.
Closes-Bug: #1687511
Change-Id: I914430d68f64d29932c9409d055b15e4cb384ec4
Right now, we can't build Nova package in RDO because the tooling still
find some bits for nova-cert in Nova codebase.
This patch aims to purge them:
- man entry for nova-cert
- nova-cert binary in setup.cfg
Change-Id: Iebee0fbcdad5808e6543e3bcad10ea1f08b8f306
This patch adds os-assisted-volume-snapshots related routes
by a plain list, instead of using stevedore. After all the Nova
API endpoints moves to the plain routes list, the usage of stevedore
for API loading will be removed from Nova.
Partial-implement-blueprint api-no-more-extensions-pike
Change-Id: I1dabc1021e6899d5d5c293e3af3eccfba8d245e2
This patch adds os-agents related routes by a plain list, instead
of using stevedore. After all the Nova API endpoints moves to
the plain routes list, the usage of stevedore for API loading will be
removed from Nova.
Partial-implement-blueprint api-no-more-extensions-pike
Change-Id: Ie34c861cdcab5ae7ea73e8c00e9c190ae6a32a94
This patch adds os-floating-ip-dns related routes by a plain list, instead
of using stevedore. After all the Nova API endpoints moves to
the plain routes list, the usage of stevedore for API loading will be
removed from Nova.
Partial-implement-blueprint api-no-more-extensions-pike
Change-Id: Id0df46d980c8141e6207d221e9bbe1d31f50aea3
Jenkins