Bug 1310114

Summary:	[RFE] Adding Ceilometer event support for Openstack providers
Product:	Red Hat CloudForms Management Engine	Reporter:	John Prause <jprause>
Component:	Providers	Assignee:	Tzu-Mainn Chen <tzumainn>
Status:	CLOSED ERRATA	QA Contact:	Ola Pavlenko <opavlenk>
Severity:	high	Docs Contact:
Priority:	high
Version:	5.5.0	CC:	carnott, cpelland, dajohnso, gblomqui, jcheal, jfrey, jhardy, mcornea, mfeifer, obarenbo, tshefi
Target Milestone:	GA	Keywords:	FutureFeature, ZStream
Target Release:	5.5.4
Hardware:	Unspecified
OS:	Unspecified
Whiteboard:	openstack
Fixed In Version:	5.5.4.0	Doc Type:	Enhancement
Doc Text:	This Red Hat CloudForms update adds the ability to specify the AMQP server IP address for OpenStack providers. As a result, when deploying an undercloud with SSL enabled, the Keystone endpoints are set on a different IP address than the address RabbitMQ uses to bind.	Story Points:	---
Clone Of:	1296146
Clones:	1326509 (view as bug list)		Environment:
Last Closed:	2016-05-31 13:40:56 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:	1326509

Comment 5 Marius Cornea 2016-05-16 08:55:00 UTC

I wasn't able to get the events from an Openstack infra provider showing up in the UI. evm.log shows the following message continuously:

INFO -- : Reseting Openstack Ceilometer connection after could not obtain a database connection within 5.000 seconds (waited 5.000 seconds).

After adjusting the pool in config/database.yml I hit BZ#1336336 which seems to be caused by a wrong version of fog.

Comment 8 Ronnie Rasouli 2016-05-26 12:03:42 UTC

I was able to verify.
Configured the openstack director with Ceilometer support, e.g. configured wrong credentials in AMQP 
grep store_events undercloud.conf 
store_events = true
I can see in nodes utilizations events

Comment 10 errata-xmlrpc 2016-05-31 13:40:56 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/RHBA-2016:1101