commit 9279e3d2c01fbd1d4cc9d95005aff5deeaa77c6d
Author: Tim Burke <email address hidden>
Date: Tue Mar 12 09:13:46 2024 -0700
CI: Bring unit test jobs in line with 2024.1 tested runtimes
The last time I really looked at this was probably Yoga, when we were
targetting 3.6 through 3.9 (and left 3.7 and 3.8 as experimental jobs).
Now, though, OpenStack is targetting 3.8 through 3.11; as before, we
can assume that if tests pass on those two versions, they should pass
on the versions in-between, too. (But still have them as experimental,
on-demand jobs).
This change allows individual SLO segments to be downloaded by adding
an extra 'part-number' query parameter to the GET request. You can
also retrieve the Content-Length of an individual segment with a HEAD
request.
commit 4135133a63eb8dea52601593765dd853bbea30a0
Author: Matthew Oliver <email address hidden>
Date: Tue Mar 5 14:44:37 2024 +1100
memcachering: change failed to yield log message
Currently when the memcachering `_get_conns` method runs out of memcached
servers to try and so fails to yield anything we log a:
All memcached servers error-limited
However, this error message isn't entirely accurate. It can also fail
because it failed to connect all it's memcached servers not just because
they're error limited.
You can disable error-limiting of memcached servers. So in this case
this error message is a red-herring.
Downstream we use a mcrouter client on each node which itself talks to a
bunch of memcache servers. Therefore in swift's memcachering client we
only configure the 1 mcrouter client as a single server in the ring.
Because of this we disable memcached error-limiting.
If the node gets too overloaded we've had timeouts talking to the local
mcrouter client. This fires off error-limitted log messages which can
confuse things.
Because it's possible to turn off error-limiting, the log line isn't
quite adequate anymore. So this patch changes it to:
Reviewed: https:/ /review. opendev. org/c/openstack /swift/ +/913237 /opendev. org/openstack/ swift/commit/ 774ab78455dd085 6d3e0beb47c4b08 8512667dac
Committed: https:/
Submitter: "Zuul (22348)"
Branch: feature/mpu
commit 5f95b6b26db1c86 dd9c5276c4124dd 80041df75f
Author: Tim Burke <email address hidden>
Date: Mon Mar 11 11:04:32 2024 -0700
AUTHORS/ CHANGELOG for 2.33.0
Change-Id: I6b0a074fca4d6b d3b8b95888ae872 1a62f3a6df0
commit 9279e3d2c01fbd1 d4cc9d95005aff5 deeaa77c6d
Author: Tim Burke <email address hidden>
Date: Tue Mar 12 09:13:46 2024 -0700
CI: Bring unit test jobs in line with 2024.1 tested runtimes
The last time I really looked at this was probably Yoga, when we were
targetting 3.6 through 3.9 (and left 3.7 and 3.8 as experimental jobs).
Now, though, OpenStack is targetting 3.8 through 3.11; as before, we
can assume that if tests pass on those two versions, they should pass
on the versions in-between, too. (But still have them as experimental,
on-demand jobs).
See https:/ /governance. openstack. org/tc/ reference/ runtimes/ 2024.1. html
Keep 2.7 and 3.6 testing as our own self-imposed minimums.
Change-Id: I7700aa3c93df31 1644655e7ebaf0b 67aa692ee80
commit b06ffea94131682 40d31110fcff0a5 df2cf62f47
Author: Tim Burke <email address hidden>
Date: Tue Mar 12 09:06:23 2024 -0700
CI: Update rolling-upgrade jobs to point to unmaintained branches
Change-Id: I936d9074ab60e3 4b379fb207d63f1 0bd5c3a4312
commit d10351db301793e e35a8f87c599f60 c77b5d8dd4
Author: Clay Gerrard <email address hidden>
Date: Tue Feb 27 15:46:07 2024 -0600
s3api test for zero byte mpu
Change-Id: I89050cead3ef2d 5f8ebfc9cb58f73 6f33b1c44fe
commit 46e7da97c6e620b a2998872901ed44 055714e699
Author: Ashwin Nair <email address hidden>
Date: Mon Sep 11 14:03:01 2023 -0700
s3api: Support GET/HEAD request with ?partNumber
Co-Authored-By: Alistair Coles <email address hidden> 6bc419377fe23fc f5603a89f45
Co-Authored-By: Clay Gerrard <email address hidden>
Closes-Bug: #1735284
Change-Id: Ib396309c706fbc
commit 6adbeb40365b88c 721294e72c8a95a ccb1b1d4f7
Author: Ashwin Nair <email address hidden>
Date: Mon Sep 11 11:48:00 2023 -0700
slo: part-number=N query parameter support
This change allows individual SLO segments to be downloaded by adding
an extra 'part-number' query parameter to the GET request. You can
also retrieve the Content-Length of an individual segment with a HEAD
request.
Co-Authored-By: Clay Gerrard <email address hidden> f042b52dd5db000 072f2c7512e
Co-Authored-By: Alistair Coles <email address hidden>
Change-Id: I7af0dc9898ca35
commit dc379af8936e043 a01bd11e7fa3d24 df03037a61
Author: OpenStack Release Bot <email address hidden>
Date: Tue Mar 12 10:49:32 2024 +0000
reno: Update master for unmaintained/xena
Update the xena release notes configuration to build from d/xena.
unmaintaine
Change-Id: I72576af46cc13f ac0a7a69461b673 931c8b8496e
commit 3ad1565f0ace40b 6a0a33270003017 5a4c2a1134
Author: OpenStack Release Bot <email address hidden>
Date: Tue Mar 12 10:49:01 2024 +0000
reno: Update master for unmaintained/ wallaby
Update the wallaby release notes configuration to build from d/wallaby.
unmaintaine
Change-Id: Ieb2d4542d395bb 1f4498beab0d9ec 146fad7ba84
commit 0d8c89b123a7622 91d083a6f1ec3e1 0e05c13780
Author: OpenStack Release Bot <email address hidden>
Date: Tue Mar 12 10:48:24 2024 +0000
reno: Update master for unmaintained/ victoria
Update the victoria release notes configuration to build from d/victoria.
unmaintaine
Change-Id: I5a420de74a2ef5 096135511dfea24 89419414856
commit 6a426f7fa08014f 6d4b6b04f5e51c8 870f77eeaf
Author: Tim Burke <email address hidden>
Date: Mon Mar 11 10:35:13 2024 -0700
sharder: Add periodic_ warnings_ interval to example config
Change-Id: Ie3c64646373580 b70557f2720a13a 5a0c5ef7097
commit cc2778004205d6a 42d9a3f01bed8f2 1af0b482d2
Author: Alistair Coles <email address hidden>
Date: Wed Mar 6 10:59:24 2024 +0000
docs: add discussion of content-type metadata
Change-Id: I2aa13e2b23bda8 6c51ef6aaa69ea3 fd0075bb9ad
commit 4135133a63eb8de a52601593765dd8 53bbea30a0
Author: Matthew Oliver <email address hidden>
Date: Tue Mar 5 14:44:37 2024 +1100
memcachering: change failed to yield log message
Currently when the memcachering `_get_conns` method runs out of memcached
servers to try and so fails to yield anything we log a:
All memcached servers error-limited
However, this error message isn't entirely accurate. It can also fail
because it failed to connect all it's memcached servers not just because
they're error limited.
You can disable error-limiting of memcached servers. So in this case
this error message is a red-herring.
Downstream we use a mcrouter client on each node which itself talks to a
bunch of memcache servers. Therefore in swift's memcachering client we
only configure the 1 mcrouter client as a single server in the ring.
Because of this we disable memcached error-limiting.
If the node gets too overloaded we've had timeouts talking to the local
mcrouter client. This fires off error-limitted log messages which can
confuse things.
Because it's possible to turn off error-limiting, the log line isn't
quite adequate anymore. So this patch changes it to:
No more memcached servers to try
Change-Id: I97fb4f3ee2ac45 831aae14a782b2c 6dc73e82d85