| mcape | Is there a recommended upgrade path for old openstack swift installations? | 07:34 |
|---|---|---|
| mcape | Am considering upgrading 2.19.1 rocky to 2.29.1 yoga. | 07:34 |
| mcape | The cluster is not using encryption and erasure coding. | 07:34 |
| mcape | I was thinking of consecutive release upgrades, but there are hints of direct upgrade possibility in release notes. | 07:35 |
| mcape | Generally it looks like node-by-node rolling upgrade from 2.19.1 to 2.29.1 is possible, using old configs. | 07:35 |
| mcape | I would definitely test in on our test installation, however it is much less used than our production cluster, so any input is appreciated. | 07:35 |
| opendevreview | Tim Burke proposed openstack/swift stable/zed: CI: Pin tox<4 on stable branches https://review.opendev.org/c/openstack/swift/+/868932 | 18:44 |
| opendevreview | Tim Burke proposed openstack/swift stable/zed: CI: Pin tox<4 on stable branches https://review.opendev.org/c/openstack/swift/+/868932 | 19:42 |
| opendevreview | Clay Gerrard proposed openstack/swift master: Let zuul use new tox if it wants https://review.opendev.org/c/openstack/swift/+/868934 | 22:15 |
| opendevreview | Merged openstack/swift master: CI: Fix our usage of tox https://review.opendev.org/c/openstack/swift/+/868732 | 23:40 |
Generated by irclog2html.py 2.17.3 by Marius Gedminas - find it at https://mg.pov.lt/irclog2html/!