* Update openstack-helm from branch 'master'
to 3013cbc94a201b48bf5b3e0bced9297ae924a133
- Merge "Align horizon chart with 2024.1"
- Align horizon chart with 2024.1
- Update pymysql version info. Horizon requiers newer
mysql client version than we had previously
- Update scripts to use sysconfig.get_path
instead of distutils.sysconfig.get_python_lib which
is deprecated
Story: 2011130
Depends-On: Ibd278f64b49c445dbbf774240a38c6c5ef3a4548
Change-Id: Ic763b72268042bda029c373d2b54c4c309fc70d2
* Update openstack-ansible-os_magnum from branch 'master'
to e8e16b93013dccceab57d1b60acde3b70505d518
- Merge "Implement variables to address oslo.messaging improvements"
- Implement variables to address oslo.messaging improvements
During last release cycle oslo.messaging has landed [1] series of extremely
useful changes that are designed to implement modern messaging
techniques for rabbitmq quorum queues.
Since these changes are breaking and require queues being re-created,
it makes total sense to align these with migration to quorum queues by default.
[1] https://review.opendev.org/q/topic:%22bug-2031497%22
Change-Id: I5dbb9a359872dbcff133b0003ab769df239d0e64
* Update cloudkitty-dashboard from branch 'master'
to e7bf46d8a47041be6bc7daa50ba42efab7936db8
- Imported Translations from Zanata
For more information about this automatic import see:
https://docs.openstack.org/i18n/latest/reviewing-translation-import.html
Change-Id: I14c2e4dab37c38c504185818ab6f05619d7fcc0a
* Update openstack-ansible-os_cloudkitty from branch 'master'
to 3ef1a0127d8873054cf0d621af9bbd92b5af010c
- Add tag to enable targeting of post-install config elements only
<service>-config tags are quite broad and have a long execution
time. Where you only need to modify a service's '.conf' file and
similar it is useful to have a quicker method to do so.
Depends-On: https://review.opendev.org/c/openstack/openstack-ansible/+/920058
Change-Id: Iae6fb286658fc924796a29fb08979cfe9113283b
* Update openstack-ansible from branch 'master'
to 55173855be84a0f59ba6e3aa3e3748daed60146a
- Merge "Add cloudkitty-dashboard to zuul required-projects"
- Add cloudkitty-dashboard to zuul required-projects
We now deploy horizon with metal jobs so the dashboards must be
available in CI jobs.
Change-Id: I5d7cb016160352ce12bb1203beeae441d185c573
* Update openstack-helm-images from branch 'master'
to a81fd5bf5c3711f29b38e0294cf9e75163912ba4
- Merge "[nagios] Build Jammy-based image"
- [nagios] Build Jammy-based image
+ unify Dockerfiles for different Ubuntu versions
+ switch plugins to use Python 3, as it is the only supported version starting from Ubuntu Focal
Change-Id: I0e66ed0c96ed72c8202940e8a97db17d932a5e47
* Update puppet-openstack-integration from branch 'master'
to 2f4576bf7d563a1bb024047bd72b49ae9e1e6c09
- Merge "Horizon: Enable c-bak panel"
- Horizon: Enable c-bak panel
... when cinder-backup is enabled.
The service is not automatically discovered and the availability should
be declared by the OPENSTACK_CINDER_FEATURES option.
Change-Id: Ieba9b30b6ef32b021a1d04a616b836d2a480f9a1
* Update neutron from branch 'master'
to 06c1972a4866c81d8dbb6131c8ea747588855e01
- Merge "Return both project_id when validating auto allocate network"
- Return both project_id when validating auto allocate network
When neutron API is called to check requirements for the auto_allocate
topology, it needs to return not only 'tenant_id' field but also
'project_id' as that is required for the policy enforcement.
Without this 'project_id' field requirements check was failing for
member and reader users as they got 404 from the Neutron API. And the
reason why Neutron was returning 404 was that it wasn't passing policy
enforcement due to missing project_id field in the 'target' object.
Closes-bug: #2066369
Change-Id: Idf96a82bc6c8cb0b47dfde3baba94b42a8a8beba
* Update openstack-helm from branch 'master'
to 510ee6c0dff1ac275c963ca22007c24250db6c57
- ironic: make conductor statefulset more configurable
Made the conductor statefulset more configurable by allowing the user to
enable/disable the http or pxe containers and to modify their init
and/or runtime scripts. Allow another OS to potentially be used by
letting the user supply the HOST_OS value and FILEPATH. Simplify the code
by using the variables already defined. Include the snponly image as the
counterpart to undionly.
Change-Id: I181657bca6ace0f94f6e0ef0b6f8a5bc7a433ac3
* Update manila from branch 'master'
to ebdccfab588971439009f0c0d557538233a1a81c
- Merge "Enable Bandit testing in Manila"
- Enable Bandit testing in Manila
Adds a Bandit testing environment to the tox.ini file and
adds a job to project.yaml Zuul CI file to run the Bandit
test environment. Also includes a nosec comment to ignore
a hardbinding to 0.0.0.0 in service.py
Depends-On: I78a5b708cd970dcb60f480d8e6a201d0768645fc
Depends-On: I27d1204ec7dafd3b578d1261c3fd2e371ae405fb
Depends-On: I2a913f3b87e16554b1bd68543fcf254cc4226031
Depends-On: I46ad1a7ca723157488525ca7239cbd0ef421b975
Depends-On: Ib5404d9e165be5879f5351c3f0952648ae702b2d
Depends-On: Id71c0ee4138b695ff19085a284ccced6b1a9dbba
Depends-On: I33bbb7070ada5509ca05c90d7a38077d38f54a1f
Depends-On: I3e974a2113b29af1111f27ca1afeb78091a0ec75
Depends-On: I0e686c91ce02ea42719d00d17f6ed659e97470ac
Depends-On: I171c90a281c7b62c2601131293f9f00a926641e2
Change-Id: I8eb93cdcd5d47a6a5495ee7277c72d5f028cb412
* Update manila from branch 'master'
to 4109b81f21692bb70ac93d12090d446b7bdd7141
- Merge "Applies nosec in Dell EMC eNAS"
- Applies nosec in Dell EMC eNAS
Bandit raises a flag at evals, suggests using
literal_eval which does not work here.
Instead of using eval to parse the attributes,
should use getattr method instead.
When using getattr, unit tests fail
because of problems with mocking requests.
Applying nosec and reported a bug.
Related-Bug: 2065727
Change-Id: Ib5404d9e165be5879f5351c3f0952648ae702b2d
* Update manila from branch 'master'
to dbfb40c9f17261dfa382608723d69a5468a1e7a8
- Merge "Fixes for Bandit Issues in Nexenta Drivers"
- Fixes for Bandit Issues in Nexenta Drivers
Adds a timeout to a post so Bandit
stops crying. Adds a nosec comment to
an MD5 hash because I can't tell if it's
used for security or not.
Change-Id: I46ad1a7ca723157488525ca7239cbd0ef421b975
* Update swift from branch 'master'
to f3adce13753f9b32be60a68b49c79321cb552a61
- expirer: bad config should not loop forever
Change-Id: I9413c72f41465fb8026848f71ec3b39fa990c3b7
* Update swift from branch 'master'
to a2df74ffe267565b7bb4af875141b73668388c39
- tests: new test_config module for utils.config
Drive-by: fix ValueError message for non_negative_int
Change-Id: I06508279d59fa57296dd85548f271a7812aeb45f
* Update requirements from branch 'master'
to 9ce3c2c195e7a7f2b069252e29fbcaf8463dea94
- Merge "Remove ansible-runner"
- Remove ansible-runner
ansible-runner was added to be used by networking-ansible[1]. However
the project hasn't get any update for 3 years and looks unmaintained.
[1] a449abac5d3336db765006d8cc6829fd4785dccb
Remove ansible-runner from global-requirements to avoid maintaining
dependencies for unmaintained projects. This allows us to get rid of
lockfile which was already retired[2].
[2] 45d30134d218f661346326da7fa0f19cb3de97f9
Change-Id: I1304f2dfcd6c9b0ab3a3ec54f50238705179d1f5
* Update nova from branch 'master'
to bded279a00122ce65839da8836d21b8130ab5475
- Merge "docs: Add more information about unified limits"
- docs: Add more information about unified limits
The admin docs are missing some details about enabling unified limits,
like oslo.limit configuration and Keystone roles. This adds more
information about what roles are needed for what actions, how to set
quota limits, quota enforcement, and unified limits in general.
This also removes a couple of tables from the user docs that show
obsolete/deprecated quota limits because they may be more confusing
than helpful considering we don't want new deployments to use them and
they add more clutter to the page.
More info is also added regarding the CLI commands for unified limits
and makes it consistent between the user and admin docs.
Change-Id: Id93f9997d1b217e0c2151c88323564f7a7fefc02
* Update cinder from branch 'master'
to bb6add385b08760d1343d67de0657d3f13e3136c
- Merge "Remove six from netapp drivers"
- Remove six from netapp drivers
Change-Id: I372aa42b868ebf356948737d714a3e1bea3185ba
* Update ironic from branch 'master'
to df6342d1ab2dfaeff84733896ecee40c1b1225e4
- Merge "Fix negative lookahead assertion syntax error"
- Fix negative lookahead assertion syntax error
Python regexes are deprecated in Zuul, so this commit updates the
configuration to use RE2-compatible syntax.
Change-Id: If4973be103076f5a3879dc630e104d129377f7da
* Update nova from branch 'master'
to d7d2fb1edddf83d69c31c5cfa76f76e913a240a4
- Merge "scheduler: AggregateMultitenancyIsolation to support unlimited tenant"
- scheduler: AggregateMultitenancyIsolation to support unlimited tenant
This commit removes the previous limitation on the number of tenants
that can be filtered using the `filter_tenant_id` aggregate property
in the AggregateMultitenancyIsolation scheduler filter.
The `filter_tenant_id` can now be used as a suffix, allowing for an
unlimited number of tenant ID properties to be set on the
aggregate. This update maintains backward compatibility.
Implements: blueprint aggregatemultitenancyisolation-to-support-unlimited-tenant
Signed-off-by: Sahid Orentino Ferdjaoui <sahid.ferdjaoui@industrialdiscipline.com>
Change-Id: Ic87d142647774b62a6af2cc5eb7a3cd66f9afeb7
* Update cinder from branch 'master'
to 05ec5904457ed57067ea4d4cebaa67dafa910626
- Imported Translations from Zanata
For more information about this automatic import see:
https://docs.openstack.org/i18n/latest/reviewing-translation-import.html
Change-Id: I0fff1a1f232f4ad14c83061d85fc626db58e0ff2
* Update barbican-tempest-plugin from branch 'master'
to d7f96744c352e16301832751ae4af14818c4ec5c
- Add stable/2024.1 jobs on master gate
As 2024.1 is released, we should add its job on master
gate to keep branchless tempest plugins compatible to stable branch.
Ref: Tempest plugins guide for stable branch testing:
- https://docs.openstack.org/tempest/latest/stable_branch_testing_policy.html
Change-Id: I16163f77b25c1ba00822a4fd2ab00b9d26870de9
* Update openstack-ansible from branch 'master'
to 774764e52f483dbec2b136d4e6679e46d506478c
- Merge "[doc] Add information about hook playbooks to the 'extending-osa' docs"
- [doc] Add information about hook playbooks to the 'extending-osa' docs
Change-Id: I131920a1622d8ba36362f6ccc95dc705baca8a16
* Update releases from branch 'master'
to 90a7d437a2dfd18fd9031665991d8eb794901a74
- Merge "Create new keystone-tempest-plugin release"
- Create new keystone-tempest-plugin release
This release pulls in the latest SRBAC related testing changes.
Change-Id: I1905eec71e6d7050f1cbf2bd81f8c6f80d051629
* Update releases from branch 'master'
to 7d7502001b3b924333066464ec186a2c9f2c9a9d
- Merge "[tempest] Tag zed-last"
- [tempest] Tag zed-last
Yoga branch is moving to unmaintained state now[1]. Tempest and
tempest plugins are branchless which means master version of
Tempest and its plugins is used to test the supported stable
branches.
Once any stable branch is moved to unmaintained state then,
Tempest and its plugins compatible tag[2] needs to be
released so that we can keep testing the unmaintained stable branches
with that tag once master Tempest and its plugins are not compatible[3].
Tagging 'zed-last' with the same hash of new tag 39.0.0 which mark
the end of support for stable/zed in Tempest.
[1] https://review.opendev.org/q/topic:%22zed-unmaintained%22
[2] https://docs.openstack.org/tempest/latest/stable_branch_support_policy.html
[3] https://docs.openstack.org/tempest/latest/tempest_and_plugins_compatible_version_policy.html
Change-Id: I8a748123627d9fea17ec1669f1f7ec5353572a2b
* Update releases from branch 'master'
to c532f1cb71825a0865a1e6cf191cfc961cb14f22
- Merge "Release oslo.messaging for Dalmatian-1 milestone"
- Release oslo.messaging for Dalmatian-1 milestone
This is a library release for oslo.messaging for the Dalmatian-1
milestone. This repository contains commits that have not been releases
for this cycle yet.
If the team is ready to process with this release, please leave a +1
to indicate we should go ahead with the release.
If the team needs more time for things about to merge, or if there is
some other reason a release should not be done at this time, please
leave a -1 with a comment indicating the status. Then update the patch
with the new commit hash to use once the team is ready to do the
release.
Change-Id: I7940a8cbc7308fe793eeda5c0d6cb4639ad0bce8
Signed-off-by: Elod Illes <elod.illes@est.tech>