Support light weight sample model to all meter
Currently, The sample model (or metric), include metric attributes (unit, volume, type) and resource info see[1], the resource info include resource_metadata attribute, that may contain a big payload and make the Sample object heavy. The resource model also include these resource info, see[2] and overlap with Sample definition. we should make metering more focus on metering, so we should make the metric data (sample) only include attributes about metric, the value/volume, unit, type, resource_id. the resource info should be in Resource object. This light weight sample proposal will separate the resource from metric polling and will reduce the workload of message bus when transfer samples.
[1] https:/
[2] https:/
Blueprint information
- Status:
- Complete
- Approver:
- None
- Priority:
- Undefined
- Drafter:
- Liusheng
- Direction:
- Needs approval
- Assignee:
- None
- Definition:
- Obsolete
- Series goal:
- None
- Implementation:
-
Unknown
- Milestone target:
- None
- Started by
- Completed by
- gordon chung
Related branches
Related bugs
Sprints
Whiteboard
to be honest, this seems ilke it'll be breaking upgrades. can you give a better example. if not, let's just close this. -- gordc (10.03.16)
Work Items
Dependency tree
* Blueprints in grey have been implemented.
