The following commit missed to bump the related list when bumping the
object version.
commit 1d4ad44f15
Author: Przemyslaw Czesnowicz <przemyslaw.czesnowicz@intel.com>
Date: Thu Nov 20 12:04:05 2014 +0000
Add numa_node to PCIDevice
The change extends the PCI device model and its DB representation.
Query libvirt for the PCI devices numa node.
This patch adds the necessary changes to master. We only bump the
PciDeviceList version, and add a backporting rule to obj_relationship
dictionary of the Instance object, to start sending the new version with
1.20 version of the instance (we are currently on 1.21).
Landing this patch fixes versioning going forward, and all interactions
that request the PciDeviceList through the Instance object, however
applying the stable/kilo backport of this is required for Kilo nodes to
start requesting the latest version of PciDevice through PciDeviceList.
We can't send 1.2 PciDeviceList to Kilo nodes yet because of
related-bug 1475254 , so we have to backport this to Kilo first before
we can start sending the 1.2 to Kilo nodes.
Related-bug: #1474074
Change-Id: Id743848061d2bcd64d785979c7a11ee7c945f06b
Now the resource tracker has been converted to objects
there is no need for a reference to the conductor api.
This change removes obsolete references to conductor
from the resource tracker and related tests.
Change-Id: Ibf843e843975e3f0addb1471b31786e355b5beab
Partially-Implements: blueprint make-resource-tracker-use-objects
Commit 2ef014eb31 changed resource_tracker
to use the ComputeNode object instead of direct conductor calls. There
are a couple tests in test_tracker that assert that things are not called
which didn't get updated after this change (since they were still not
being called). This patch fixes those up.
Co-Authored-By: Paul Murray <pmurray@hp.com>
Change-Id: I6aaa927d08e5fa24163b4bad38f98586a063d14a
* Fix sort(): dictionaries are no more comparable on Python 3, use a key
function building a sorted list of the dictionary items
* Replace __builtin__ with six.moves.builtins
* get_hash_str() now accepts Unicode: Unicode is encoded to UTF-8
before hashing the string. Mention also the hash method (MD5) in the
docstring.
* LastBytesTestCase: use binary files instead of text files. Use also a
context manager on the TemporaryFile to ensure that the temporary file
is closed (even on error).
* Functions: use the __code__ attribute instead of func_code, and
__closure__ instead of func_closure. These attributes are also
available on Python 2.6.
* Replace unichr() with six.unichr()
* SafeTruncateTestCase(): write directly the chinese Unicode character
instead of using safe_decode() (which is not reliable, it depends on
the locale encoding!)
* sanitize_hostname(): On Python 3, decode the hostname from Latin1 to
get back Unicode. Add also a comment explaining the purpose of the
conversion to Latin1.
* last_bytes(): replace the hardcoded constant 22 with errno.EINVAL and
add a comment explaining how the function works.
* tox.ini: add nova.tests.unit.test_utils to Python 3.4
Blueprint nova-python3
Change-Id: I96d9b0581ceaeccf9c35e0c9bada369e9d19fd15
Changeset ed9f1b8b restricted the allowed options for iscsi_iface
to the allowed transports mentioned in the help text. iface &
transport are distinct entities for open-iscsi, and an iface is
generally a mix of transport plus an underlying interface, hence
this change was incorrect. This breaks transport support and is
generally incorrect, hence reverting
Closes-Bug:1466730
Change-Id: I687fb9c95133dbbb193004df44794404b58ca692
This reverts commit 5b4083f8cb
There are gate failures spiking with InstanceUpdateConflict
since this merged, the exception isn't being handled like
how UnexpectedTaskStateError would be handled, so we need
to think about this some more before landing it.
Change-Id: I1d2868eac456052a9ce05a7b8c838eff817d89a4
Closes-Bug: #1474550
The sphinx latex generation generates invalid latex that won't compile
when you try to use it.[1][2] This commit adds a helper script to generate
the sphinx latex and then modify it so it'll work. It depends on
ImageMagick convert and sed being available to work.
[1] https://github.com/sphinx-doc/sphinx/issues/1907
[2] https://github.com/sphinx-doc/sphinx/issues/1959
Change-Id: Id289c10907aaddae2483f18b39063852ec699d66
test_save_updates_numa_topology has a rather complex nova object to
represent numa. This includes items which are sets, but must be
converted to lists for json. This is not a stable output operation
across all space and time. The mock comparator was failing here some
times because of it.
Instead, we can manually inspect the parameter in question with our
json comparator to ensure that it is correct.
Closes-Bug: #1473949
Change-Id: Ibfa441356d10417e2b1e092826562ad03d8cfd02
For v2.1 quota_class API, all the hard-code permission was deleted.
The quota_class code is un-winded except the policy enforcement at
REST API entrance.
This patch adjusts the request context in the unittest, use non-admin
context for all the v2.1 unittest.
Partially implements bp nova-api-policy-final-part
Change-Id: I0a70c092d572d0989dd6fd7f873638a9570817b7
This patch removes db layer hard-code permission checks for
quota_class_create/update.
For v2 API, this patch adds back-comptiable permission checks at REST
API layer.
For v2.1 API, this patch adds new rule for update method.
Partially implements bp nova-api-policy-final-part
SecurityImpact
UpgradeImpact: Due to the db layer permission checks deleted, the policy
rule "os_compute_api:os-quota-class-sets:update" was updated with
a default that match the permission as before. Admin should be notified
to update their policy configuration to keep permission as before.
Change-Id: Icddc7e5cc1c11ab3d272f61a2ef623d3f750030c
This patch removes the hard-code permission checks for db call
quota_class_get_all_by_name.
For v2 api, there already have same hard-code permission checks in REST API
layer, so it is back-compatible.
For v2.1 api, to distinguish show and update permission, this patch adds
new rule for show method.
Partially implements bp nova-api-policy-final-part
SecurityImpact
UpgradeImpact: Due to the db layer permission checks deleted, they need
default policy rule instead of that. In this patch,
"os_compute_api:os-quota-class-sets:show" was updated with a default
rule. Admin will be notfied to update their policy configure file to keep
the behavior as before.
Change-Id: I02da6cc8c766e5f43689449ef63121122f537b5b
This patch removes the hard-code permission checks for db call
reservation_expire.
reservation_expire is only invoked in SchedulerManager. So there isn't
any REST API invoke it. So we can remove the hard-code permission directly.
Partially implements bp nova-api-policy-final-part
Change-Id: Ic872d5d03fb0859a738e4cf2691c94b3963eb0b7
OpenStack Proposal Bot