* Update puppet-oslo from branch 'master'
to ebabe95157ecafe98fccaab4139214615fe08949
- Merge "Remove support for amqp1 messaging driver"
- Remove support for amqp1 messaging driver
It was deprecated during the 2023.2 cycle[1], so can be removed now.
Also add validation about transport_url options to reject unsupported
drivers.
[1] e174113210699b433dbae4c2c5a68bc3d269b5c3
Depends-on: https://review.opendev.org/918774
Change-Id: I3c3b17b8109c84cc0cbfb4254cc969cc563265e4
* Update puppet-openstack-integration from branch 'master'
to dc443f90e9fe4c17ddb8aa4c3caa37b311d97af5
- Merge "swift: Use different log name per daemon"
- swift: Use different log name per daemon
... so that we can identify which daemon emits a specific log line.
Depends-on: https://review.opendev.org/919498
Change-Id: I82c82e2753f98555a2876b998418ca8c9eb91c74
* Update openstack-ansible-os_octavia from branch 'master'
to 77478dfd99e1fc302aa353c3a358f3c893a0eff6
- 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: I88e1fd869fa0e1e13184d17d5fa16364f87d14bd
* Update python-magnumclient from branch 'master'
to 65e0403dc5881c0d0f727fe4a0c4b98bddb765f8
- Merge "Add insecure_registry to osc part of the client"
- Add insecure_registry to osc part of the client
insecure_registry argument is not present for the template creation
command of osc, while it's present in deprecated client for years.
Change-Id: I613a772801abd32031c52627c51fff20f4701ab8
* Update devstack-plugin-ceph from branch 'master'
to 13f94aaaf2b4a59581b1be5979600ca18a8df5c3
- Merge "Add service secret to libvirt when cinder enabled"
- Add service secret to libvirt when cinder enabled
The current code only adds the service secret to libvirt when Ceph has
been enabled in Nova, but it should also be enabled if it has only been
enabled in Cinder.
This patch changes devstack/plugin.sh to write the service secret to
libvirt whenever Nova or Cinder is using Ceph.
This would be the counterpart of the code we already have in
_undefine_virsh_secret where we are already checking if it's enabled in
either of the services to remove the secret.
Change-Id: I1067d52b7a435fcef7996eea6479d598be842dca
* Update cinder from branch 'master'
to 6e71a67f4da86bf95ca118eeb26ad75de2a19c1f
- Merge "StorPool: drop _attach_volume() and _detach_volume()"
- StorPool: drop _attach_volume() and _detach_volume()
Our os-brick connector already handles the "keep track of which volume
is attached for what reason" calls to storpool.spopenstack. However,
we need to explicitly specify the access mode in initialize_connection()
now, since our os-brick connector does not know how to divine it yet.
(this will come later with the "attach snapshot" functionality)
Incidentally, this fixes the "create an encrypted volume" flow, since
our _attach_volume() implementation never actually returned a connector
in the attachment info...
Change-Id: I5da7ae04b87b4fd52a682a6545060e852174f6c8
Closes-Bug: #1939241
* Update openstack-ansible-os_octavia from branch 'master'
to 053b2f8f5b4572f29f28a3f5a7af0725cfe464b7
- Add variable to globally control notifications enablement
In order to be able to globally enable notification reporting for all services,
without an need to have ceilometer deployed or bunch of overrides for each
service, we add `oslomsg_notify_enabled` variable that aims to control
behaviour of enabled notifications.
Presence of ceilometer is still respected by default and being referenced.
Potential usecase are various billing panels that do rely on notifications
but do not require presence of Ceilometer.
Change-Id: Id9bc7f2ba4a2e813657d65f2bb6be5089c1a5461
* Update ironic from branch 'master'
to dcace881bc36cb9a2af851ea6b055cc9ce3dd433
- Merge "docs: revise notes around iso booting for clarity"
- docs: revise notes around iso booting for clarity
Had someone try to boot the tinycore ISO on a UEFI machine, and they
got a nice error. Just turns out we needed to update our docs a little
bit to provide appropriate clarity.
Change-Id: I1adfb62ea22d0b58740ceadc8c338fc04d9b78de
* Update puppet-swift from branch 'master'
to f07105ad248be0e46f497d82506fac28c7191e36
- Expose log_name_per_daemon configurable
Add the log_name_per_daemon parameter to the all class so that this
parameter can be customized via the simplified definition.
Change-Id: I34989778f607db869d7acd1787682f5a8c97be5b
* Update puppet-openstack-integration from branch 'master'
to 0a9c65cbe1f7aa9507bc8accc50b249b9782d2e8
- redis: Generate tls certs timely for redis-sentinel
The same certs are used by not only redis but also redis-sentinel so
the certs should be generated at the appropriate timing for sentinel
installation/configuration.
Change-Id: I50e08ff61d3e4152777b425fe15f2f48fcea6070
* Update puppet-aodh from branch 'master'
to 6cdb315944cd225ee926efb2a8e41eda510e71aa
- Merge "Add validations for keystone resource parameters"
- Add validations for keystone resource parameters
The underlying implementation already have type validations. Inherit
these and make a few adjustment so that validation failures are raised
from the external interface layer instead of the internal interface.
Change-Id: Iefbdb1483986ad734ebce03d96c762eba4639067
* Update swift from branch 'master'
to d1aa735a37d9d679c51a9eda6131ec3e365976b8
- Merge "backend ratelimit: support per-method rate limits"
- backend ratelimit: support per-method rate limits
Add support for config options such as:
head_requests_per_device_per_second = 100
Change-Id: I2936f799b6112155ff01dcd8e1f985849a1af178
* Update puppet-vitrage from branch 'master'
to 7778cc3b316f828feab2ec84b5ed2b2ff3c81ea5
- Merge "Remove support for amqp1 messaging driver"
- Remove support for amqp1 messaging driver
The base implementation in puppet-oslo was deprecated during the 2023.2
cycle[1], so can be removed now.
[1] e174113210699b433dbae4c2c5a68bc3d269b5c3
Change-Id: Ib0104a11066f2047e3095ac8cbee571c531c9a67
* Update bifrost from branch 'master'
to 38ac4344f1538a212e9fd11c7de690dbb7da3588
- Merge "Remove last traces of ubuntu focal"
- Remove last traces of ubuntu focal
The CI jobs are no longer used by anything, and bifrost does not support
focal either already.
Change-Id: I1093e87048b5cab51add180b90be836628a15731
* Update puppet-oslo from branch 'master'
to 352c9b8207311697b2227ab6ba8bb1004a782835
- Merge "Improve unit test coverage"
- Improve unit test coverage
Validate a few resources which are not covered, to improve test
coverage.
Change-Id: Ie165830609ee5b91fcad324a2b030223c566831e
* Update manila-tempest-plugin from branch 'master'
to 4940aecb96ea43a15a1d953cac9d46f32a82fa6f
- Merge "Add stable/2024.1 job on gate and remove zed job"
- Add stable/2024.1 job on gate and remove zed job
As 2024.1 is released, we should add its job on master
gate to keep branchless tempest plugins compatible to
stable branch.
At the same time, we're dropping the zed job
since the zed branch of openstack/manila has now
transitioned to "unmaintained". manila-tempest-plugin
may no longer support running against the zed branch.
Please use the "zed-last" tag instead [1]
Ref: Tempest plugins guide for stable branch testing:
- https://docs.openstack.org/tempest/latest/stable_branch_testing_policy.html
[1] https://review.opendev.org/c/openstack/releases/+/918346
Change-Id: I0625576d14d9e084aa65beed5d0c988dcebd85dc
Signed-off-by: Goutham Pacha Ravi <gouthampravi@gmail.com>
* Update puppet-heat from branch 'master'
to abbb1a7b41a86501b9060c8801d9a9f86ee1f51a
- Add missing test coverage for [DEFAULT] options
Change-Id: Icb6676ce62c800d60305a11045489da24970c9ce
* Update openstack-ansible-os_murano from branch 'master'
to 5f59188e4646897659cb36c06c017dc9c9959d5f
- Merge "Preserve actual production playbook in examples"
- Preserve actual production playbook in examples
Since Murano is moved to inactive state, we can not provide further
releases of the role either, which means that Sahara should be dropped
from the integrated repo.
With that it's worth to preserve actuall playbook that was used for
deployment as example playbook, in case somebody needs to use old
role/service version in their deployments.
Change-Id: Iffcf7e865591ef76f62053f3ec3d022a90cfb331
* Update openstack-ansible-os_murano from branch 'master'
to 39aeb27b7fe347ec64fcf5f5c0ec6130438dfd42
- reno: Update master for unmaintained/zed
Update the zed release notes configuration to build from
unmaintained/zed.
Change-Id: I51173e3f0aac7894e903465e515a7e3aca6cf6b8
* Update kolla-ansible from branch 'master'
to cff75f6eacf2723877cfd8e32993bfec9acd42d2
- Merge "ironic: mount metrics in conductor only when exporter is enabled"
- ironic: mount metrics in conductor only when exporter is enabled
Related-Bug: #2062401
Change-Id: I2c058e0fe56b32fce36e1c9f637c12fe5950ff21
* Update openstacksdk from branch 'master'
to 0d5d48f65f3eae30f940504d319ea3515608a238
- Merge "Add support for federation service providers"
- Add support for federation service providers
Change-Id: I0c4c1ee77b0bbccd18af5b9b84a585a79f1a500c
* Update openstack-ansible-os_cinder from branch 'master'
to 62f3ce0efc7cbde90e192dff2199f5c1f21787ae
- 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: I02db2ad91ad036ff24c35882e1746b3d6a8f3cc0
* Update devstack from branch 'master'
to c80b9f4fc16997631696100a8e468d907a177f7d
- Drop reno
devstack doesn't do releases, so there should be no release notes,
either. Drop the one that was accidentally created to avoid confusion.
Change-Id: I75a295e50c36925a0137a5458444fb48bd5d9f8a
* Update cloudkitty from branch 'master'
to 8a5319fd5de3f9f9c7b543936a3bb42fb02a62a8
- Merge "CI: Remove grenade branch variables"
- CI: Remove grenade branch variables
This was always testing the upgrade with master, causing CI failures on
the stable/2024.1 branch.
Also remove USE_PYTHON3 which is always true in our supported branches.
Change-Id: I9ba2b02b7c5abd2b6a2114cd3b680ea0244484a4
* Update neutron from branch 'master'
to 35daa2d8684888798b974487d1f7468dc1ca1e9e
- Merge "Optimize deletion of static routes"
- Optimize deletion of static routes
Instead of having a separate OVN command for deletion of each
static route, send out the deletion as a single command.
Which significantly improves the performance. Previously
deletion of 1000 routes took >1m30s and >6m30s for 2000 routes,
with this change it takes ~5s and ~8s, respectivily.
Closes-Bug: #2060054
Change-Id: Iaa5204e2e48795c31c502160041bd128189eef5a
* Update openstack-ansible-ceph_client from branch 'master'
to 33f8ad519f64d28f410e856aa129060e3a80f27c
- Merge "reno: Update master for unmaintained/zed"
- reno: Update master for unmaintained/zed
Update the zed release notes configuration to build from
unmaintained/zed.
Change-Id: I74308ab07e06c6f81830076feb7a7446932f25a3
* Update cloudkitty from branch 'master'
to f3a3a78ca4c6f0fdcc52d92b4526c682adf36a20
- Merge "Add rating modules PUT endpoint to v2 API"
- Add rating modules PUT endpoint to v2 API
This introduces the PUT method for rating modules in the v2 API. Work items:
* Implement the "/v1/rating/modules" endpoints in the v2 API, including
unit tests and documentation
Change-Id: I202c1021c11926c40ac1d9f5ca51c026ec3b674b
Co-Authored-By: Pedro Henrique Pereira Martins <phpm13@gmail.com>
Story: 2006572
Task: 36798
* Update openstack-ansible-ceph_client from branch 'master'
to 79074ab18b53e2220f22ae96d16580fb573fe952
- Switch default ceph version to reef
Depends-On: https://review.opendev.org/c/openstack/openstack-ansible/+/917014
Change-Id: I0e9f9a4559dd18cfd1bd431b3035c2f1f411d46d
* Update openstack-ansible-os_neutron from branch 'master'
to d0917f561cc7c80143c831e83af36b15e64c36fd
- 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: I6f1131cb9c8f15d7d9367397ff8ca1b439d66ab0
* Update horizon from branch 'master'
to 47823cce7c9b832b1f23eeb754e6ad4b9f212722
- Remove deprecated exceptions.check_message
It was deprecated 5 years ago[1] and has been kept for enough long
time.
[1] 31f7fc6bb24995376bb74d7de6866f5bf2b322c8
Change-Id: Ie80b418c3eee3212006124be1eb4ee9f831f3d1d
* Update openstack-ansible-os_neutron from branch 'master'
to 32db8f9d85f145bc003bb756f5c008c5ee74ea53
- Add variable to globally control notifications enablement
In order to be able to globally enable notification reporting for all services,
without an need to have ceilometer deployed or bunch of overrides for each
service, we add `oslomsg_notify_enabled` variable that aims to control
behaviour of enabled notifications.
Presence of ceilometer is still respected by default and being referenced.
Potential usecase are various billing panels that do rely on notifications
but do not require presence of Ceilometer.
Change-Id: Idd3bb9a0ab58307b6acced6dd60fce3adf17b138
* Update openstack-ansible-os_neutron from branch 'master'
to 5525538be1a8240fc28c0a09b8cd2be4704ecdf4
- Add service policies defenition
In order to allow definition of policies per service, we need to add variables
to service roles, that will be passed to openstack.osa.mq_setup.
Currently this can be handled by leveraging group_vars and overriding `oslomsg_rpc_policies` as a whole, but it's not obvious and
can be non-trivial for some groups which are co-locating multiple services
or in case of metal deployments.
Change-Id: If239bee6267b983cf335c37ce9fb26bd352a3921
* Update openstack-ansible-os_keystone from branch 'master'
to 98e41b6eee98f0a3b7965f83a911604e67ef9415
- Add qos_prefetch_count to variables
When rabbit_stream_fanout is set to true, rabbit_qos_prefetch_count
should be set to a positive value.
This also fixes defenition of transient_quorum_queue as if
rabbit_stream_fanout is enabled - transient_quorum_queue should be also
enabled. [1]
[1] https://github.com/openstack/oslo.messaging/blob/master/oslo_messaging/_drivers/impl_rabbit.py#L726-L736
Change-Id: I8ea72890948ef1c4516c6272c3b19e81693e611a
* Update openstack-ansible-os_octavia from branch 'master'
to e85299f41320434712ba626df6f50d6ef99cda1e
- Add service policies defenition
In order to allow definition of policies per service, we need to add variables
to service roles, that will be passed to openstack.osa.mq_setup.
Currently this can be handled by leveraging group_vars and overriding `oslomsg_rpc_policies` as a whole, but it's not obvious and
can be non-trivial for some groups which are co-locating multiple services
or in case of metal deployments.
Change-Id: I594514580ca7180089699914805a595c2feb965b
* Update openstack-ansible-os_nova from branch 'master'
to 6a592e88d0a333958b68d70f3c11e783516d38b0
- 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.
Change-Id: Ia5069c9976d07ee3949e637d8eb76a06b380cdec
* Update openstack-ansible-os_heat from branch 'master'
to 1787a43986ded7a730e0c5b215cb3a003cc551c7
- Add qos_prefetch_count to variables
When rabbit_stream_fanout is set to true, rabbit_qos_prefetch_count
should be set to a positive value.
This also fixes defenition of transient_quorum_queue as if
rabbit_stream_fanout is enabled - transient_quorum_queue should be also
enabled. [1]
[1] https://github.com/openstack/oslo.messaging/blob/master/oslo_messaging/_drivers/impl_rabbit.py#L726-L736
Change-Id: I4d3c9f792f01eb6d9cfa077d70a70daa6524d216
* Update openstack-ansible-os_barbican from branch 'master'
to c46805fe1a85bb480dfa8a869f5a28ee7ccb6e63
- Add qos_prefetch_count to variables
When rabbit_stream_fanout is set to true, rabbit_qos_prefetch_count
should be set to a positive value.
This also fixes defenition of transient_quorum_queue as if
rabbit_stream_fanout is enabled - transient_quorum_queue should be also
enabled. [1]
[1] https://github.com/openstack/oslo.messaging/blob/master/oslo_messaging/_drivers/impl_rabbit.py#L726-L736
Change-Id: I3b7b501ded69c7d4ef0aa9b89649ad227cf51ed0
* Update openstack-ansible-os_swift from branch 'master'
to 2a9721eb26c1d830e494cbe129b419445511a768
- Add service policies defenition
In order to allow definition of policies per service, we need to add variables
to service roles, that will be passed to openstack.osa.mq_setup.
Currently this can be handled by leveraging group_vars and overriding `oslomsg_rpc_policies` as a whole, but it's not obvious and
can be non-trivial for some groups which are co-locating multiple services
or in case of metal deployments.
Change-Id: I1258e2dc385d8d004091167835e9c14e314cbc2b
* Update openstack-ansible-os_cloudkitty from branch 'master'
to f98219872599a214dbb3a412f3ed72a13c882523
- Add qos_prefetch_count to variables
When rabbit_stream_fanout is set to true, rabbit_qos_prefetch_count
should be set to a positive value.
This also fixes defenition of transient_quorum_queue as if
rabbit_stream_fanout is enabled - transient_quorum_queue should be also
enabled. [1]
[1] https://github.com/openstack/oslo.messaging/blob/master/oslo_messaging/_drivers/impl_rabbit.py#L726-L736
Change-Id: I2c25783d4c65aa04ad9305adf2cbb6028e1dab57
* Update openstack-ansible-os_mistral from branch 'master'
to 7b89942398defc65835d6a9579c88cd3d87a40d2
- 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: Ic5714dc3d6cd42ce1745c2e2044caf812dc94022
* Update openstack-ansible-os_designate from branch 'master'
to 487e8d9a0febbc89dc558e0a45b61e8a82aaadce
- Add qos_prefetch_count to variables
When rabbit_stream_fanout is set to true, rabbit_qos_prefetch_count
should be set to a positive value.
This also fixes defenition of transient_quorum_queue as if
rabbit_stream_fanout is enabled - transient_quorum_queue should be also
enabled. [1]
[1] https://github.com/openstack/oslo.messaging/blob/master/oslo_messaging/_drivers/impl_rabbit.py#L726-L736
Change-Id: I9c89c31e56d6c61d8ddbeb6ba1fb85140620a6bf
* Update openstack-ansible-os_tacker from branch 'master'
to 72059c1cfb2484edb4dd73ae0e89060ab2d5b323
- 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: I7d439d03086ef65e3533d87cf1dc5c0237c8eeb0
* Update openstack-ansible-os_tacker from branch 'master'
to 5a692ce993ab038c0804917585859cdbb2737f36
- Add variable to globally control notifications enablement
In order to be able to globally enable notification reporting for all services,
without an need to have ceilometer deployed or bunch of overrides for each
service, we add `oslomsg_notify_enabled` variable that aims to control
behaviour of enabled notifications.
Presence of ceilometer is still respected by default and being referenced.
Potential usecase are various billing panels that do rely on notifications
but do not require presence of Ceilometer.
Change-Id: I63f5b887608f4c43e1fa953fbc194414d9bebc30
* Update openstack-ansible-os_nova from branch 'master'
to 97c408e19da67c938f150fac17dbb7848b9628e2
- Add variable to globally control notifications enablement
In order to be able to globally enable notification reporting for all services,
without an need to have ceilometer deployed or bunch of overrides for each
service, we add `oslomsg_notify_enabled` variable that aims to control
behaviour of enabled notifications.
Presence of ceilometer is still respected by default and being referenced.
Potential usecase are various billing panels that do rely on notifications
but do not require presence of Ceilometer.
Change-Id: Ib5d4f174be922f9b6f5ece35128a604fddb58e59
* Update openstack-ansible-os_nova from branch 'master'
to 82d439c3fb0721aecb5cc46622a549f3d7ab7b7e
- Add service policies defenition
In order to allow definition of policies per service, we need to add variables
so service roles, that will be passed to openstack.osa.mq_setup.
Currently this can be handled by leveraging group_vars and overriding `oslomsg_rpc_policies` as a whole, but it's not obvious and
can be non-trivial for some groups which are co-locating multiple services
or in case of metal deployments.
Change-Id: I6a4989df2cd53cc50faae120e96aa4480268f42d
* Update openstack-ansible-os_tacker from branch 'master'
to f65cf84486472634d07e73a6915a025f8524f24e
- Add service policies defenition
In order to allow definition of policies per service, we need to add variables
to service roles, that will be passed to openstack.osa.mq_setup.
Currently this can be handled by leveraging group_vars and overriding `oslomsg_rpc_policies` as a whole, but it's not obvious and
can be non-trivial for some groups which are co-locating multiple services
or in case of metal deployments.
Change-Id: Ieb972f50687c3e37aca2627cf85ffe27271ada26
Zuul
OpenStack Release Bot