Bug 1042315

Summary: [RFE][ceilometer]: Tighten models
Product: Red Hat OpenStack Reporter: RHOS Integration <rhos-integ>
Component: RFEsAssignee: RHOS Maint <rhos-maint>
Status: CLOSED UPSTREAM QA Contact:
Severity: unspecified Docs Contact:
Priority: unspecified    
Version: unspecifiedCC: markmc, yeylon
Target Milestone: ---Keywords: FutureFeature
Target Release: ---   
Hardware: Unspecified   
OS: Unspecified   
URL: https://blueprints.launchpad.net/ceilometer/+spec/tighten-model
Whiteboard: upstream_milestone_none upstream_status_unknown upstream_definition_superseded
Fixed In Version: Doc Type: Enhancement
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2015-03-19 17:07:32 UTC Type: ---
Regression: --- Mount Type: ---
Documentation: --- CRM:
Verified Versions: Category: ---
oVirt Team: --- RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: --- Target Upstream Version:

Description RHOS Integration 2013-12-12 21:43:48 UTC 
Cloned from launchpad blueprint https://blueprints.launchpad.net/ceilometer/+spec/tighten-model.

Description:

Currently, the data model of Ceilometer has no limitation in theory: for example, there's nothing stating that a resource_id is always linked to only one project_id. While a lot of assumptions are done in various place around that, the schema don't always implement these.

We need to describe a tighter model with better defined relationship in Ceilometer samples and events to build a better APIv3 and a more optimized models, so it can have better performance in the end.

Specification URL (additional information):

https://wiki.openstack.org/wiki/Ceilometer/blueprints/tighten-model