Synchronise master with upstream#120
Open
github-actions[bot] wants to merge 46 commits into
Open
Conversation
As per 2025.1 testing runtime[1], we need to test on Ubuntu Noble (which will be taken care by depends-on tempest and devstack patches to move base jobs to Noble) and at least single job to run on Ubuntu Jammy (for smooth upgrade from previous releases). This commit adds a new job to run on Jammy which can be removed in future cycle when testing runtime test next version of Ubuntu as default. Depends-On: https://review.opendev.org/c/openstack/blazar-tempest-plugin/+/932947 [1] https://governance.openstack.org/tc/reference/runtimes/2025.1.html Change-Id: I539b02f54e1207e1e9a0109f50aa89ac15b74fa4
olso.policy 4.5.0[1] changed the config options policy_file default value to 'policy.yaml', which means it is changed for all the OpenStack services and they do not need to override the default anymore. NOTE: There is no change in behaviour here, oslo.policy provides the same configuration that services have overridden till now. [1] https://review.opendev.org/c/openstack/releases/+/934012 [2] https://review.opendev.org/c/openstack/requirements/+/934295 Change-Id: I4783f751c8ec775e862f378dc0b212a416198c38
Update the 2023.1 release notes configuration to build from unmaintained/2023.1. Change-Id: Ie1e38bc85f247ec2a97d391104bdfc852e067f23
The datetime.utcnow() is deprecated in Python 3.12. Replace datetime.utcnow() with oslo_utils.timeutils.utcnow(). Change-Id: I4d3382b142c1c9225cad29f9e33abf539ecf0f30 Signed-off-by: Takashi Natsume <takanattie@gmail.com>
Change-Id: Ia0ef7ba891bfbdbfcd2abb3c46df26f34899435f
This add new RBAC defaults in the blazar API policy. There is no change in the admin policy except they are scoped to the 'project'. Adding project reader role in the read APIs which continue to be allow by the member and admin role. Change-Id: I3246638e03ab7ddae366b4423b9397db7fe6051e
Previously, this was implemented using the shuffle method of the Random class without instantiating a Random object, which did not work. This changes swaps to the random.shuffle method, which works as expected. Closes-Bug: #2099927 Change-Id: Ib288091af9cc035ccb0535fbc1748c17bb3cb1e9
Add file to the reno documentation build to show release notes for stable/2025.1. Use pbr instruction to increment the minor version number automatically so that master versions are higher than the versions on stable/2025.1. Sem-Ver: feature Change-Id: Ie566be732d06d70c7732290f55e4e28c1ba27a48
These files are not actually executable. Change-Id: Ia11e696ffa804172cb4b6814f1813f3ad0ee1a00
Currently, tests are using 2026 as date in the future. Unfortunately, if we set the date of the machine running the tests in let's say 2027, then tests are failing, as per Debian report here: https://bugs.debian.org/1104885 This patch fixes this by using 2046 instead of 2026 in the tests. Closes-Bug: #2110472 Change-Id: I190daa89d134a4440dd914a9a935000aaa87d4f2
Changes in python packaging tooling mean that the wsgi_scripts functionality via PBR may not longer function. This patch switches blazar from using the PBR wsgi_scripts method to using a new wsgi module that provides the same behavior as the generated wsgi scripts provided. A related devstack patch enables devstack to setup uWSGI to use the new module path instead of the generated wsgi scripts. For more details see the proposed OpenStack goal [1]. [1] https://review.opendev.org/c/openstack/governance/+/902807 Change-Id: Ib16d5d1ea5d7416d7b1f026f771d6c2b77657970
Some syntax errors in JSON make it unparsable for tools like `jq` Change-Id: Idd3ba27933868a3eaa53f9ce8c8db94a49558e74
Python 3.9 is no longer part of the tested runtimes [1]. Python 3.8 testing was removed in the 2024.2 release [2]. Add Python 3.12 to classifiers. [1] https://governance.openstack.org/tc/reference/runtimes/2025.2.html [2] https://governance.openstack.org/tc/reference/runtimes/2024.2.html Change-Id: I5a62b7b6ffdefafa1966a74faa2725ff88fdec3a
Jammy testing is not needed in 2025.2 release. Change-Id: I5f6de2316e42685a4f80aed990327ade61ccb50a
sqlalchemy.ext.declarative was deprecated in sqlalchemy 1.4.0, due to the built-in implementations[1]. [1] sqlalchemy/sqlalchemy@450f5c0d6519a439f40 Change-Id: I2bc3a39313e2534ca0a5638e08fcac736bac66ed
Previously, target was always None, and so ownership check essentially compared the current context against itself. Under this implementation, if the target is None, we look up the relevant object based on kwargs, and then use this object as the target. At the moment "lease" is the only type of object that has ownership, and so it is the only case. Co-Authored-By: Mark Powers <markpowers@uchicago.edu> Closes-Bug: #2120655 Change-Id: I4bb85d650f4d7f3534206f1c4690cef8eca0a4c2 Signed-off-by: Matt Crees <mattc@stackhpc.com>
As is described, ZeroMQ support by oslo.messaging was removed during Stein cycle. Change-Id: I871426ef37db699e79a211ffdc91bb366a394918 Signed-off-by: Takashi Kajinami <kajinamit@oss.nttdata.com>
Add file to the reno documentation build to show release notes for stable/2025.2. Use pbr instruction to increment the minor version number automatically so that master versions are higher than the versions on stable/2025.2. Sem-Ver: feature Change-Id: I382b5a722b9fe141584fad7ee0d12caa236cf326 Signed-off-by: OpenStack Release Bot <infra-root@openstack.org> Generated-By: openstack/project-config:roles/copy-release-tools-scripts/files/release-tools/add_release_note_page.sh
The tags framework has been discontinued for a long time. https://governance.openstack.org/tc/reference/tags/ https://governance.openstack.org/tc/resolutions/20211224-tags-framework-removal.html Change-Id: I8f7940030afede4391b614f7c242bc3ccfb7daf0 Signed-off-by: Ivan Anfimov <lazekteam@gmail.com>
Python 2 reached its EOL long time ago and we no longer expect any user may attempt to run tox in Python 2. Removing the option allows us to remove ignore_basepython_conflict. Change-Id: Ifb7db1e4c5dc928346ce0704951d9fb538f9a679 Co-authored-by: Takashi Kajinami <kajinamit@oss.nttdata.com> Signed-off-by: Ivan Anfimov <lazekteam@gmail.com>
Update the 2024.1 release notes configuration to build from unmaintained/2024.1. Change-Id: I1cde60ec473743089f8e13fa41c36bc0f9c5ab5b Signed-off-by: OpenStack Release Bot <infra-root@openstack.org> Generated-By: openstack/project-config:roles/copy-release-tools-scripts/files/release-tools/change_reno_branch_to_unmaintained.sh
…tire lease data. Change-Id: I6b6b971fc5df9721f474020965abdf7d34d6e913 Signed-off-by: nitin-29-gupta <nitin291989@gmail.com>
pylint is no longer in use and can be removed. Change-Id: I118c61cf56a9761f0afb3ed26905237b5d4a0152 Co-authored-by: Takashi Kajinami <kajinamit@oss.nttdata.com> Signed-off-by: Ivan Anfimov <lazekteam@gmail.com>
Since 'resource_properties' was added, 'amount' is no longer the last item in the updatable list, so updating the amount would be denied. Correct this by instead explicitly checking for 'amount'. Closes-Bug: #2138386 Change-Id: Idd3ee49f173a62392eb5aec7ea664921a36d5068 Signed-off-by: Matt Crees <mattc@stackhpc.com>
Change-Id: I2f98ffe2cfbfb20c1c26be37bf54705b6666d01f Signed-off-by: Matt Crees <mattc@stackhpc.com>
Recent versions of pip no longer requires that the requirements are listed in specific orders and can resolve dependencies automatically. Change-Id: Icb4310abaf3bf85777d1e4ea2a885f22b684496b Signed-off-by: Takashi Kajinami <kajinamit@oss.nttdata.com>
Change-Id: Ic81e7c0601d62f7bec7d32d3e68227539aa417b1 Signed-off-by: Ivan Anfimov <lazekteam@gmail.com>
Previously, traits could not be included with a flavor reservation. This commit implements checking flavor traits when querying available hosts. This check is done via the placement API to get resource providers based on a trait query only when traits are specified on the flavor. Co-Authored-By: Michael Sherman <shermanm@uchicago.edu> Change-Id: I5905d97d85955113d07b418cbe65fbafe132cd4b Signed-off-by: Mark Powers <markpowers@uchicago.edu>
This file isn't needed as far as we use pbr. Trivial-Fix Change-Id: Ifaf86dd72193d2fa41acaab918a78bf3ba3b802e Signed-off-by: Takashi Kajinami <kajinamit@oss.nttdata.com>
Makes it clear to the user that this feature is not yet supported. Change-Id: I26c1af3f02a0afc98329b0f9840a2d7b56d7ea90 Signed-off-by: Matt Crees <mattc@stackhpc.com>
Add file to the reno documentation build to show release notes for stable/2026.1. Use pbr instruction to increment the minor version number automatically so that master versions are higher than the versions on stable/2026.1. Sem-Ver: feature Change-Id: I9a28f797f062b9c626d852600662fdc19ee2b24e Signed-off-by: OpenStack Release Bot <infra-root@openstack.org> Generated-By: openstack/project-config:roles/copy-release-tools-scripts/files/release-tools/add_release_note_page.sh
github-actions
Bot
added
automated
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
12 participants
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
This PR contains a snapshot of master from upstream master.