summaryrefslogtreecommitdiff
path: root/requirements.txt
Commit message (Collapse)AuthorAgeFilesLines
* db: Remove legacy migrationsStephen Finucane2023-02-011-1/+0
| | | | | | | | | sqlalchemy-migrate does not (and will not) support sqlalchemy 2.0. We need to drop these migrations to ensure we can upgrade our sqlalchemy version. Change-Id: I7756e393b78296fb8dbf3ca69c759d75b816376d Signed-off-by: Stephen Finucane <stephenfin@redhat.com>
* Use new get_rpc_client API from oslo.messagingTobias Urdin2023-01-171-1/+1
| | | | | | | | | | | | | | Use the new API that is consistent with the existing API instead of instantiating the client class directly. This was introduced in release 14.1.0 here [1] and added into oslo.messaging here [2] [1] https://review.opendev.org/c/openstack/requirements/+/869340 [2] https://review.opendev.org/c/openstack/oslo.messaging/+/862419 Change-Id: If1128fe0faacef757ed10023c00a67e5ec0440bd
* Enable new defaults and scope checks by defaultGhanshyam Mann2023-01-101-1/+1
| | | | | | | | | | | | | | | | | | | | | | As discussed in PTG, we need to test the new RBAC in the integrated gate and accordingly enable the new defaults and scope check by default. A new integrated testing job has been added and results show that the new defaults and scope checks are working fine. During testing, we found a few bugs in neutron policies but all are fixed now. enforce_scope and enforce_new_defaults are oslo policy config options but they are per service level and the default value can be overridden. Oslo policy 3.11.0 version allows to override the default value for these config options[1] so upgrading the oslo policy version in requirements.txt Depends-On: https://review.opendev.org/c/openstack/devstack/+/869781 Depends-On: https://review.opendev.org/c/openstack/placement/+/869525 [1] https://github.com/openstack/oslo.policy/blob/3.11.0/oslo_policy/opts.py#L125 Change-Id: I977b2daedf880229c8d364ca011f2ea965b86e3a
* Bump minimum version of os-vif to 3.1.0Rodolfo Alonso Hernandez2022-11-141-1/+1
| | | | | | | | | | | | | | This new os-vif version implements [1]. Now os-vif (Nova that uses this library) is responsible of deleting the trunk bridges. No other change is needed in Nova. Please check [2] for context. [1]https://review.opendev.org/c/openstack/os-vif/+/841499 [2]https://lists.openstack.org/pipermail/openstack-discuss/2022-April/028164.html Related-Bug: #1869244 Change-Id: Icb5744497faa8761eb0891cc8c347dfaa71f1f29
* requires os-traits >= 2.9.0Thomas Goirand2022-09-191-1/+1
| | | | | | | | Without the latest version, nova fails many unit tests (it failed with os-traits 2.7.0 at least). Closes-Bug: #1990121 Change-Id: I6b320ae1f9058aaa5bac91c7c7ca60136e0cee5c
* Bump min oslo.concurrencty to >= 5.0.1Balazs Gibizer2022-09-131-1/+1
| | | | | | | | The oslo.concurrency 5.0.1 fixes the fair lock we use heavily in the ResourceTracker. Closes-Bug: #1988311 Change-Id: I68914b2e21726138ee9a178fdf6a8bb6389c09be
* Remove the PowerVM driverStephen Finucane2022-08-021-1/+0
| | | | | | | | | | | | | | The PowerVM driver was deprecated in November 2021 as part of change Icdef0a03c3c6f56b08ec9685c6958d6917bc88cb. As noted there, all indications suggest that this driver is no longer maintained and may be abandonware. It's been some time and there's still no activity here so it's time to abandon this for real. This isn't as tied into the codebase as the old XenAPI driver was, so removal is mostly a case of deleting large swathes of code. Lovely. Change-Id: Ibf4f36136f2c65adad64f75d665c00cf2de4b400 Signed-off-by: Stephen Finucane <sfinucan@redhat.com>
* Fix compatibility with jsonschema 4.xStephen Finucane2022-07-181-0/+1
| | | | | | | | | This changed one of the error messages we depend on [1]. [1] https://github.com/python-jsonschema/jsonschema/commit/641e9b8c Change-Id: I643ec568ee2eb2ec1a555f813fd2f1acff915afa Signed-off-by: Stephen Finucane <sfinucan@redhat.com>
* Remove unused requirementStephen Finucane2022-07-181-1/+0
| | | | | | | | We no longer support Python 3.6 so there's no need for Python 3.6-only dependencies. Change-Id: I139e454a2c6e49a1d5229c90a56d518b0d96ca57 Signed-off-by: Stephen Finucane <sfinucan@redhat.com>
* Drop lower-constraints.txt and its testingGhanshyam Mann2022-04-291-0/+4
| | | | | | | | | | | | | As discussed in TC PTG[1] and TC resolution[2], we are dropping the lower-constraints.txt file and its testing. We will keep lower bounds in the requirements.txt file but with a note that these are not tested lower bounds and we try our best to keep them updated. [1] https://etherpad.opendev.org/p/tc-zed-ptg#L326 [2] https://governance.openstack.org/tc/resolutions/20220414-drop-lower-constraints.html#proposal Change-Id: Ifbc383f6d4c858189cee55e67b4d4274d9c3358a
* Sync rootwrap.conf from oslo.rootwrapTakashi Kajinami2022-04-051-1/+1
| | | | | | | | The current rootwrap.conf file is outdated and doesn't include some parameters. This change updates the content to make it consistent with the latest example file in oslo.rootwrap. Change-Id: I989b7da5ff6afae0c1a476e01c3df07870be5f74
* Add logic to enforce local api and db limitsJohn Garbutt2022-02-241-0/+1
| | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | Local API and DB limits are limits on resources that are counted either as an API request parameter (example: server metadata items) or as records in the database (example: server key pairs). Future patches will make use of this logic, and actually enforce the limits. This patch just adds the infrastructure to allow for the enforcement of the limits. We are moving all existing quotas to be managed via Keystone's unified limits. To stop confusion between injected_file_path_length and injected_file_path_bytes, the unified limit in Keystone will use the latter name to match the name used the API. These local limits are all about preventing excessive load on the API and database and have little to do with resource usage. These limits are represented by keystone registered limits only, accordingly. Local limits include things that just limit items in an API request: * metadata_items * injected_files * injected_file_content_bytes * injected_file_path_bytes Local limits also include things that are stored in the database: * key_pairs * server_groups * server_group_members Some resource names have been changed to prepend a prefix of "server_" in order to disambiguate them from other potential unified limits in keystone: * metadata_items => server_metadata_items * injected_files => server_injected_files * injected_file_content_bytes => server_injected_file_content_bytes * injected_file_path_bytes => server_injected_file_path_bytes * key_pairs => server_key_pairs Note that each of the above are counted via a different scope. This new code ensures that key_pairs are counted per user, server_groups are counted per project and server_group_members are counted per server_group. Note: Previously server_group_member were counted per user inside each server_group, which has proved very confusing, as adding more users into a project increases the maximum size of allowed for a server_group. blueprint unified-limits-nova Change-Id: I0b6f4d29aaee1d71541a95cbecfd0708aac325d2
* Lightbits LightOS driveryuval brave2022-02-221-10/+10
| | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | This commit introduces the LightOS driver for nova. LightOS is a software-defined disaggregated clustered storage solution running on commodity servers with commodity SSDs. It it developed by Lightbits Labs (https://www.lightbitslabs.com) and is actively developed and maintained. LightOS is proprietary but the openstack drivers are licensed under Apache v2.0. The Cinder driver for LightOS currently supports the following functionality: Create volume Delete volume Attach volume Detach volume Create image from volume create volume from image Live migration Volume replication Thin provisioning Multi-attach Extend volume Create snapshot Delete snapshot Create volume from snapshot Create volume from volume (clone) This driver has been developed and has been in use for a couple of years by Lightbits and our clients. We have tested it extensively internally with multiple openstack versions, including Queens, Rocky, Stein, and Train. We have also tested it with master (19.1 xena) and we are working to extend testing to cover additional openstack releases. We are glad to join the openstack community and hope to get your feedback and comments on this driver, and if it is acceptable, to see it merged into the tree. Note: the patch depends on os-brick 5.2.0. That version also increased the lower constraints of several dependencies, thus needs nova to increase those as well in requirements.txt, lower-constraints.txt and setup.cfg. Depends-On: I2e86fa84049053b7c75421d33ad1a1af459ef4e0 Signed-off-by: Yuval Brave yuval@lightbitslabs.com Change-Id: Ic314b26695d9681d31a18adcec0794c2ff41fe71
* Merge "Move optional build dependencies to 'extras'"Zuul2022-02-091-5/+0
|\
| * Move optional build dependencies to 'extras'Stephen Finucane2022-01-281-5/+0
| | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | ...and start skipping the relevant tests in 'nova.tests.unit.virt' if these dependencies are not present. Thanks to hacking rules N311 and N312, which prevent virt drivers using code from other virt drivers, simply skipping the unit tests for a virt driver module is enough to ensure we never load those modules. This means users that want to use the powervm driver can install the required dependencies using e.g. 'pip install .[powervm]', and packagers can choose to skip packaging a dependency safe in the knowledge that the relevant tests will be skipped. Change-Id: I3787f9afd78cd0a7c7feb4dfe1bcb21437b5a128 Signed-off-by: Stephen Finucane <stephenfin@redhat.com>
* | Bump os-traits to 2.7.0Dmitrii Shcherbakov2022-02-091-1/+1
|/ | | | | | | | | The new version contains changes needed by the multi-architecture support and off-path SmartNIC DPU support code. Needed-By: I168d3ccc914f25a3d4255c9b319ee6b91a2f66e2 Needed-By: Ia070a29186c6123cf51e1b17373c2dc69676ae7c Change-Id: Ic1179f3e5e2c1aeb069972f21edffe5b003eb525
* requirements: Remove os-xenapiStephen Finucane2022-01-281-1/+0
| | | | | | | We no longer have a Xen driver. This is an unnecessary dependency. Change-Id: Ic298fa9ac4a8935ce4e0dc17d8842d399d4eb808 Signed-off-by: Stephen Finucane <stephenfin@redhat.com>
* Move ReaderWriterLock to the test treeBalazs Gibizer2022-01-171-1/+0
| | | | | | | | | | | | | | | | The commit I168fffac8002f274a905cfd53ac4f6c9abe18803 added a wrapper around fasteners.ReaderWriterLock to fix up an issue with eventlet. But the wrapper was added to nova.utils module that is use not only by the nova tests but also the nova production code. This made the fixture library a dependency of the nova production code. While the current ReaderWriterLock usage only limited to the nova test sub tree. The I712f88fc1b6053fe6d1f13e708f3bd8874452a8f commit fix the issue of not having fixtures in the nova requirements.txt. However I think a better fix is to move the wrapper to the test subtree instead. This patch does that and restores the state of the requirements.txt Change-Id: I6903ce53b9b91325f7268cf2ebd02e4488579560 Related-Bug: #1958075
* Add fixtures to requirementsTakashi Kajinami2022-01-161-0/+1
| | | | | | | | | | | | The commit 887c445a7a6a17b92a37b6ed1dcdcc7dd009f65d made the nova.utils module dependent on the fixtures library but the change missed updating requirements and the fixtures library is not installed automatically. This change migrates the fixtures library from test-requirements.txt to requirements.txt so that the library is installed without test codes. Closes-Bug: #1958075 Change-Id: I712f88fc1b6053fe6d1f13e708f3bd8874452a8f
* db: Final cleanupsStephen Finucane2021-08-171-5/+2
| | | | | | | | | | | | | | | | | | | | | | | | | | | Some things that were missed in previous patches and are thrown together here: - Add alembic as an explicit dependency (we were getting it transitively from oslo.db). We also bump the sqlalchemy dependency to a 1.4.x release, which is the minimum supported by our chosen version of alembic (more on this below) - Remove tooling related to the old migrations - Fix the tox whitelisting of the flaky MySQL tests On the SQLAlchemy front, we opt for 1.4.13. Technically alembic should support anything from 1.4.0, however, with SQLAlchemy >= 1.4.0, < 1.4.13 we see errors like the following in some tests: sqlalchemy.exc.InvalidRequestError: Entity namespace for "count(instance_mappings.id)" has no property "queued_for_delete" There's nothing specific about this in the release notes for 1.4.13 [1] but it definitely fixes things. [1] https://docs.sqlalchemy.org/en/14/changelog/changelog_14.html#change-1.4.13 Change-Id: I4c8eb13f11aa7471c26a5ba326319aef245c9836 Signed-off-by: Stephen Finucane <stephenfin@redhat.com>
* Merge "Bump oslo.db to 10.0.0"Zuul2021-08-071-1/+1
|\
| * Bump oslo.db to 10.0.0Balazs Gibizer2021-07-211-1/+1
| | | | | | | | | | | | | | | | This makes it possible to partially revert If48dd949ec4d69a09c87178f16d56a2517e21fd8 as one of the warning silenced there now fixed in oslo.db. Change-Id: I0051c0f8694699865bc16636953908d60ba456d2
* | Bump os-resource-classes to 1.1.0Balazs Gibizer2021-07-161-1/+1
|/ | | | | | The 1.1.0 lib contains the new packet rate related resource classes Change-Id: Id5a720d91ee9bb0e660823219ec5a6b55bf523a1
* Use neutronclient's port binding APIsStephen Finucane2021-07-141-1/+1
| | | | | | | | | Take advantage of the neutronclient bindings for the port binding APIs added in neutronclient 7.1.0 to avoid having to vendor this stuff ourselves. Change-Id: Icc284203fb53658abe304f24a62705217f90b22b Signed-off-by: Stephen Finucane <stephenfin@redhat.com>
* Fix oslo policy DeprecatedRule warningsGhanshyam Mann2021-07-041-1/+1
| | | | | | | | | | Since 3.7.0, oslo policy started the DeprecationWarning[1] if deprecated_reason and deprecated_since param are not passed in DeprecatedRule or they are passed in RuleDefault object. [1] https://github.com/openstack/oslo.policy/blob/3.7.0/oslo_policy/policy.py#L1538 Change-Id: Idbbc203c6ae65aee29f9463a4911bae2bb541f41
* Use the new type HostDomainOpt.Daniel Bengtsson2021-05-191-1/+1
| | | | | | | | | | Use the new oslo.confg type HostDomainOpt to support underscore in the name. You can see the bugzilla[1] to have more information. [1] https://bugzilla.redhat.com/show_bug.cgi?id=1868940 Related-Bug: #1892044 Change-Id: Ib6c8fc1e3d90b79b10066c429670fcb957bddd23
* libvirt: Delegate OVS plug to os-vifStephen Finucane2021-04-301-1/+1
| | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | os-vif 1.15.0 added the ability to create an OVS port during plugging by specifying the 'create_port' attribute in the 'port_profile' field. By delegating port creation to os-vif, we can rely on it's 'isolate_vif' config option [1] that will temporarily configure the VLAN to 4095 (0xfff), which is reserved for implementation use [2] and is used by neutron to as a dead VLAN [3]. By doing this, we ensure VIFs are plugged securely, preventing guests from accessing other tenants' networks before the neutron OVS agent can wire up the port. This change requires a little dance as part of the live migration flow. Since we can't be certain the destination host has a version of os-vif that supports this feature, we need to use a sentinel to indicate when it does. Typically we would do so with a field in 'LibvirtLiveMigrateData', such as the 'src_supports_numa_live_migration' and 'dst_supports_numa_live_migration' fields used to indicate support for NUMA-aware live migration. However, doing this prevents us backporting this important fix since o.vo changes are not backportable. Instead, we (somewhat evilly) rely on the free-form nature of the 'VIFMigrateData.profile_json' string field, which stores JSON blobs and is included in 'LibvirtLiveMigrateData' via the 'vifs' attribute, to transport this sentinel. This is a hack but is necessary to work around the lack of a free-form "capabilities" style dict that would allow us do backportable fixes to live migration features. Note that this change has the knock on effect of modifying the XML generated for OVS ports: when hybrid plug is false will now be of type 'ethernet' rather than 'bridge' as before. This explains the larger than expected test damage but should not affect users. [1] https://opendev.org/openstack/os-vif/src/tag/2.4.0/vif_plug_ovs/ovs.py#L90-L93 [2] https://en.wikipedia.org/wiki/IEEE_802.1Q#Frame_format [3] https://answers.launchpad.net/neutron/+question/231806 Change-Id: I11fb5d3ada7f27b39c183157ea73c8b72b4e672e Depends-On: Id12486b3127ab4ac8ad9ef2b3641da1b79a25a50 Closes-Bug: #1734320 Closes-Bug: #1815989
* Bumping min os-brick ver to 4.3.1Balazs Gibizer2021-03-291-8/+8
| | | | | | | | | | | | | | | | | | | | | | The os-brick 4.3.1 release fixes a critical data loss bug that can be triggered by reconfiguring [libvirt]/volume_use_multipath while volumes are attached. The following requirements and lower-requirements are also bumped as introduced into os-brick by Ie7dcc859e1291bd1d50b1ae516be38d8732de836: os-brick 4.3.1 depends on eventlet>=0.30.1 os-brick 4.3.1 depends on oslo.concurrency>=4.4.0 os-brick 4.3.1 depends on oslo.service>=2.5.0 os-brick 4.3.1 depends on oslo.serialization>=4.1.0 os-brick 4.3.1 depends on oslo.utils>=4.8.0 os-brick 4.3.1 depends on pbr>=5.5.1 os-brick 4.3.1 depends on requests>=2.25.1 os-brick 4.3.1 depends on tenacity>=6.3.1 Co-Authored-By: Lee Yarwood <lyarwood@redhat.com> Related-Bug: #1921381 Change-Id: I0d5df271dec1c6035229b02ec45e03abad6f27e7
* hyper-v rbd volume supportLucian Petrut2021-03-021-1/+1
| | | | | | | | | | | | | | | | | | | | Ceph 16 (Pacific) will support attaching RBD images to Windows hosts as well as Hyper-V VMs [1]. This patch updates the Hyper-V driver so that it may be able to consume RBD volumes. We're also updating the os-win requirement to 5.4.0. It should've been bumped by [2], vms won't spawn without it. Note this introduces no new or unmet direct or in-direct version dependencies and so is included as part of this change. [1] https://github.com/ceph/ceph/pull/33750 [2] Ibe6aff4edeb32208bc9865e9216a7432caddab2b Implements: blueprint hyperv-rbd Change-Id: I9ad90817648ca12f80a6b53f6ba728df15cbafab
* requirements.txt: Bump os-brick to 4.2.0Lee Yarwood2021-03-021-11/+11
| | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | This change simply bumps the version of os-brick required by Nova to version 4.2.0. This is itself required by I9ad90817648ca12f80a6b53f6ba728df15cbafab that introduces support for rbd volumes within the HyperV driver. After much back and fourth it was decided to bump the required version of os-brick ahead of that change to allow the following requirements.txt and lower-constraints.txt changes caused by direct and in-direct dependency changes to be documented clearly: os-brick 4.2.0 depends on oslo.log>=4.4.0 \_ oslo-log 4.4.0 depends on python-dateutil>=2.7.0 os-brick 4.2.0 depends on oslo.serialization>=4.0.1 os-brick 4.2.0 depends on pbr>=5.5.0 os-brick 4.2.0 depends on oslo.privsep>=2.4.0 \_ oslo.privsep 2.4.0 depends on msgpack>=0.6.0 os-brick 4.2.0 depends on oslo.service>=2.4.0 os-brick 4.2.0 depends on tenacity>=6.2.0 os-brick 4.2.0 depends on oslo.context>=3.1.1 os-brick 4.2.0 depends on oslo.concurrency>=4.3.0 os-brick 4.2.0 depends on oslo.i18n>=5.0.1 os-brick 4.2.0 depends on six>=1.15.0 os-brick 4.2.0 depends on os-win>=5.1.0 The above changes have been tested with pip 21.0.1 to ensure the new resolver is happy and that nothing has been missed. Change-Id: Ic83f3c7c955d0df89d75f700ee4fe2bd7f715794 Implements: blueprint hyperv-rbd
* scheduler: Add 'socket' PCI NUMA affinity policy traitArtom Lifshitz2021-02-241-1/+1
| | | | | | | | | | | | | Since only Wallaby compute nodes will support the 'socket' PCI NUMA affinity policy, this patch adds a ResourceRequest translator that adds a required trait if the value of '(hw_|hw:)pci_numa_affinity_policy' is 'socket'. The actual trait reporting by the libvirt driver will be added in a future patch. Until then the 'socket' value remains a hidden no-op. Implements: blueprint pci-socket-affinity Change-Id: I908ff07e1107304ca5926cc04d2fdc8fe0da5ed9
* Uncap PrettyTableStephen Finucane2021-02-111-1/+1
| | | | | | | | | This is now maintained as a Jazzband project [1]. [1] https://github.com/jazzband/prettytable Change-Id: Ie422a243a97ffbe2f553934004369f01562b95b9 Signed-off-by: Stephen Finucane <stephenfin@redhat.com>
* Reuse code from oslo lib for JSON policy migrationGhanshyam Mann2021-01-141-3/+3
| | | | | | | | | | | | | | | | | | | | | In Victoria cycle, we migrated the JSON formatted policy file to YAML - https://review.opendev.org/#/c/748059/ Which added the upgrade check and policy fallback logic to select the default JSON file if exist. In Wallaby cycle, this work is defined as community wide goal - https://governance.openstack.org/tc/goals/selected/wallaby/migrate-policy-format-from-json-to-yaml.html and common part of 1. upgrade check 2. policy fallback logic is moved from nova to oslo.upgradechecks and oslo.policy respectively. - oslo.upgradechecks(1.3.0): https://review.opendev.org/#/c/763484/ - oslo.policy(3.6.0): https://review.opendev.org/#/c/763261/ This commit make use these code form oslo lib. Change-Id: I1a8bc19b77abdcb6867eb61fe6ea1945142b32d2
* Merge "Remove six.text_type (2/2)"Zuul2020-12-221-1/+0
|\
| * Remove six.text_type (2/2)Takashi Natsume2020-12-131-1/+0
| | | | | | | | | | | | | | | | | | Replace six.text_type with str. This patch completes six removal. Change-Id: I779bd1446dc1f070fa5100ccccda7881fa508d79 Implements: blueprint six-removal Signed-off-by: Takashi Natsume <takanattie@gmail.com>
* | Merge "Bump the lowest eventlet version to 0.26.1"Zuul2020-12-211-1/+1
|\ \ | |/ |/|
| * Bump the lowest eventlet version to 0.26.1Balazs Gibizer2020-11-051-1/+1
| | | | | | | | | | | | | | | | | | | | | | | | The dnspython 2.0.0 incompatibility[1] is worked around in eventlet 0.26.1 by restricting the dnspython version to < 2.0.0. So the issue affects nova-novncproxy as well we need to bump our lower constraint as well. [1] https://github.com/eventlet/eventlet/issues/619 Related-Bug: #1888237 Change-Id: Ie9cc718e654cb37a4f31ccb4b052b23878d476a2
* | Replace md5 with oslo versionAde Lee2020-10-291-1/+1
|/ | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | md5 is not an approved algorithm in FIPS mode, and trying to instantiate a hashlib.md5() will fail when the system is running in FIPS mode. md5 is allowed when in a non-security context. There is a plan to add a keyword parameter (usedforsecurity) to hashlib.md5() to annotate whether or not the instance is being used in a security context. In the case where it is not, the instantiation of md5 will be allowed. See https://bugs.python.org/issue9216 for more details. Some downstream python versions already support this parameter. To support these versions, a new encapsulation of md5() has been added to oslo_utils. See https://review.opendev.org/#/c/750031/ This patch is to replace the instances of hashlib.md5() with this new encapsulation, adding an annotation indicating whether the usage is a security context or not. The instances being replaced here appear to be used to provide representations for paths. There is in fact already a sha256 version of get_hash_str that is supposed to be used in security sensitive usages. With this change (and the related dependent changes), the unit and functional tests pass when run on a FIPS enabled system. Change-Id: If0ec11e7b7fcde4dacc57265c4dd77b0f536bfab Depends-On: https://review.opendev.org/#/c/756432 Depends-On: https://review.opendev.org/#/c/756153 Depends-On: https://review.opendev.org/#/c/760160
* Migrate default policy file from JSON to YAMLGhanshyam Mann2020-09-091-5/+5
| | | | | | | | | | | | | | | | | | | | Default value of 'CONF.oslo_policy.policy_file' config option has been changed from 'policy.json' to 'policy.yaml'. If new default file 'policy.yaml' does not exist but old default 'policy.json' exist then fallback to use old default file. An upgrade checks is added to check the policy_file format and fail upgrade checks if it is JSON formatted. Added a warning in policy doc about JSON formatted file is deprecated, also removed all the reference to policy.json file in doc as well as in tests. Related Blueprint: policy-json-to-yaml Closes-Bug: #1875418 Change-Id: Ic4d3b998bb9701cb1e3ef12d9bb6f4d91cc19c18
* [goal] Prepare for job migration to Ubuntu Focal (20.04)Ghanshyam Mann2020-08-181-4/+4
| | | | | | | | | | | | | | | | | As per victoria cycle testing runtime and community goal[1] we need to migrate upstream CI/CD to Ubuntu Focal(20.04). Bump the lower constraints for required deps which added python3.8 support in their later version. Story: #2007865 Task: #40200 Closes-Bug: #1886298 [1] https://governance.openstack.org/tc/goals/selected/victoria/migrate-ci-cd-jobs-to-ubuntu-focal.html Change-Id: I6d79fc80b85d398fe0168677318c9c34285189ae
* Fix lower-constraints conflictsSean McGinnis2020-08-031-8/+8
| | | | | | | | | | Several version specified in our lower-constraints files had conflicting dependencies. This updates a few packages to avoid those conflicts. It also removes the linters that are tracked in the global requirements blocklist since we do not need to enforce lower-constraints for linters. Change-Id: Iae93f0631d77794f093fd330e849d2fd805b238f Signed-off-by: Sean McGinnis <sean.mcginnis@gmail.com>
* Provider Config File: YAML file loading and schema validationDustin Cowles2020-07-301-0/+1
| | | | | | | | | | | | | | | This series implements the referenced blueprint to allow for specifying custom resource provider traits and inventories via yaml config files. This first commit includes schema version 1.0 and functions to load and validate against that schema. Since this patch, package ddt>=1.2.1 is required to run tests. Co-Author: Tony Su <tao.su@intel.com> Author: Dustin Cowles <dustin.cowles@intel.com> Blueprint: provider-config-file Change-Id: I58099726f799c427e9174a0dcce9889344d51e7c
* Add traits for new AVX512 CPU featureLin Yang2020-07-061-1/+1
| | | | | | | | | | | | | | To support new AVX512 cpu feature, this patch adds the mapping between cpu features reported by libvirt [1] and corresponding os-traits [2]. The traits include 'AVX512VBMI', 'AVX512IFMA', 'AVX512VBMI2', 'AVX512BITALG', 'AVX512VAES', 'AVX512GFNI', 'AVX512VPCLMULQDQ' and 'AVX512VPOPCNTDQ'. [1] https://github.com/libvirt/libvirt/blob/master/src/cpu_map/x86_features.xml [2] https://review.opendev.org/#/c/728576/ Depends-On: I58cba02f204d2e19a1a838852c628694edd47d73 Change-Id: I212a84e5cae15bc133aafd538d55f85149ab360f
* Merge "Cap jsonschema 3.2.0 as the minimal version"Zuul2020-06-241-1/+1
|\
| * Cap jsonschema 3.2.0 as the minimal versionHervé Beraud2020-05-261-1/+1
| | | | | | | | | | | | | | | | | | | | | | | | Previous versions of jsonschema (<3.2.0) doesn't support python 3.8 [1]. Python 3.8 is part of the victoria supported runtimes [2] so we now force to use jsonschema version 3.2.0 to avoid issues, remove ambiguity and ensure that everything works with python 3 in general. [1] https://github.com/Julian/jsonschema/pull/627 [2] https://governance.openstack.org/tc/reference/runtimes/victoria.html#python-runtimes-for-victoria Change-Id: Ic8246b83563444501fe6d31712ea64d39e88140d
* | Remove eventlet hub workaround for monotonic clockMatthew Booth2020-05-221-1/+1
|/ | | | | | The fix landed in eventlet in 0.21.0 Change-Id: Icf7d671bc5d3f32831e6867c297e838f984d81b6
* Merge "Remove Babel requirement"Zuul2020-04-281-1/+0
|\
| * Remove Babel requirementAndreas Jaeger2020-04-171-1/+0
| | | | | | | | | | | | | | | | | | Babel is not needed as requirement, remove it. See also http://lists.openstack.org/pipermail/openstack-discuss/2020-April/014227.html Change-Id: I953b12bc3237c96ae640808949068ec4a4f85181
* | Merge "Use oslo policy flag to disable default change warning instead of all"Zuul2020-04-211-1/+1
|\ \ | |/ |/|
| * Use oslo policy flag to disable default change warning instead of allGhanshyam Mann2020-04-151-1/+1
| | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | oslo has new flag to disable the warning for default check_str change and keep logging warning if policy name is changed or it is marked for removal. Policy defaults refresh BP work changed the defaults for all the policy so logging their warning is dangerousa and fill up the log file. Once we switch to new defaults then we can enable them if needed. Logging warning for name change and marked for removal make sense when old rules are override by operator so the new flag does not control those. For policy defaults refresh BP work, we do not have many policies in this category so logging their warning is ok. This commits reset the testing flag 'suppress_deprecation_warnings' default value back to False. Test policy fixture sets that to True to avoid any warnig during tests run. Bumping the oslo policy version where this new flag is present - https://review.opendev.org/#/c/719547/ Partial implement blueprint policy-defaults-refresh Change-Id: Iaa6baf6877890babb6205bdb3ee2e1a2b28ebd9c
View Lorry Controller Status