per commit 00eca5fdd352be7db52bbf89496762023db4a951
nova is failing here:
logs.openstack.org/87/523387/32/check/requirements-check/408e28c/job-output.txt.gz
Change-Id: Ie63f47fc403704af7ba16a29cc58cd914172f6bd
The previous implementation doesn't support live migration in
pool-based multi-hosts OpenStack environments. Modify code to
support it.
In this patch we will,
1. Support live migration in XAPI pool:
-Add code to support resource pre-check before live migration.
-Add code to support resource clean after live migration.
-Add code to support using local storage in xapi pool.
Depends-On: I80007bb897a1f7eda47ebda82e08fe270f97ff40
Implements: blueprint live-migration-in-xapi-pool
Change-Id: I6437a315f1400a73f7a149bed5550f6d6dd1406f
Exposes flavor extra_specs in the flavor representation since
microversion 2.61. Now users can see the flavor extra-specs
in flavor APIs response only and do not need to call
``GET /flavors/{flavor_id}/extra_specs`` API.
Flavor extra_specs will be included in Response body of the
following APIs:
* ``GET /flavors/detail``
* ``GET /flavors/{flavor_id}``
* ``POST /flavors``
* ``PUT /flavors/{flavor_id}``
Part of blueprint add-extra-specs-to-flavor-list
Change-Id: I048747633babf690a63c6de9773bff5547872053
Replace mox with mock in nova/tests/unit/test_utils.py.
The 'test_supports_direct_io' method is
in the 'GetEndpointTestCase' class currently.
But it should be in an isolated test class.
So add the test class and move the method into it.
Then split the method into methods for each test case
to improve readability.
Change-Id: Id2350529b3322dfa8f7c13ac8e5f85aaf3041082
Implements: blueprint mox-removal
Closes-Bug: #1760017
It is a follow-up for If01b2dcfa9df8c0e80ad1da65115204fe321891b.
The 'progress' parameter has been changed to an optional parameter
in If01b2dcfa9df8c0e80ad1da65115204fe321891b.
Optional parameters should be after required parameters.
So fix parameter order in rebuild action.
And fix 'adminPass' as well.
Change-Id: I38e0cdd73e9b81b5c4c8bd69c1139f99db3c7773
This patch verifies BDM, fault and scheduler hint parameters.
A subsequent patch will verify other parameters.
Change-Id: If57aa3e37ebaa6fa13718480bb216d10664aa5b1
Partial-Bug: #1738930
Replace stubs.Set with stub_out or mock in
nova/tests/unit/virt/test_virt_drivers.py.
Change-Id: I3af68f745ffb23ef2b5407ccec0bebf4b2645734
Implements: blueprint mox-removal
Fixes ResourceClass.normalize_name to produce the same result in py2 and
py3 even when sharp S ('ß') is part of the input.
We do this by waiting until after replacing non-alphanumerics to upcase.
Change-Id: I431fa29d36d0d633374973fc25168344042d6c1a
Closes-Bug: #1762789
Demonstrates the cited bug by invoking ResourceClass.normalize_name on a
string containing sharp S ('ß'). The result is different for py2 and
py3.
Change-Id: I632995c1a234f26f05ef0b5675e0e22b9866b03d
Related-Bug: #1762789
This introduces a new PowerVM conf option, proc_units_factor, which can
range from 0.05 to 1.0 and will default to 0.1. It is used to calculate
the physical processing power to assign per vCPU, where 1.0 is a whole
physical processor and 0.05 is 1/20th of a physical processor.
Change-Id: I67bfe2a6eff86f1947ada7661fc7c3fed81ed28f
We're well past the point of Placement being required,
so this drops the wording about Newton and Ocata and
just makes the warnings say that Placement is required.
Change-Id: I42730e6ef0ac66efe9122ac3078ca15c1071b080
This option is in the driver interface but was hard coded in the manager
class.
Defaults to old value (10 seconds) if not set in configuration file.
Change-Id: I0c8db2efec6098c017aad2f6588938bc548db139
The last time we incremented versions for libvirt and QEMU was during
the "Pike" release (commit: b980df0, 11-Feb-2017); for "Queens" we
didn't do any. The advertized NEXT_MIN_{LIBVIRT,QEMU} versions during
"Pike" release were set to: libvirt 1.3.1 and QEMU 2.5.0 -- but they
weren't actually bumped for "Queens". They will be applied for the
"Rocky" release.
Based on the LibvirtDistroSupportMatrix[*], this patch announces a
version increment for libvirt and QEMU that will be applied for the
"Stein" release, with predicted minimum versions setting libvirt to
3.0.0 and QEMU to 2.8.0.
[*] https://wiki.openstack.org/wiki/LibvirtDistroSupportMatrix
Change-Id: I872304f99e3401f9c09d61b5511300ef9c5c7e8d
This patch removes using mox in the following test classes.
* GenerateEphemeralTestCase
* StreamDiskTestCase
* VMUtilsSRPath
* CreateKernelRamdiskTestCase
This patch completes removing using mox
except where 'stubout_session' is used
in nova/tests/unit/virt/xenapi/test_vm_utils.py.
The 'stubout_session' will be modified
at the same time when nova/tests/unit/virt/xenapi/stubs.by
is modified in another patch.
Change-Id: I138657464aecf6712804a87f102a430c242d85a4
Implements: blueprint mox-removal
This patch removes using mox in the following test classes.
* ResizeHelpersTestCase
* CheckVDISizeTestCase
* ShutdownTestCase
* CreateVBDTestCase
Subsequent patches will remove using mox in another test class
in nova/tests/unit/virt/xenapi/test_vm_utils.py.
Change-Id: Ie3376145c1779b4163537194727c4541db38cfaf
Implements: blueprint mox-removal
This patch removes using mox in the following test classes.
* LookupTestCase
* XenAPIGetUUID
* FetchVhdImageTestCase
Subsequent patches will remove using mox in another test class
in nova/tests/unit/virt/xenapi/test_vm_utils.py.
Change-Id: Ie40f36b717d935d010e40d2ab29bac647c77b02d
Implements: blueprint mox-removal
currently we have following output:
$ curl http://169.254.169.254/openstack
2012-08-10
2013-04-04
2013-10-17
2015-10-15
2016-06-30
2016-10-06
2017-02-22
latest
Change-Id: I6b4aed63d5c981abc9374baf929f05b26760e645
While debugging something I noticed that we are dumping stack when we
intentionally abort a build. When we raise BuildAbortException, it means
we have caught some situation and are handling it, setting error states
and such. We do not need to dump stack in that situation, and doing so
pollutes the logs. We already dump stack when we catch an unexpected
exception in the same path, which makes sense.
This just changes that LOG.exception to LOG.error and adds a trivial
test verification to make it clear that it is the behavior we want.
Change-Id: I4e3343f250ee563e87001b0e17ab19dc872caa66
* Remove unnecessary parameter description
* Fix a format of the comments
* Fix a wrong method name (self.obj_what_changed())
TrivialFix
Change-Id: If5db63bf1b63ca8f1ef7b73c5f798122275b7cd3
The original check in Ibfa64f18bbd2fb70db7791330ed1a64fe61c1355 only
blocked swap volume _from_ an encrypted LUKS volume while using native
QEMU decryption. This change expands that check to also block swap
volume when swapping _to_ an encrypted LUKS volume while using native
QEMU decryption, regardless of the original volume being encrypted.
Change-Id: I258127fdcd011ccec721d5ff62eb7f128f130336
Closes-bug: #1749418
Zuul