I think its critical. It's difficult for me to pitch CloudStack as a
solution if I have no stats to show what's possible or how much of a
userbase it has. It would have been nice to have that yesterday. I
think in the past year things have gone backward in this regard, as
there used to at least be a list of contributing vendors somewhere
that I can no longer find. I wonder perhaps if that's due in part to
migration to the ASF. I think it will be hard to stay relevant if it's
difficult for the average IT person to get a sense of how active the
community is by visiting the site.

On Tue, Mar 18, 2014 at 7:06 AM, Rohit Yadav <bhais...@apache.org> 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.
>
> 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