On 03/18/2014 02:06 PM, Rohit Yadav wrote:
Cool idea, we can also have a monkey-brag ACS plugin which gives users an
API which can be triggered via cloudmonkey cli tool or by some gui/button
on the frontend to submit stats anonymously to our servers.


So I was thinking of writing 'cloudstack-report' as a tool.

The Debian and RPM packages can install a CRON which runs weekly/monthly to invoke the tool and reports to our service.

Via a config in /etc/cloudstack/report people can configure the tool. They could add their company/organization if they want or leave it set to anonymous.

The tool could do a PUT with some JSON data to 'report.cloudstack.org' which runs ElasticSearch where we then store all the data.

Easy to analyze and run statistics on.

I would like to have a opt-out since as a project member I want as much feedback about how CloudStack is being used, but as a user I want a opt-in.

So I think I'll start on the code itself to gather the data and later on we can discuss how we are going to do this.

In the end we need more feedback about the usage of CloudStack so we know what our users need.

Wido

Cheers.


On Tue, Mar 18, 2014 at 4:45 PM, Wido den Hollander <w...@widodh.nl> wrote:

On 03/18/2014 12:07 PM, Marcus wrote:

Do we have any general stats on how cloudstack is being used? Common
deployment sizes, largest deployments, etc? I'm curious as to how far
people have actually scaled it in real deployments, although I realize
that
the info can be proprietary.


Recently at the Ceph project the tool "ceph-brag" was developed. It
gathers information about your Ceph deployment and sends back the
information to the project.

Something like this might be nice (opt-in!!) for CloudStack. It can
anonymously report things like:
- Number of Instances
- Number of pods, cluster, hosts
- Number of Primary Storage and their type
- Basic / Advanced Networking

This could all be written into one JSON file which we can submit back to
the project.

With this we would get more information about how CloudStack is used.

Obviously, the code will be Open Source so people can see how we gather
the information (probably a lot of SQL selects..) and how we submit it to
our servers.

Is that something what you would like?

Wido


Reply via email to