Bug 1042436

Summary:	[RFE][neutron]: Extend l3 metering API to be able to retrieve traffic counters
Product:	Red Hat OpenStack	Reporter:	RHOS Integration <rhos-integ>
Component:	openstack-neutron	Assignee:	RHOS Maint <rhos-maint>
Status:	CLOSED UPSTREAM	QA Contact:	Ofer Blaut <oblaut>
Severity:	medium	Docs Contact:
Priority:	low
Version:	unspecified	CC:	chrisw, lpeer, markmc, nyechiel, yeylon
Target Milestone:	---	Keywords:	FutureFeature, Triaged
Target Release:	---
Hardware:	Unspecified
OS:	Unspecified
URL:	https://blueprints.launchpad.net/neutron/+spec/l3-metering-api-ext
Whiteboard:	upstream_milestone_next upstream_status_needs-code-review upstream_definition_obsolete
Fixed In Version:		Doc Type:	Enhancement
Doc Text:		Story Points:	---
Clone Of:		Environment:
Last Closed:	2015-03-19 10:34:20 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 22:16:51 UTC

Cloned from launchpad blueprint https://blueprints.launchpad.net/neutron/+spec/l3-metering-api-ext.

Description:

Currently with the L3 metering API we are able to set labels/rules for the routers of a tenant, metering notification are sent for these labels/rules and are collected by ceilometer. However there is no API calls to retrieve traffic counters with neutron. The aim of this blueprint is to extend the metering API for this purpose.

Specification URL (additional information):

None

Comment 3 Nir Yechiel 2014-03-05 08:32:16 UTC

Updating based on upstream status

Comment 4 Nir Yechiel 2015-03-19 10:34:20 UTC

This RFE was automatically opened to track status of upstream development. At this point we see no reason to keep track of this in Red Hat bugzilla, thus closing it.