cloudstack-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "ASF GitHub Bot (JIRA)" <>
Subject [jira] [Commented] (CLOUDSTACK-8677) Call-home functionality for CloudStack
Date Wed, 26 Aug 2015 09:38:46 GMT


ASF GitHub Bot commented on CLOUDSTACK-8677:

Github user bhaisaab commented on the pull request:
    @wido can you implement this as a plugin instead of core feature? Also do we want cloudstack
to report statistics on each run; I suggest to have it as a plugin with a small db entry (global
setting or a separate db) to track the last time+version we sent the payload/report and we
can report that on each upgrade and perform checks every time cloudstack runs. This also needs
to have a global lock in case of multiple mgmt servers.

> Call-home functionality for CloudStack
> --------------------------------------
>                 Key: CLOUDSTACK-8677
>                 URL:
>             Project: CloudStack
>          Issue Type: New Feature
>      Security Level: Public(Anyone can view this level - this is the default.) 
>          Components: Management Server
>    Affects Versions: Future, 4.6.0
>            Reporter: Wido den Hollander
>            Assignee: Wido den Hollander
>             Fix For: 4.6.0
> A call-home feature for the CloudStack management server would send anonimized reports
back to the CloudStack project.
> These statistics will contain numbers and details on how CloudStack will be used. It
will NOT contain:
> * Hostnames
> * IP-Addresses
> * Instance names
> It will report back:
> * Hosts (Number, version, type, hypervisor)
> * Clusters (Hypervisor en Management type)
> * Primary storage (Type and provider)
> * Zones (Network type and providers)
> * Instances (Number and types)
> This gives the CloudStack project a better insight on how CloudStack is being used and
allows us to develop accordingly.
> It will be OPT-OUT, using the "" users can disable usage reporting.
By default it will run every 7 days and send a JSON document to

This message was sent by Atlassian JIRA

View raw message