bo of some proxy
middleware, and translating a bunch of Swift's syslog lines to statsd events).
--
Florian Hines | @pandemicsyn
http://about.me/pandemicsyn
On Tuesday, January 29, 2013 at 12:16 PM, Dieter Plaetinck wrote:
> On Tue, 29 Jan 2013 15:24:31 -0200
> Gui Maluf mailto:gui
I just need to clean it up at this point (mainly the rebalance). Since the
rebalance (i.e. swift-ring-builder rebalance) can take minutes to complete when
you have lots of devices I need to move it off to a background task.
--
Florian Hines | @pandemicsyn
http://about.me/pandemicsyn
On
meone else adding features as well would be awesome!
--
Florian Hines | @pandemicsyn
http://about.me/pandemicsyn
On Monday, June 18, 2012 at 2:23 PM, Mark Gius wrote:
> Hello Swifters,
>
> I've got some interns working with me this summer and I had a notion that
> they mig
wift-recon cli. It's what
reports async-pending's, replication times, etc to graphite.
Right now it gets tied together by tiny hackish Flask app that generates some
tv dashboard's and will probably start doing the monitoring/alerting for the
traffic prediction/confidence bands (
unt a shared folder that uses swift for storage (ala
dropbox/jungledisk/fuse) ?
> Is it necessary that storage devices have to be mounted on /srv/node??
>
You can change where you mount devices with the "devices" config option in the
default section of your config.
--
Flori
ally have pretty complete Swift zenpack:
https://github.com/zenoss/ZenPacks.zenoss.OpenStackSwift#readme
You'll need to enable the recon middleware on the object servers to use it
though.
--
Florian Hines | @pandemicsyn
http://about.me/pandemicsyn
___
On Jun 9, 2011, at 1:09 PM, Jon Slenk wrote:
> hi,
>
> I'm experimenting with expanding a cluster's set of rings. The report
> is 100% ok before I expand, but when I run swift-stats-report after
> the expansion it fails to get all the stuff. Anybody have
> insight/thoughts/guesses re: this? Hrm.
On May 3, 2011, at 5:22 PM, Ant Messerli wrote:
> Hey all,
>
> I wanted to see what everyones opinions were on separating out some of the
> IRC channels. When the project started we decided to keep #openstack as the
> primary channel since the project was small at the time. Over the last yea
8 matches
Mail list logo