Hi Wido, Daan, We have support for this capability in the upcoming release of the ONTAP Plugin through a feature we call AutoSupport Data (ASUP). We are excited about the opportunity to further enhance and align this implementation with CloudStack requirements.
As part of this feature, the ONTAP Plugin generates and pushes ASUP data to ONTAP storage at a configurable frequency. We would like to understand the preferred mechanism or destination within CloudStack where this data should be delivered on a scheduled basis. The current ASUP payload is similar to the sample that Daan shared earlier. We would appreciate your input on the expected ingestion point and any specific requirements around data collection, storage, or consumption within CloudStack. Please let us know in case we can collaborate and take it forward. Regards Rajiv Jain On Sat, Aug 29, 2026 at 9:01 PM Wido den Hollander via dev < [email protected]> wrote: > > > Op 27-08-2026 om 14:21 schreef Nux: > > Hi, > > > > On one side I love the idea of being able to more properly assess where > > and how CloudStack is being used, > > on the other hand receiving, maintaining and securing this data seems > > like a small nightmare. > > To be clear, the data will be very anonymous, see the example JSON on > Github: > > https://github.com/wido/cloudstack/blob/6890a986f135125e919f13d021e0a01bc7b1b8d4/server/src/test/resources/usage-report-expected.json > > > Also, it's hard for me to imagine why someone running CloudStack in > > production would opt to share this information. > > To help the project? As a way of returning the favor. > > Wido > > > > > > > > > > > Daan Hoogland wrote: > >> +1 to this (old) idea sounds, it compelling and as a cloudstacker I > >> want this info.My only insecurity is on how to process the data once > >> in and who has access. What data we gather is something we can tune, > >> but it would be good to ask some AI input on that and start from > >> there. > >> Also a collector app would be needed (I propose Claude and I write it > >> in rust ;) which creates a data pool. > >> As for access to highly anonymised, denormalised, aggregated data. I > >> see not much harm in publishing it on a publicly accessible dashboard. > >> > >> On Thu, Aug 27, 2026 at 9:13 AM Wido den Hollander via dev > >> <[email protected]> wrote: > >>> Hello, > >>> > >>> I just opened a PR [0] for a "Call Home" functionality of CloudStack. > If > >>> enabled by the user the management server will send a report every 7 > >>> days (default, configurable) back to the project. > >>> > >>> This report is a anonymized JSON file which contains counts of the > >>> hypervisor type, host/cluster types, storage pool type/provider/scope, > >>> zone network and service providers, instance states/types, disk > offering > >>> characteristics, and the version upgrade history. > >>> > >>> Currently the project has almost no insights into how CloudStack is > >>> being used, we can only gather this information by sending out surveys. > >>> > >>> The discussion can be: Do we want this as a project? Who will have > >>> access to the submitted reports? Any enhancement proposals? Other > >>> feedback? > >>> > >>> Wido > >>> > >>> [0]: https://github.com/apache/cloudstack/pull/13985 > >> > >> > > > >
