Backup volumes appear in the "vol listvol" with a "BK" status, which
broke our existing match which only handles RO/RW volumes.
Add matching for this, and a basic unit test for parsing of this
output.
Change-Id: I1b3e985f79977981b2f0d3e3d3823d99f7cf3626
After discussion, the best way to see if volumes are being released is
to check the creation date.
This adds the creation date to reported volume stats, and also starts
reporting RO volumes by default too (skipping them was a theory to
reduce output, but they are important for seeing how releases are
working).
The creation date is reported in statsd with a unix timestamp gauge
Change-Id: I3feb4eac26bf1eb7196531b2d01029d28417e162
Add a fileservers option (which extends the cell list if specified).
Add debug option to config file
Better handle all config variables and better document the sample
config file.
With a few volumes, stats tend to go missing as there's a big flood of
individual packets. Use the statsd pipeline which is meant for this
sort of batch reporting.
Test-case is updated to handle the batched messages which are
delineated by newlines.
Ian Wienand