Feature #2829
closedreport on cluster size/status (for service billing purposes)
0%
Description
The plan is to base support contract pricing on capacity,
which means we need a quick, easy (and moderately trusted)
means of ascertaining the deployed capacity of each supported
system.
SUGGESTED APPROACH (not to be taken to seriously)
Phone-home systems are often complex, controversial,
and brittle ... but such systems are usually intended
for support/diagnostic purposes and require regular and
detailed reports. For billing purposes we can probably
get by with something much simpler.
Perhaps we can create a new status command/option that lists
general identification, capacity and configuration information
followed by a digital signature for that report.
Customers with relatively open systems could create a cron
job that automatically ran this command and piped the output
to "mail config-reporting@inktank.com".
Customers in secure environments could copy the output,
satisfy themselves that it contained nothing inappropriate,
and then manually paste it into a message to be mailed to us.
Updated by Sage Weil over 11 years ago
- Translation missing: en.field_position set to 1
Updated by Sage Weil over 11 years ago
- Translation missing: en.field_story_points set to 5
- Translation missing: en.field_position deleted (
3) - Translation missing: en.field_position set to 1
Updated by Sage Weil over 11 years ago
- Translation missing: en.field_position deleted (
31) - Translation missing: en.field_position set to 1
Updated by Sage Weil over 11 years ago
- Status changed from New to Fix Under Review
Updated by Sage Weil over 11 years ago
- Target version set to 83
- Translation missing: en.field_position deleted (
12) - Translation missing: en.field_position set to 12
Updated by Anonymous over 11 years ago
- Priority changed from Normal to High
- Tags set to CY2012
Updated by Sage Weil over 11 years ago
- Status changed from Fix Under Review to Resolved
at some point we need the receiving end of this: extract the json, validate the crc, and stick it in some database or something. that comes later!
Updated by Sage Weil over 11 years ago
- Target version changed from 83 to v0.52a