I've uploaded the checks we use in production here at Spil Games to
https://github.com/spilgames/swift. Besides check_swift (which is a functional
test) everything's meant to gather statistics from the cluster and we're
looking to replace that with a Graphite-based solution to avoid having to
If John Dickinson can steal me a 30 minute block at the conference I'll
probably be giving a talk about it, but we (Rackspace) started switching to
Graphite back in December. We're basically just following the etsy cookbook to
graph all the things!.
We're using
On 02/22/2012 11:45 AM, Florian Hines wrote:
If John Dickinson can steal me a 30 minute block at the conference I'll
probably be giving a talk about it, but we (Rackspace) started switching
to Graphite back in December. We're basically just following the etsy
cookbook to graph all the things!.
This does bring up a more generic problem of sharing the
availability/performance code for all of the OpenStack components.
At the design summit, this was proposed as one of the example use cases of
the OpenStack community forge (I forget the exact name) but it was intended
as a place for
4 matches
Mail list logo
