Comment 1 for bug 2003345

Bah, sorry -- I had pushed up a guarded version at one point [1], but grew less concerned upon realizing the only in-tree place that we'd trip it would be probe tests. One question I've got: how much of a "public" API do we want to make this? We know we have some external tooling that want to use MemcacheRing -- what sorts of tests do we want to make sure we don't accidentally introduce another breaking change?

[1] https://review.opendev.org/c/openstack/swift/+/869390/6/swift/common/utils.py