Bug 1042313

Summary:	[RFE][ceilometer]: Pipeline configuration cleanup
Product:	Red Hat OpenStack	Reporter:	RHOS Integration <rhos-integ>
Component:	RFEs	Assignee:	RHOS Maint <rhos-maint>
Status:	CLOSED UPSTREAM	QA Contact:
Severity:	unspecified	Docs Contact:
Priority:	unspecified
Version:	unspecified	CC:	markmc, yeylon
Target Milestone:	---	Keywords:	FutureFeature
Target Release:	---
Hardware:	Unspecified
OS:	Unspecified
URL:	https://blueprints.launchpad.net/ceilometer/+spec/pipeline-configuration-cleanup
Whiteboard:	upstream_milestone_next upstream_status_not-started upstream_definition_obsolete
Fixed In Version:		Doc Type:	Enhancement
Doc Text:		Story Points:	---
Clone Of:		Environment:
Last Closed:	2015-03-19 17:20:17 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:24 UTC

Cloned from launchpad blueprint https://blueprints.launchpad.net/ceilometer/+spec/pipeline-configuration-cleanup.

Description:

Pipelines have are configured with the names of the counters they should produce, but they don't have a real list. Instead they have a set of wildcard patterns and negation options that can be used to test an individual counter by name. We should resolve that list fully when the pipeline is configured, so it is possible for the pipeline manager to ask the pipeline for a list of the counters supported by a pipeline. That will allow us to have the PublisherTask ask the pipeline which counters to collect, instead of having to work it out in advance.

Specification URL (additional information):

None