Use the new oslo.report config option for specifying a
log_dir in which the GMR reports can be generated in.
consolidate the gmr related setup code in config.py
Introduced in oslo.reports change id:
I9ed0191628f2d552acd8130687b636671bc07a3e
Change-Id: Ib5edf65fd33ce86757f7cb1a6546a6f00738c9a3
This mirrors the indirection fixture override that we have for
object_class_action() while we transition fully to the base
VersionedObjectRegistry. This prevents us from breaking with current
oslo.versionedobjects.
This also caused a few other tests to get run with manifest calls,
which needed to be converted to continue to work.
Change-Id: I2aaa42784b2cc5c6898a3fac0c951dd57dd4f4c6
Closes-Bug: #1516805
The unit test logs currently contain 9 of the following warnings. Short
circuit and return an empty list in these cases rather than executing
the query needlessly.
SAWarning: The IN-predicate on "<table>.<column>" was invoked with
an empty sequence. This results in a contradiction, which nonetheless
can be expensive to evaluate. Consider alternative strategies for
improved performance.
Change-Id: I19460ed4e03a0db66186a4c231d315c2396b7eca
The novaclient already has the following service commands:
service-disable Disable the service.
service-enable Enable the service.
service-list Show a list of all running services.
host-describe Describe a specific host
This covers what nova-manage service was providing so let's
deprecate the legacy nova-manage subcommand and mark it for
removal in the N release.
UpgradeImpact: nova-manage service is deprecated, use novaclient
DocImpact: update openstack operations guide
Implements: bp deprecate-service-management-in-nova-manage
Change-Id: I3e625dbf39f5831157104f5c368acd53b1899f76
The new test_schedule_to_all_nodes test fails in some epic ways in
cells. Not really worth debugging, this is a new test and had just
exposed another cells / devstack issue. Just skip the test.
Change-Id: Icc71e36f4ecb015dff9e806caacd31262f7e17f7
The original support for Opaque networks make use of a
configuration flag indicating that a global integration bridge
was configured on the ESX host. If this global integration
bridge was used then that would be selected as the opaque network.
The next generation NSX neutron plugin will not make use of the
integration bridge. This will require that we make use of the network
ID for the opaque network.
The support for VC 6.0 has specific support for this. For 5.5 we make
use of a DynamicProperty setting to achieve the same goal.
DocImpact
For backward compatible opaque support the setting
'CONF.vmware.integration_bridge' needs to be set.
If this is not set then the network id will be used as the
opaque id.
In addition to this the default value has been set to 'None'.
Implements blueprint vmware-expand-opaque-support
Change-Id: I309ca2bc8186b8eefc0a979d039dd4cd2a6f89f6
is_volume_backed_instance() assumed from old times, that if image_ref
is not set, the instance is always volume backed. This is not true
anymore, since block device mappings can also reference images as
source. This fix adapts the test cases and function accordingly.
Change-Id: Ie83d8d8154d372991fb37dae0def37e3f4583090
Closes-Bug: #1501851
Right now to check if some part of code supports
requested microversion developer usually:
1. get a microversion from request.
2. create instance of class APIVersionRequest
with requested microversion.
3. compare these two objects.
This check takes at least 2 lines and looks ugly.
Sometimes developers create unnecessary class fields
to store object APIVersionRequest with requested microversion.
To make nova code more readable and simple method
'is_supported' was created.
Microversion check with this method takes only one line
and code looks more beautiful.
Change-Id: I9078cfa1afad8b6b09583dac87fa757a0cc32daa
Davanum Srinivas