Bug 1417214

Summary: Gnocchi scaling up to 5000 VMs
Product: Red Hat OpenStack Reporter: Franck Baudin <fbaudin>
Component: openstack-gnocchiAssignee: Pradeep Kilambi <pkilambi>
Status: CLOSED ERRATA QA Contact: Sasha Smolyak <ssmolyak>
Severity: high Docs Contact:
Priority: high    
Version: 12.0 (Pike)CC: akrzos, apevec, fbaudin, jdanjou, jjoyce, jschluet, lhh, nlevinki, tvignaud, yprokule
Target Milestone: Upstream M2Keywords: OtherQA, TestOnly, Triaged, UseCase
Target Release: 12.0 (Pike)   
Hardware: x86_64   
OS: Linux   
Whiteboard:
Fixed In Version: openstack-gnocchi-4.0.0-0.20170606093551.4b6c156.el7ost Doc Type: If docs needed, set a value
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2017-12-13 21:04:11 UTC Type: Bug
Regression: --- Mount Type: ---
Documentation: --- CRM:
Verified Versions: Category: ---
oVirt Team: --- RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: --- Target Upstream Version:
Embargoed:
Bug Depends On:    
Bug Blocks: 1442136, 1470825    

Description Franck Baudin 2017-01-27 14:56:13 UTC
Description of problem:

Telemetry is suffering of a bad reputation regarding performances, as first versions, before RHOSP9 were relying on MongoDB and Ceilometer API. It was performant enough to store the metrics but not to retrieve and exploit them – so the usage was very limited.


Solution Overview:

Gnocchi (for metrics) and Aodh (for alarms) have been implemented to resolve all scalabilities issues. MongoDB has been replaced by Gnocchi. Nothing specific needs to be deployed but we need to demonstrate and communicate on the new status of Telemetry: it now really scales!

We should provide a dimensioning guide for Telemetry at scale, indicating how and how far it scales and performs.

Comment 8 Julien Danjou 2017-11-15 13:17:12 UTC
Testing has been done by Alex Krzos and showed great improvements. He was able to monitor up to 20k VMs on a 5 minutes interval with OSP 12.

Results are presented here:

https://www.youtube.com/watch?v=PC96PpT05G4

Comment 11 errata-xmlrpc 2017-12-13 21:04:11 UTC
Since the problem described in this bug report should be
resolved in a recent advisory, it has been closed with a
resolution of ERRATA.

For information on the advisory, and where to find the updated
files, follow the link below.

If the solution does not work for you, open a new bug report.

https://access.redhat.com/errata/RHEA-2017:3462