Allow specification of object devices for audit
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
openstack-manuals |
Fix Released
|
Medium
|
Alexandra Settle |
Bug Description
https:/
commit 793489b80d212ef
Author: Eamonn O'Toole <email address hidden>
Date: Mon Feb 24 11:24:56 2014 +0000
Allow specification of object devices for audit
In object audit "once" mode we are allowing the user to specify
a sub-set of devices to audit using the "--devices" command-line
option. The sub-set is specified as a comma-separated list. This
patch is taken from a larger patch to enable parallel processing
in the object auditor.
We've had to modify recon so that it will work properly with this
change to "once" mode. We've modified dump_recon_cache()
so that it will store nested dictionaries, in other words it will
store a recon cache entry such as {'key1': {'key2': {...}}}. When
the object auditor is run in "once" mode with "--devices" set the
object_
{'object_
swift-recon is run, it hunts through the nested dicts to find the
appropriate entries. The object auditor recon cache entries are set
to {} at the beginning of each audit cycle, and individual disk
entries are cleared from cache at the end of each disk's audit cycle.
DocImpact
Change-Id: Icc53dac0a8136f
Changed in openstack-manuals: | |
status: | New → Confirmed |
importance: | Undecided → Medium |
milestone: | none → icehouse |
Changed in openstack-manuals: | |
milestone: | icehouse → juno |
Changed in openstack-manuals: | |
assignee: | nobody → Loic Dachary (dachary) |
Changed in openstack-manuals: | |
assignee: | Loic Dachary (dachary) → José (irigon) |
Changed in openstack-manuals: | |
milestone: | juno → kilo |
Changed in openstack-manuals: | |
milestone: | kilo → liberty |
Changed in openstack-manuals: | |
assignee: | José (irigon) → Alexandra Settle (alexandra-settle) |
To fix this bug
1) add a new section (or find existing section) on object-auditor to the admin-guide-cloud
2) Ensure it's noted that you can run the object-auditor 'once' in the configuration described in this bug report.
3) Consider adding a mention to the ops-guide