Bug 967310
Summary: | [RFE] add packstack support for installation & config of ceilometer | ||
---|---|---|---|
Product: | Red Hat OpenStack | Reporter: | Attila Fazekas <afazekas> |
Component: | openstack-packstack | Assignee: | Martin Magr <mmagr> |
Status: | CLOSED ERRATA | QA Contact: | Nir Magnezi <nmagnezi> |
Severity: | medium | Docs Contact: | |
Priority: | high | ||
Version: | 3.0 | CC: | ajeain, aortega, derekh, eglynn, fvollero, ichavero, jkt, mlopes, mmagr |
Target Milestone: | Upstream M3 | Keywords: | FutureFeature |
Target Release: | 4.0 | Flags: | nmagnezi:
needinfo-
|
Hardware: | Unspecified | ||
OS: | Unspecified | ||
Whiteboard: | |||
Fixed In Version: | openstack-packstack-2013.2.1-0.6.dev749.el6ost | Doc Type: | Enhancement |
Doc Text: | Story Points: | --- | |
Clone Of: | Environment: | ||
Last Closed: | 2013-12-20 00:03:22 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: | 994571, 1015878 | ||
Bug Blocks: | 975499 |
Description
Attila Fazekas
2013-05-26 12:58:18 UTC
There is a puppet module for ceilometer upstream in stackforge: https://github.com/stackforge/puppet-ceilometer which could potentially provide a good starting point for packstack ceilometer support. This puppet-ceilometer module was contributed by eNovance, who have apparently tested it extensively and proved it in the field with their customers. However, their usage has been Ubuntu-centric, so we would need to contribute some changes upstream in order for this to be usable with packstack on Fedora/RHEL. In particular, it supports only rabbitmq as the AMQP provider currently: https://github.com/stackforge/puppet-ceilometer/blob/master/manifests/init.pp#L33-L38 so this would need to optionally accept the qpid configuration parameters also, as do puppet modules for the other openstack projects: https://github.com/stackforge/puppet-nova/blob/master/manifests/init.pp#L191-L207 Also, one other departure from the usual pattern of the puppet modules used by packstack (IIUC), is that the ceilometer compute agent has a direct cross-project dependency on the nova compute agent catalog entry: https://github.com/stackforge/puppet-ceilometer/blob/master/manifests/agent/compute.pp#L107-L110 (this change to the nova-compute's nova.config is required so that a special ceilometer notification driver is installed, in order to catch the dieing breath of a deleted instance) Finally, eNovance targetted this work at Folsom initially, and there appear to be some throwbacks to Folsom-ness in the code, e.g. this setting of notification_driver=nova.openstack.common.notifier.rabbit_notifier as opposed to notification_driver=nova.openstack.common.notifier.rpc_notifier & rpc_backend=nova.openstack.common.rpc.impl_kombu: https://github.com/stackforge/puppet-ceilometer/blob/master/manifests/agent/compute.pp#L102-L105 However, overall, it looks like a decent enough starting point for packstack ceilometer support. will this be part og RHOS 4.0? It is currently not blocking the Havana tracker bug Taking over Ceilometer support. Due to Bug #1015878, Ceilometer cannot tested for basic sanity. Setting Bug #1015878 as a blocker for this bug. Bug #1015878 is in MODIFIED state, please check installation with the appropriate version of openstack-ceilometer. Verified NVR: openstack-packstack-2013.2.1-0.9.dev840.el6ost.noarch Puddle 2013-11-08.1 Verification Steps: 1. Install OpenStack 2. Verify that 'ceilomter meter-list' works (for sanity) 3. Verified that there are no errors in Celimeter logs 4. Verified that all Ceilomter services are up # for svc in api central collector compute ; do service openstack-ceilometer-$svc status ; done openstack-ceilometer-api (pid 22755) is running... openstack-ceilometer-central (pid 22725) is running... openstack-ceilometer-collector (pid 22696) is running... openstack-ceilometer-compute (pid 6091) is running... 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. http://rhn.redhat.com/errata/RHEA-2013-1859.html |