Ceilometer not consuming notifications, therefore not producing samples/events solely based on notifications.

[Miguel Alejandro Cantu]

Ceilometer is not consuming any notifications from the notification.* queues from the openstack service vhosts. This results in ever growing notification queues and ceilometer never producing samples/events based on notifications. I think this has something to do with the way ceilometer implements their queue listeners and how we separate each service out to it's own respective rabbitmq virtual host. I haven't fully figured out how to tell ceilometer to listen to specific external vhosts, but I am investigating.

[OpenStack Infra (hudson-openstack)]

Fix proposed to branch: master
Review: https://review.openstack.org/263774

[OpenStack Infra (hudson-openstack)]

Fix proposed to branch: liberty
Review: https://review.openstack.org/266491

[OpenStack Infra (hudson-openstack)]

Reviewed: https://review.openstack.org/263774
Committed: https://git.openstack.org/cgit/openstack/openstack-ansible/commit/?id=f4757d65745ac7f3c04beb6d0a3dd9125f81717a
Submitter: Jenkins
Branch: master

commit f4757d65745ac7f3c04beb6d0a3dd9125f81717a
Author: Miguel Alex Cantu <email address hidden>
Date: Tue Jan 5 15:24:09 2016 +0000

    Add ceilometer messaging_url for each service...

    Without specifying messaging_urls, ceilometer only listens on the vhost
    specified in the rabbit configuration directives.
    To align with the the default OSA architecture, which isolates each service
    into it's own respective rabbitmq vhost, this patchset has added jinja code
    in the ceilometer.conf.j2 template to specifiy a messaging_url for each service,
     and for each service, each rabbitmq host. This ensures ceilometer is spawning
    the correct number of listeners on the correct vhost and consuming notifications
    correctly.

    In addition, a few small changes were made in the patch set:

    * store_events is now True by default
    * rabbitmq_userid and rabbitmq_vhost service variables have been moved to group_vars.

    Change-Id: I2bd9cf0ac7ca0492f6b2c56897f77117d2ae730b
    Depends-On: I98bcd17dac9a47cc19e0d9ec90176945a6d7e355
    Closes-Bug: #1526457

[OpenStack Infra (hudson-openstack)]

Reviewed: https://review.openstack.org/266491
Committed: https://git.openstack.org/cgit/openstack/openstack-ansible/commit/?id=210012da415de74a979c4337e0f26e5450fd6a72
Submitter: Jenkins
Branch: liberty

commit 210012da415de74a979c4337e0f26e5450fd6a72
Author: Miguel Alex Cantu <email address hidden>
Date: Tue Jan 5 15:24:09 2016 +0000

    Add ceilometer messaging_url for each service...

    Without specifying messaging_urls, ceilometer only listens on the vhost
    specified in the rabbit configuration directives.
    To align with the the default OSA architecture, which isolates each service
    into it's own respective rabbitmq vhost, this patchset has added jinja code
    in the ceilometer.conf.j2 template to specifiy a messaging_url for each service,
     and for each service, each rabbitmq host. This ensures ceilometer is spawning
    the correct number of listeners on the correct vhost and consuming notifications
    correctly.

    In addition, a few small changes were made in the patch set:

    * store_events is now True by default
    * rabbitmq_userid and rabbitmq_vhost service variables have been moved to group_vars.

    Backports included:

    * https://review.openstack.org/#/c/267112/5

    Change-Id: I2bd9cf0ac7ca0492f6b2c56897f77117d2ae730b
    Closes-Bug: #1526457
    (cherry picked from commit f4757d65745ac7f3c04beb6d0a3dd9125f81717a)

[OpenStack Infra (hudson-openstack)]

Fix proposed to branch: kilo
Review: https://review.openstack.org/269773

[Doug Hellmann (doug-hellmann)]

This issue was fixed in the openstack/openstack-ansible 12.0.8 release.

[Doug Hellmann (doug-hellmann)]

This issue was fixed in the openstack/openstack-ansible 12.0.9 release.

[Doug Hellmann (doug-hellmann)]

This issue was fixed in the openstack/openstack-ansible 13.0.0 release.

[Davanum Srinivas (DIMS) (dims-v)]

This issue was fixed in the openstack/openstack-ansible 13.0.0 release.

[Davanum Srinivas (DIMS) (dims-v)]

This issue was fixed in the openstack/openstack-ansible 12.0.11 release.

[OpenStack Infra (hudson-openstack)]

Change abandoned by Jesse Pretorius (odyssey4me) (<email address hidden>) on branch: kilo
Review: https://review.openstack.org/269773
Reason: Kilo is heading towards EOL and this patch has been dormant for a long time.