* Update swift from branch 'master'
to 1d30e8e69689d97e03f8883c66320eb125adae75
- Add Anish to authors.
Change-Id: I0441226e279b36a787ec85a459d6d1b72a2c8c84
* Update openstacksdk from branch 'master'
to 67887103acda99158b13e756cd2f36c4d33c177e
- Merge "Allow filtering BGPVPNs"
- Allow filtering BGPVPNs
BGPVPNs can be filtered server-side when being listed. The most
interesting filters here are for routers, networks and ports, as these
allow to filter for a specific association the BGPVPN has, but the other
filter options might come in handy as well.
route|import|export-target support only exact matches in the BGPVPN API,
meaning all entries need to be given in the right order as a comma
separated string. As this is quiet counter-intuitive for a user (that
might expect they could provide only one or unsorted entries) these
attributes have been left out.
Change-Id: I355b6584e115cf70a7fd040a24d30f9686555b85
* Update loci from branch 'master'
to 0842d310b33a51d2b1d90930c62b8ac451867d58
- Merge "Fix building python-nss==1.0.1 for Focal images"
- Fix building python-nss==1.0.1 for Focal images
Change-Id: I7c6e676087b4ed1f8acc9dd39558dfa79e1b0dff
* Update whitebox-tempest-plugin from branch 'master'
to 3d0c83974ef55fe2d5abf95470b1905438395a3f
- Merge "Deploy with CPU power management enabled"
- Deploy with CPU power management enabled
Until we fixed https://bugs.launchpad.net/nova/+bug/2056613 and
https://bugs.launchpad.net/nova/+bug/2056612, libvirt CPU power
management was broken with the `isolate` thread emualtor thread
policy, and with live migration. This was noticed more or less by
accident when the patch above this one triggered the right conditions
for our existing tests with incomplete coverage to break.
To prevent his from happening again, this patch turns on CPU power
management in our CI job, and modifies the test to assume that it's
turned on.
Change-Id: Ia48289ee4f909a33bfe6dac19eccff558b448da9
* Update openstacksdk from branch 'master'
to e4cd7e0abc56eb65f5172741b6237fe9097b0c19
- Merge "Add quota class set to shared file system"
- Add quota class set to shared file system
Add Quota class set Get and Update api implementation
to file share system as a service.
Change-Id: Id1c5591e7954d1d1f97b58ab409b4bd985e63125
* Update releases from branch 'master'
to 4efa3e12c1e7240dabdfb83069066004aeece04c
- Merge "[cyborg] Transition Zed to Unmaintained"
- [cyborg] Transition Zed to Unmaintained
This branch reached the end of its official stable maintained period,
hence this patch transition stable/zed branch to Unmaintained. (For
details about Unmaintained state please see: [1][2])
The transitions is as follows:
- tip of the stable/zed branch is tagged with zed-eom tag
- unmaintained/zed branch will be cut from zed-eom tag
- stable/zed branch will be deleted
Note:
- there will no longer be official releases off of zed branch after this
transition
- backports can be pushed to unmaintained/yoga branch
- openstack-unmaintained-core (or <project>-unmaintained-core groups if
such exists) have the rights to merge patches
Important: please +1 if the team is ready for us to proceed with this
transition, or -1 if there are any final Zed stable release with
backports currently in flight that we should wait for. For the latter
case, please propose a final Zed stable release patch, and rebase this
patch on top of that, with the latest commit hash of stable/zed.
The transition deadline is May 2nd, 2024. [3]
[1] https://docs.openstack.org/project-team-guide/stable-branches.html#unmaintained
[2] https://governance.openstack.org/tc/resolutions/20230724-unmaintained-branches.html
[3] https://releases.openstack.org
Change-Id: Ied156f2143d5bc159486428cdf10f76701b94378
* Update manila from branch 'master'
to 6175390f185242c0f4a82211e9f4b92fee23904e
- Merge "[DOC] Add subnet metadata to user guide"
- [DOC] Add subnet metadata to user guide
Add code block for share network subnet set and unset to user guide.
Closes-Bug: 2058391
Change-Id: If94d554378961388c6266a83025a5c74af077504
* Update releases from branch 'master'
to dea49c6d9d74c2a19419094daf9c436105369aad
- Merge "[cloudkitty] Transition Zed to Unmaintained"
- [cloudkitty] Transition Zed to Unmaintained
This branch reached the end of its official stable maintained period,
hence this patch transition stable/zed branch to Unmaintained. (For
details about Unmaintained state please see: [1][2])
The transitions is as follows:
- tip of the stable/zed branch is tagged with zed-eom tag
- unmaintained/zed branch will be cut from zed-eom tag
- stable/zed branch will be deleted
Note:
- there will no longer be official releases off of zed branch after this
transition
- backports can be pushed to unmaintained/yoga branch
- openstack-unmaintained-core (or <project>-unmaintained-core groups if
such exists) have the rights to merge patches
Important: please +1 if the team is ready for us to proceed with this
transition, or -1 if there are any final Zed stable release with
backports currently in flight that we should wait for. For the latter
case, please propose a final Zed stable release patch, and rebase this
patch on top of that, with the latest commit hash of stable/zed.
The transition deadline is May 2nd, 2024. [3]
[1] https://docs.openstack.org/project-team-guide/stable-branches.html#unmaintained
[2] https://governance.openstack.org/tc/resolutions/20230724-unmaintained-branches.html
[3] https://releases.openstack.org
Change-Id: I75b6eccf54a5331310e2c0eca497af8de7dc88f6
* Update releases from branch 'master'
to a09c4aea7dc6ec43819b0448955553cc70ae0153
- Merge "[vitrage] Transition Zed to Unmaintained"
- [vitrage] Transition Zed to Unmaintained
This branch reached the end of its official stable maintained period,
hence this patch transition stable/zed branch to Unmaintained. (For
details about Unmaintained state please see: [1][2])
The transitions is as follows:
- tip of the stable/zed branch is tagged with zed-eom tag
- unmaintained/zed branch will be cut from zed-eom tag
- stable/zed branch will be deleted
Note:
- there will no longer be official releases off of zed branch after this
transition
- backports can be pushed to unmaintained/yoga branch
- openstack-unmaintained-core (or <project>-unmaintained-core groups if
such exists) have the rights to merge patches
Important: please +1 if the team is ready for us to proceed with this
transition, or -1 if there are any final Zed stable release with
backports currently in flight that we should wait for. For the latter
case, please propose a final Zed stable release patch, and rebase this
patch on top of that, with the latest commit hash of stable/zed.
The transition deadline is May 2nd, 2024. [3]
[1] https://docs.openstack.org/project-team-guide/stable-branches.html#unmaintained
[2] https://governance.openstack.org/tc/resolutions/20230724-unmaintained-branches.html
[3] https://releases.openstack.org
Change-Id: I576b84b39af225a7a2c99dc6079911954c2158e6
* Update releases from branch 'master'
to 68d6e1ed4daf76d63d77587d5136e161dac5edf9
- Merge "[storlets] Transition Zed to Unmaintained"
- [storlets] Transition Zed to Unmaintained
This branch reached the end of its official stable maintained period,
hence this patch transition stable/zed branch to Unmaintained. (For
details about Unmaintained state please see: [1][2])
The transitions is as follows:
- tip of the stable/zed branch is tagged with zed-eom tag
- unmaintained/zed branch will be cut from zed-eom tag
- stable/zed branch will be deleted
Note:
- there will no longer be official releases off of zed branch after this
transition
- backports can be pushed to unmaintained/yoga branch
- openstack-unmaintained-core (or <project>-unmaintained-core groups if
such exists) have the rights to merge patches
Important: please +1 if the team is ready for us to proceed with this
transition, or -1 if there are any final Zed stable release with
backports currently in flight that we should wait for. For the latter
case, please propose a final Zed stable release patch, and rebase this
patch on top of that, with the latest commit hash of stable/zed.
The transition deadline is May 2nd, 2024. [3]
[1] https://docs.openstack.org/project-team-guide/stable-branches.html#unmaintained
[2] https://governance.openstack.org/tc/resolutions/20230724-unmaintained-branches.html
[3] https://releases.openstack.org
Change-Id: I41690e5591f55de5880744cebe92881728322f45
* Update loci from branch 'master'
to 6aa92e029da939d9df55abf3de6cb4628aa77f76
- Stop building Ubuntu Focal images for master
Master branch is not compatible with Ubuntu Focal.
Some projects like Octavia recently bumped
the minimal required python version to 3.9 while
the default python3 version in Focal is 3.8.
Also Nova requires Libvirt/Qemu newer than the
default versions on Ubuntu Focal.
See for example:
https://review.opendev.org/c/openstack/octavia/+/915970https://review.opendev.org/c/openstack/nova/+/887255
Change-Id: Ida62539a250554e776eaae3fdf283716b98f8298
* Update releases from branch 'master'
to 7d2d96fd0574306024e622875f170fcf01efe7d6
- Merge "[adjutant] Transition Zed to Unmaintained"
- [adjutant] Transition Zed to Unmaintained
This branch reached the end of its official stable maintained period,
hence this patch transition stable/zed branch to Unmaintained. (For
details about Unmaintained state please see: [1][2])
The transitions is as follows:
- tip of the stable/zed branch is tagged with zed-eom tag
- unmaintained/zed branch will be cut from zed-eom tag
- stable/zed branch will be deleted
Note:
- there will no longer be official releases off of zed branch after this
transition
- backports can be pushed to unmaintained/yoga branch
- openstack-unmaintained-core (or <project>-unmaintained-core groups if
such exists) have the rights to merge patches
Important: please +1 if the team is ready for us to proceed with this
transition, or -1 if there are any final Zed stable release with
backports currently in flight that we should wait for. For the latter
case, please propose a final Zed stable release patch, and rebase this
patch on top of that, with the latest commit hash of stable/zed.
The transition deadline is May 2nd, 2024. [3]
[1] https://docs.openstack.org/project-team-guide/stable-branches.html#unmaintained
[2] https://governance.openstack.org/tc/resolutions/20230724-unmaintained-branches.html
[3] https://releases.openstack.org
Change-Id: I2d27b3b6c3e1295f320f50af5e5b735729253caa
* Update releases from branch 'master'
to f2ae15ce172e3f7b8df6ee1f65358c591cd4c98d
- Merge "[monasca] Transition Zed to Unmaintained"
- [monasca] Transition Zed to Unmaintained
This branch reached the end of its official stable maintained period,
hence this patch transition stable/zed branch to Unmaintained. (For
details about Unmaintained state please see: [1][2])
The transitions is as follows:
- tip of the stable/zed branch is tagged with zed-eom tag
- unmaintained/zed branch will be cut from zed-eom tag
- stable/zed branch will be deleted
Note:
- there will no longer be official releases off of zed branch after this
transition
- backports can be pushed to unmaintained/yoga branch
- openstack-unmaintained-core (or <project>-unmaintained-core groups if
such exists) have the rights to merge patches
Important: please +1 if the team is ready for us to proceed with this
transition, or -1 if there are any final Zed stable release with
backports currently in flight that we should wait for. For the latter
case, please propose a final Zed stable release patch, and rebase this
patch on top of that, with the latest commit hash of stable/zed.
The transition deadline is May 2nd, 2024. [3]
[1] https://docs.openstack.org/project-team-guide/stable-branches.html#unmaintained
[2] https://governance.openstack.org/tc/resolutions/20230724-unmaintained-branches.html
[3] https://releases.openstack.org
Change-Id: I87a086d6e8d61f8dfc32f0fb9c406b07107e8fa6
* Update releases from branch 'master'
to cb4258a5e4d3feadd0c6c9578b0ffbe60051bc86
- Merge "[zaqar] Transition Zed to Unmaintained"
- [zaqar] Transition Zed to Unmaintained
This branch reached the end of its official stable maintained period,
hence this patch transition stable/zed branch to Unmaintained. (For
details about Unmaintained state please see: [1][2])
The transitions is as follows:
- tip of the stable/zed branch is tagged with zed-eom tag
- unmaintained/zed branch will be cut from zed-eom tag
- stable/zed branch will be deleted
Note:
- there will no longer be official releases off of zed branch after this
transition
- backports can be pushed to unmaintained/yoga branch
- openstack-unmaintained-core (or <project>-unmaintained-core groups if
such exists) have the rights to merge patches
Important: please +1 if the team is ready for us to proceed with this
transition, or -1 if there are any final Zed stable release with
backports currently in flight that we should wait for. For the latter
case, please propose a final Zed stable release patch, and rebase this
patch on top of that, with the latest commit hash of stable/zed.
The transition deadline is May 2nd, 2024. [3]
[1] https://docs.openstack.org/project-team-guide/stable-branches.html#unmaintained
[2] https://governance.openstack.org/tc/resolutions/20230724-unmaintained-branches.html
[3] https://releases.openstack.org
Change-Id: I51ac024710dae8d291d9b0b459ff13e2d52d2f92
* Update releases from branch 'master'
to 9acf301043d1c81a7b2cd393c3655f4f5cc44a44
- Merge "[Quality Assurance] Transition Zed to Unmaintained"
- [Quality Assurance] Transition Zed to Unmaintained
This branch reached the end of its official stable maintained period,
hence this patch transition stable/zed branch to Unmaintained. (For
details about Unmaintained state please see: [1][2])
The transitions is as follows:
- tip of the stable/zed branch is tagged with zed-eom tag
- unmaintained/zed branch will be cut from zed-eom tag
- stable/zed branch will be deleted
Note:
- there will no longer be official releases off of zed branch after this
transition
- backports can be pushed to unmaintained/zed branch
- openstack-unmaintained-core (or <project>-unmaintained-core groups if
such exists) have the rights to merge patches
Important: please +1 if the team is ready for us to proceed with this
transition, or -1 if there are any final Zed stable release with
backports currently in flight that we should wait for. For the latter
case, please propose a final Zed stable release patch, and rebase this
patch on top of that, with the latest commit hash of stable/zed.
The transition deadline is May 2nd, 2024. [3]
[1] https://docs.openstack.org/project-team-guide/stable-branches.html#unmaintained
[2] https://governance.openstack.org/tc/resolutions/20230724-unmaintained-branches.html
[3] https://releases.openstack.org
Change-Id: Ie6a0034451fa7d6a2616129c99c2783f315f467c
* Update releases from branch 'master'
to efd0d55a261614495e21023450ef21dbf38ee681
- Merge "[requirements] Transition Zed to Unmaintained"
- [requirements] Transition Zed to Unmaintained
This branch reached the end of its official stable maintained period,
hence this patch transition stable/zed branch to Unmaintained. (For
details about Unmaintained state please see: [1][2])
The transitions is as follows:
- tip of the stable/zed branch is tagged with zed-eom tag
- unmaintained/zed branch will be cut from zed-eom tag
- stable/zed branch will be deleted
Note:
- there will no longer be official releases off of zed branch after this
transition
- backports can be pushed to unmaintained/yoga branch
- openstack-unmaintained-core (or <project>-unmaintained-core groups if
such exists) have the rights to merge patches
Important: please +1 if the team is ready for us to proceed with this
transition, or -1 if there are any final Zed stable release with
backports currently in flight that we should wait for. For the latter
case, please propose a final Zed stable release patch, and rebase this
patch on top of that, with the latest commit hash of stable/zed.
The transition deadline is May 2nd, 2024. [3]
[1] https://docs.openstack.org/project-team-guide/stable-branches.html#unmaintained
[2] https://governance.openstack.org/tc/resolutions/20230724-unmaintained-branches.html
[3] https://releases.openstack.org
Change-Id: I1436f982567f79d5ebb8f0204e5bb764cc75e701
* Update ironic from branch 'master'
to cd489983dec5a276a34e125da47bf0e5f8a403df
- Merge "Ensure [molds] password is not logged"
- Ensure [molds] password is not logged
The [molds] password option accepts a secret value apparently. So its
value should not appear in debug logs.
Change-Id: If8a54c1d4f74516f1c24f7286e76955b2e424f5c
* Update swift from branch 'master'
to 937af35e6251e559379eb41aa2799388eea7a2de
- Merge "object-expirer: add example to delay_reaping sample config"
- object-expirer: add example to delay_reaping sample config
Add an example of a delay_reaping config option with quoted key.
Change-Id: I0c7ead6795822ea0fb0e81abc1e4685d7946942c
Related-Change: I106103438c4162a561486ac73a09436e998ae1f0
* Update swift from branch 'master'
to f7b9a72a6ebaab6137fdd6494e4ed08cbab3733c
- Merge "object-expirer: test for mix of async and delayed deletes"
- object-expirer: test for mix of async and delayed deletes
Related-Change: I106103438c4162a561486ac73a09436e998ae1f0
Change-Id: I95606aed5a5bd70424fbc51dd965f238fa7f064f
* Update openstacksdk from branch 'master'
to 37db30af3c3df81f7d75b628281cb7f78f0b5e2b
- Merge "Fix AttributeError in delete_limit method"
- Fix AttributeError in delete_limit method
This commit resolves an issue in the delete_limit method of the
Identity V3 Proxy class. The method was incorrectly trying to
access a 'Limit' attribute of a 'Limit' object, causing an
AttributeError. The fix involves correctly passing the 'Limit'
class from the '_limit' module as the first argument to the
'_delete' method.
Closes-Bug: #2052650
Change-Id: I435f52f8085c899fe1be57fcd5a2ce6f04618427
* Update cinder-tempest-plugin from branch 'master'
to 5a5e1bf66535a650f5105783f23e8e12b84ba614
- Move create_image_with_data to BaseVolumeTest
Move this code to a base class so it can be used in
more tests.
Change-Id: If8bd605ec75c8ddf8a85bff4e32ceb435aa35b85
* Update openstacksdk from branch 'master'
to 1b6292c5a304c683c6edab5c3a8590ecb0eac0bf
- Merge "cloud: Do not reference other cloud mixin's methods"
- cloud: Do not reference other cloud mixin's methods
We are using a mixin-like pattern to construct the cloud layer of our
API. However, this is not a true mixin pattern since each of the
"mixins" have dependencies on each other and to be honest, it's really
only there to allow us to split up the otherwise giant 'Connection'
object. Unfortunately this pattern doesn't really work with type
checkers or language servers since there's no obvious way to identify
where the additional resources are coming from until they're combined in
the 'Connection' class. Fixing this will require multiple steps, but the
first it to remove all dependencies between the various service mixins.
As such, rather than depending on e.g. the 'get_volume' cloud method in
various compute-related cloud methods, we use the 'find_volume' proxy
method. A later change can then add these various proxy attributes,
exposing them.
Change-Id: I10d3782899ac519f715d771d83303990a8289f04
Signed-off-by: Stephen Finucane <stephenfin@redhat.com>
* Update openstacksdk from branch 'master'
to 5041ea8687b5d99fbfdd98068380a47e6495c01d
- Merge "cloud: Trivial fixes"
- cloud: Trivial fixes
Before we combine the various nova-net/neutron common network functions
address a few nits around return statement indentation and docstring
wrapping.
Change-Id: I992673d30225c6639012fd4add91e86ac5e72966
Signed-off-by: Stephen Finucane <stephenfin@redhat.com>
* Update python-openstackclient from branch 'master'
to 3950b4f7ce3bdd1ac516239c78fc24321abb493f
- Merge "tests: Fix trivial sorting issue"
- tests: Fix trivial sorting issue
We've seen an ordering issue pop up occasionally in the CI. Resolve it.
Change-Id: I4dd10268b673c260ac0894fac92cd8bea9e626f4
Signed-off-by: Stephen Finucane <stephenfin@redhat.com>
* Update swift from branch 'master'
to b6c377e7e5b9980442d1c70618af7b7f0c0c66f1
- Merge "support x-open-expired header for expired objects"
- support x-open-expired header for expired objects
If the global configuration option 'enable_open_expired' is set
to true in the config, then the client will be able to make a
request with the header 'x-open-expired' set to true in order
to access an object that has expired, provided it is in its
grace period. If this config flag is set to false, the client
will not be able to access any expired objects, even with the
header, which is the default behavior unless the flag is set.
When a client sets a 'x-open-expired' header to a true value for a
GET/HEAD/POST request the proxy will forward x-backend-open-expired to
storage server. The storage server will allow clients that set
x-backend-open-expired to open and read an object that has not yet
been reaped by the object-expirer, even after the x-delete-at time
has passed.
The header is always ignored when used with temporary URLs.
Co-Authored-By: Anish Kachinthaya <akachinthaya@nvidia.com>
Related-Change: I106103438c4162a561486ac73a09436e998ae1f0
Change-Id: Ibe7dde0e3bf587d77e14808b169c02f8fb3dddb3
* Update openstacksdk from branch 'master'
to 05279611f9e3fce8595ee25cc122e381ba361bf4
- Merge "cloud: Remove use of OpenStackCloudCreateException"
- cloud: Remove use of OpenStackCloudCreateException
We'd like to get rid of the openstack.cloud.exc module. This exception
has one user so it is an easy cull.
Change-Id: I9b6a96d3b4d66ed69d87ba2a1d27bee9bab8c98d
Signed-off-by: Stephen Finucane <stephenfin@redhat.com>
* Update telemetry-tempest-plugin from branch 'master'
to 2985e2d88e59920016b9588ba83bf1f8e58e941d
- Merge "Ensure both severities are used in test data"
- Ensure both severities are used in test data
... otherwise the test fails when all alarms are created with a single
severity.
Closes-Bug: #2059713
Change-Id: Ida719530d22ef9541c835da5ba63a888cb71ebb2
* Update openstacksdk from branch 'master'
to 12de8a105e0e2497905e9458ce2dc1a6b14b98d5
- Merge "hacking: Add check for deprecated exception types"
- hacking: Add check for deprecated exception types
We also move everything to a new module with no external imports so
flake8 can import it without needing to install all the dependencies of
openstacksdk.
Change-Id: I8e610bc196f530223b27a6fbb8e8ca11b6420b82
Signed-off-by: Stephen Finucane <stephenfin@redhat.com>
* Update openstacksdk from branch 'master'
to f22f20a9f6f19cf7d8ff2bcf3826e6dedab6f62b
- Merge "Allow tags to be passed through to compute.create_server"
- Allow tags to be passed through to compute.create_server
Setting tags on servers is useful for managing sets of related resources
(e.g., we're spawning JupyterHub instances in OpenStack and we want to
tag all servers created by our spawner to make it easier to clean things
up).
This commit configures the create_server method to accept the tags
keyword paramter and pass it through to compute.create_server.
Change-Id: I92a449e584f9912f2bff86939e3565c6b3001bb9
* Update openstacksdk from branch 'master'
to b77ebf2ae032cf1cc586d712c230655aa4486f74
- Merge "image: Pass correct stores argument"
- image: Pass correct stores argument
Change I3b897abccfecf9353be07abc8f8325d91f3eb9d4 introduced support for
multiple image stores. Unfortunately a typo was included that has been
carried forward since. Correct the mistake now and add a test to prevent
regressions.
Change-Id: I4d2c81d19d295aae8a77007a1c7de7083d061f24
Signed-off-by: Stephen Finucane <stephenfin@redhat.com>
* Update openstacksdk from branch 'master'
to 7ad4623a97b16e35f33e55f8fd44aecb6586daa1
- Merge "Add Binero public cloud to vendor"
- Add Binero public cloud to vendor
The [1] patch missed the actual
vendor JSON file.
[1] https://review.opendev.org/c/openstack/openstacksdk/+/915984
Change-Id: I22683505b4a7cf9c10314966309089b6e0ccf199
* Update openstacksdk from branch 'master'
to 28059afdfd22dd399ce4ff41e97068a2442bcc2a
- Merge "pre-commit: Bump versions"
- pre-commit: Bump versions
We apply fold in the new black changes also.
Change-Id: I632728aa81e6c55423c0275a0a9b35e0753980a6
Signed-off-by: Stephen Finucane <stephenfin@redhat.com>
* Update releases from branch 'master'
to d341d6882da2f35e468946b0f0b803652d23012a
- Merge "Release Neutron for stable/zed"
- Release Neutron for stable/zed
This release picks up latest backports before transition to Unmaintained
% git log --oneline --no-merges 21.2.0~..a418da89c11d9f1a15c7880c443c84a2afed84d7
4fc3c71546 Fix KeyError failure in _sync_subnet_dhcp_options()
de9e3e8c9b Fix TestOVNMechanismDriver ipv6 tests
ca25eb96f1 Enhance IptablesFirewallDriver with remote address groups
386ebde547 Use the system-dependent string for IP protocol 4
29d28152ac Remove duplicate rows in MySQL query output
38ac22354d fix netns deletion of broken namespaces
cf21a4d979 [OVN] Set MTU of the VETH interfaces between OVS and metadata
7c7b020abe Fix iptables mapping of 'ipip' protocol
d253552ad2 [stable-only][OVN] Set VETH interface MAC address before up
b7e219391d Stable-Only: Temporary stop running grenade jobs on Zed
aedb872e4f Ensure that haproxy spawned by the metadata agents is active
85debddc1c Remove TripleO jobs
32d7efbfb0 Retry ``set|get_link_attribute(s)`` if the interface is not present
b9e3818b6e [OVN] Add ``subnetpool-prefix-ops`` extension to ML2/OVN mech driver
1f5ce18a14 [OVN][FT] Retry in case of timeout when executing "ovsdb-client".
c47c600b6a [Fullstack] Consolidate segmentation_id update tests into single test
5250b62a85 [Fullstack] Remove SecurityGroupRulesTest.test_normalized_cidr_in_rule test
af83df07f4 [Fullstack] Remove test_port_shut_down module
69bda7333f [Fullstack] Remove unnecessary tests
2de488ab11 Set trunk parent port as access port in ovs to avoid loop
0396b33bc4 Revert "Add sleep before checking if ovs port is in the namespace"
905e2e430a Forbid the subnet gateway IP deletion if a router interface is attached
8f15164068 Register Chassis_Private table in BaseOvnSbIdl
222c997022 Add sleep before checking if ovs port is in the namespace
2c8076dd28 Add max limit to agent_down_time
5dcad1d7c7 Don't set port capabilities for OVS HW offloading
bbe235779b Improve the SG RPC callback ``security_group_info_for_ports``
602bb1a325 [OVN][FT] Make explicit the "publish" call check in "test_port_forwarding"
4eb234a447 [OVN] DB sync host/physnet - filter on agent_type
4698dd899f Metadata: handle process exceptions
74a3262a8a Correctly validate subnet arguments when using a subnetpool
de5b7244ee [Fullstack] Double check that agent is dead when it should be dead
69e0dacd05 [DHCP agent] Fetch OVN Metadata port from plugin
9d22276013 get_hosts_mapped_with_segments add filter agt_type
cbebc3dd8a [DHCP agent] Fix route to OVN metadata port for non-isolated networks
b2100c6a29 docs: update default value of metadata workers for ml2/ovn
61ad633a33 Catch non-existent entry failures better in ip_lib
15d5db0d6e Ensure ovn loadbalancer FIPs are centralized upon neutron restarts
Change-Id: Icf56f158ed9ca27aabeff5d0b65bb033e13dada1
* Update swift from branch 'master'
to 2e487ba6950d87dd9b6e8666bb3a8dc5b68dc281
- Merge "expirer: account and container level delay_reaping"
- expirer: account and container level delay_reaping
The object expirer can be configured to delay the reaping of
objects from disk after their expiration time using account
and container level delay_reaping values. The delay_reaping
value of accounts and containers in seconds is configured in
the object server config. The object expirer references these
configured values to only reap objects from specified accounts
and containers after their corresponding delays.
The goal of the delay_reaping feature is to prevent accidental or
premature data loss if an object marked for deletion with the
'x-delete-at' feature should not be reaped immediately, for
whatever reason.
Configuring the delay_reaping value at a granular account and
container level is beneficial for being able to keep storage
capacity consumption in control while maintaining a desired
data recovery window.
This patch also adds a sample configuration, documentation, and
tests for bad configurations and grace period functionality.
Co-Authored-By: Anish Kachinthaya <akachinthaya@nvidia.com>
Change-Id: I106103438c4162a561486ac73a09436e998ae1f0
* Update taskflow from branch 'master'
to 448cf4136b28eeb7bed3d5084e93da6d5bf4a073
- Merge "Add functional job with redis enabled"
- Add functional job with redis enabled
Some of the "unit" test cases required actual redis running. This
introduces a separate job with actual redis service enabled so that
we run these tests in CI.
Change-Id: I1ddb580e9e8eb34937acba934520a998d249da3c
* Update puppet-openstack-integration from branch 'master'
to 512b95bff0ddf38ad827b75bb9c8877340f04553
- Merge "Enable ceilometer-polling in acceptance tests"
- Enable ceilometer-polling in acceptance tests
... and also ensure that gnocchi publisher is completely disabled.
Change-Id: If4179972103b30b5e0aad195d4ed8497e15938bd
* Update zun-ui from branch 'master'
to 8cdf78ecbd4e162e6d5fae6fe0114b496b4ea89e
- Update master for stable/2024.1
Add file to the reno documentation build to show release notes for
stable/2024.1.
Use pbr instruction to increment the minor version number
automatically so that master versions are higher than the versions on
stable/2024.1.
Sem-Ver: feature
Change-Id: Ib5133fc7c6723285d7d60dcdb8492859e47ce087
* Update python-zunclient from branch 'master'
to 0af6771362903f827243ff2cd59db8cdfda43a2f
- Merge "Update master for stable/2024.1"
- Update master for stable/2024.1
Add file to the reno documentation build to show release notes for
stable/2024.1.
Use pbr instruction to increment the minor version number
automatically so that master versions are higher than the versions on
stable/2024.1.
Sem-Ver: feature
Change-Id: I117e055457354a45bd5d99bb69a350d20ab18478
* Update python-zunclient from branch 'master'
to cba28ba942eb65d2ca3186240258ec9be6087d0a
- Merge "reno: Update master for unmaintained/wallaby"
- reno: Update master for unmaintained/wallaby
Update the wallaby release notes configuration to build from
unmaintained/wallaby.
Change-Id: I5d16c086198124e4f7375c4de89dc51886435c99
* Update python-zunclient from branch 'master'
to 31f0b17bc48a06a1329a13e65e6c333a8b1ac700
- Merge "reno: Update master for unmaintained/xena"
- reno: Update master for unmaintained/xena
Update the xena release notes configuration to build from
unmaintained/xena.
Change-Id: Ibdafe7c44affe70deff8ec210c6b5143af4e90dd
* Update zun from branch 'master'
to 16eb87ee1cb5f04fd32d7277b4d6455b71925d24
- Merge "reno: Update master for unmaintained/xena"
- reno: Update master for unmaintained/xena
Update the xena release notes configuration to build from
unmaintained/xena.
Change-Id: I7d11ccf8f29aedb7737ceadfee29a0a790f7d7ff
* Update zun from branch 'master'
to 09338d75ecbf78d170bc836617125664876cb9e1
- Merge "reno: Update master for unmaintained/victoria"
- reno: Update master for unmaintained/victoria
Update the victoria release notes configuration to build from
unmaintained/victoria.
Change-Id: Iabe40faa1426c43e4b26c2396215035d0c24b0c3
* Update zun from branch 'master'
to bac3da7311ea3b3e346e26ccd5faf69cd8a54650
- Merge "Update master for stable/2024.1"
- Update master for stable/2024.1
Add file to the reno documentation build to show release notes for
stable/2024.1.
Use pbr instruction to increment the minor version number
automatically so that master versions are higher than the versions on
stable/2024.1.
Sem-Ver: feature
Change-Id: I781c0f9882f210575e3ce836e42dce94dc9811f9
* Update zun from branch 'master'
to 7e0b120fab6545ce80cde31fdf3522e07d96f257
- Merge "reno: Update master for unmaintained/wallaby"
- reno: Update master for unmaintained/wallaby
Update the wallaby release notes configuration to build from
unmaintained/wallaby.
Change-Id: I89a1b84a86ff32937706f560b2168484881d1174
* Update python-zunclient from branch 'master'
to 5354cf3903433c11ba6093d20e25754ce93c63a1
- Merge "reno: Update master for unmaintained/victoria"
- reno: Update master for unmaintained/victoria
Update the victoria release notes configuration to build from
unmaintained/victoria.
Change-Id: I596e2840e2e38e5dece4807c98b63b252d96e7ae
* Update python-zunclient from branch 'master'
to cd540e74319cd1ebee6e3f1a7c73652c0d1198f7
- reno: Update master for unmaintained/yoga
Update the yoga release notes configuration to build from
unmaintained/yoga.
Change-Id: I276dec1f3740deb3028c8be98f2ea174a4055880
* Update puppet-mistral from branch 'master'
to 81d8a8ac18c569aea224c34a36f13797d0f57d67
- Merge "coordination: Remove heartbeat_interval"
- coordination: Remove heartbeat_interval
This parameter was deprecated during the previous cycle[1].
[1] c7fa10285d33e9a6721773faf74e3e2d5c586031
Change-Id: Ib253453b39ae7ac68b6e85db8b262cd201413a5c
Anish Kachinthaya
OpenStack Release Bot