Bug 1041913

Summary: [RFE][keystone]: capture keystone performance benchmarks
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/keystone/+spec/keystone-performance-benchmark
Whiteboard: upstream_milestone_none 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 16:58:15 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 20:02:49 UTC 
Cloned from launchpad blueprint https://blueprints.launchpad.net/keystone/+spec/keystone-performance-benchmark.

Description:

Discussed at the Havana ODS, there's a need to capture and provide keystone performance benchmarks over time. 

Options to dig through:
* Tempest is starting and/or talking about doing some of this based on mining log data from devstack gate runs.
* timjr@yahoo is using ZipKin to do whole-system tracing and analysis (https://etherpad.openstack.org/zipkin-tracing)
  - possibly leverage diffs and tomograph library (https://github.com/timjr/tomograph) for extending tracing points
* heckj has a script that mines HAProxy logs for basic performance stats from an external API perspective

Specification URL (additional information):

None