z-launchpad at brim
Aug 2, 2012, 2:07 PM
Post #3 of 3
On Aug 2, 2012, at 2:45 PM, Pete Zaitcev <zaitcev [at] redhat> wrote:
> The point is to use Swift itself _and_ Keystone, in order to find
> discrepancies or "orphan" accounts. I ended using listdir for now,
> since our installation is very small, so directories fit in memory.
> I have a feeling though that I must be reinventing the bicycle here.
> Surely someone, somewhere, have written a Swift consistency checker
> -- Pete
We do something pretty similar with Rackspace Cloud Files, though we don't use Keystone but Rackspace's Auth. Same basic principle though. Collect account "stats" from all the storage boxes and upload them as csv files into the cluster itself. External jobs grab the csvs and process them however they see fit (double-checking against auth, etc.)
Part of it (John Dickinson's Slogging Project):
OpenStack-operators mailing list
OpenStack-operators [at] lists