| opendevreview | Tim Burke proposed openstack/swift stable/yoga: CI: Pin tox<4 on stable branches https://review.opendev.org/c/openstack/swift/+/868941 | 06:29 |
|---|---|---|
| timburke | mcape, yes, a rolling upgrade from 2.19.1 to 2.29.1 should be possible with old configs; the fact that neither encryption nor erasure coding are in use should mean you'll miss a few pitfalls, too | 06:40 |
| timburke | general upgrade recommendations apply: if possible, upgrade all object servers, then container, then account, then proxies. if not possible, it's probably still fine; there may be some increase in 503s during the upgrade, but there haven't been any massive changes to the data path recently | 06:40 |
| timburke | you don't get the SIGUSR1 support until after upgrade, but if you want to minimize client disruptions, you can approximate it by upgrading swift, starting up a new set of *-server processes on each node, waiting for them to come up and be accepting connections, then send a SIGHUP to the old (manager) processes | 06:43 |
| timburke | all of that's still good under py27 (though i'm guessing you already know that and are stopping at 2.29.1 because of it :-) from there, you should be able to swap over to py3 pretty easily; we don't know of any risks running in a mixed py2/py3 environment at that late of a version | 06:47 |
| timburke | even though you're not running EC, you might want to upgrade liberasurecode -- there was a checksumming issue i uncovered a while back that was annoying to deal with, so it'd simplify your life if you ever decide to add an EC policy later | 06:51 |
| opendevreview | Merged openstack/swift stable/zed: CI: Pin tox<4 on stable branches https://review.opendev.org/c/openstack/swift/+/868932 | 08:03 |
Generated by irclog2html.py 2.17.3 by Marius Gedminas - find it at https://mg.pov.lt/irclog2html/!