search for: gitter

Displaying 9 results from an estimated 9 matches for "gitter".

Did you mean: jitter
2017 Oct 26
2
[Gluster-devel] Gluster Health Report tool
...rt which provides a monitoring dashboard for a Gluster cluster. Some detail at <https://github.com/Tendrl/documentation/wiki/Metrics> At present the stack is not consuming Prometheus, however, the team is looking at switching over so as to make a more malleable dashboard. There is of course a Gitter channel at <https://gitter.im/Tendrl/tendrl-devel> Install+configure instructions for the latest release are at <https://github.com/Tendrl/documentation/wiki/Tendrl-release-v1.5.3-(install-guide)> -- sankarshan mukhopadhyay <https://about.me/sankarshan.mukhopadhyay>
2017 Oct 25
0
[Gluster-devel] Gluster Health Report tool
Hi, since people are suggesting nagios then I can't resist suggesting exporting the metrics in the prometheus format, or at least making the project into a library so https://github.com/prometheus/client_python could be used to export the prometheus metrics. There has been an attempt at https://github.com/ofesseler/gluster_exporter but it is not maintained anymore. Cheers, Marcin On Wed,
2017 Oct 25
2
[Gluster-devel] Gluster Health Report tool
Hi Aravinda, Very nice initiative, thank you very much! As as small recommendation it would be nice to have a "nagios/icinga" mode, maybe through a "-n" parameter which will do the health check and output the status ina nagios/icinga compatible format. As such this tool could be directly used by nagios for monitoring. Best, M. > -------- Original Message -------- >
2017 Nov 08
9
Adding a slack for communication?
>From today's community meeting, we had an item from the issue queue: https://github.com/gluster/community/issues/13 Should we have a Gluster Community slack team? I'm interested in everyone's thoughts on this. - amye -- Amye Scavarda | amye at redhat.com | Gluster Community Lead
2017 Nov 09
0
Adding a slack for communication?
...imited search capabilities. If we establish a > gluster channel, what would be the archiving strategy? > > Thanks, > Vijay > If we want this, we can use something like slackarchive to be able to archive this and then publish it on the website. We could also look at being able to use Gitter more, which we already have, or a Slack-IRC bridge. Many options! - amye -- Amye Scavarda | amye at redhat.com | Gluster Community Lead
2011 Aug 31
5
3.1rc8 - posting files in a test no longer works
A previously working test, that posted a file object no longer works in the latest 3.1. The test looks like this: params[:media][:new_attachment] = File.open("#{Rails.root}/test/data/ less_than_100.png") post :create, params In the controller, I obviously expect params[:media][:new_attachment] to be a File object - and it used to be. Now it looks like #inspect has been called on the
2013 Feb 07
5
does unicorn fork like phusion?
Does unicorn work like phusion in that it automatically forks based on traffic levels? Or is that what thin does also? -- You received this message because you are subscribed to the Google Groups "Ruby on Rails: Talk" group. To unsubscribe from this group and stop receiving emails from it, send an email to rubyonrails-talk+unsubscribe-/JYPxA39Uh5TLH3MbocFF+G/Ez6ZCGd0@public.gmane.org
2015 Jul 04
2
[LLVMdev] LLVM parsers for popular languages? - Python, Rust, Go
Yep we have our own parser <https://github.com/vinzenz/libpypa/> and we would love to see other people use it. When we looked around at some other Python parsers we didn't feel like any of them were easy to extract and use on their own, so we wrote our own and I think were able to keep ours well-separated. There are some things that make parsing Python somewhat difficult to do in a
2014 Nov 19
14
[LLVMdev] Proposal: add Go frontend subproject based on llgo
Hi all, I'd like to propose the contribution of a Go frontend subproject to the LLVM project, based on the existing llgo project at https://github.com/go-llvm/llgo . As with the previous contribution of the Go bindings, I have obtained permission from all llgo contributors whose code is part of this contribution, to contribute their changes to the LLVM project and relicense their changes