| opendevreview | Merged openstack/swift feature/mpu: mpu: refactor-only: merge container db rows without mutating https://review.opendev.org/c/openstack/swift/+/963863 | 12:12 |
|---|---|---|
| opendevreview | Merged openstack/swift master: trivial: tests: add failure context to flakey assertion https://review.opendev.org/c/openstack/swift/+/967400 | 12:12 |
| opendevreview | Lhoussain AIT ASSOU proposed openstack/liberasurecode master: feature: LRC (locally repairable code backend) https://review.opendev.org/c/openstack/liberasurecode/+/959280 | 14:42 |
| opendevreview | Lhoussain AIT ASSOU proposed openstack/liberasurecode master: feature: LRC (locally repairable code backend) https://review.opendev.org/c/openstack/liberasurecode/+/959280 | 15:39 |
| DHE | If I want to make sure there's always an object server listening on a specific port when I'm doing per-disk listen ports, is there a way? The only thing that comes to mind is inserting a dummy device with weight 0 into ring files. | 19:39 |
| DHE | the objective is to give an external monitoring system a known port that it can access recon data from. but if a drive fails and is pulled out, that TCP port effectively closes and that's a complication. | 19:42 |
Generated by irclog2html.py 4.0.0 by Marius Gedminas - find it at https://mg.pov.lt/irclog2html/!