Open Stack

Hi Eoghan,

Thanks for the reply. But, I need to slightly disagree with your comments.

As you have mentioned that the Ceilometer is actually interested in
the following:

"compute.instance.*"

The below mentioned notifications are actually part of
"compute.instance.*" i.e. we can write

event_types = ['compute.instance.*']

or

event_types = ['compute.instance.create.start',
'compute.instance.create.end',
'compute.instance.delete.start',
'compute.instance.delete.end',
'compute.instance.shutdown.start',
'compute.instance.shutdown.end',
'compute.instance.power_off.start',
'compute.instance.power_off.end',
...............................................,
................................................]

See respectively:

https://wiki.openstack.org/wiki/SystemUsageData

https://github.com/openstack/ceilometer/blob/master/ceilometer/compute/notifications.py#L20

Here the file "notifications.py" has Converters for producing compute
sample messages from Notification Events.

But the Ceilometer-collector is unable to fetch these notifications
from notifications.info queue.

And so Converting these notifications into sample messages is the
secondary task which the file "notifications.py" does if the
notification is fetched.

Thank you.

Regards,
Sravani M

On 12/10/13, Eoghan Glynn <eglynn at redhat.com> wrote:

 Hi Sravani,

 Here are the compute notification event types that ceilometer is actually
 interested in (modulo wildcard expansion):

  * 'compute.instance.*'

  * 'compute.instance.delete.samples'

  * 'scheduler.run_instance.scheduled'

 See respectively:

  *
 https://github.com/openstack/ceilometer/blob/master/ceilometer/compute/notifications.py#L73

  *
 https://github.com/openstack/ceilometer/blob/master/ceilometer/compute/notifications.py#L161

  *
 https://github.com/openstack/ceilometer/blob/master/ceilometer/compute/notifications.py#L54

 So, clearly ceilometer is only interested in a subset of these
 notifications,
 hence that's all that it processes.

 Cheers,
 Eoghan


 ----- Original Message -----
 Hi All,

 I'm trying to catch Nova Compute Notifications in Ceilometer

 I have Openstack installed on Ubuntu 13.04 using devstack.

 While launching an instance, Nova Compute is sending the required
 notifications to notifications.info queue.


 The same could be seen in the Nova Compute logs:

 2013-12-03 12:19:07.617 DEBUG nova.openstack.common.rpc.amqp
 [req-32a523c5-ebeb-4885-88e9-986918ab7f86 demo demo]
 Sending compute.instance.create.start on notifications.info from
 (pid=5418) notify
 /opt/stack/nova/nova/openstack/common/rpc/amqp.py:621
 ..
 ....

 2013-12-03 12:19:11.313 DEBUG nova.openstack.common.rpc.amqp
 [req-32a523c5-ebeb-4885-88e9-986918ab7f86 demo demo]
 Sending compute.instance.create.end on notifications.info from
 (pid=5418) notify
 /opt/stack/nova/nova/openstack/common/rpc/amqp.py:621


 But the ceilometer is unable to fetch these notifications from
 notifications.info. Instead it is fetching only
 compute.instance.update notification.

 The same could be seen in the ceilometer-agent-notification:

 2013-12-03 12:19:06.999 14017 DEBUG ceilometer.notification [-]
 notification u'compute.instance.update' process_notification
 /opt/stack/ceilometer/ceilometer/notification.py:124
 2013-12-03 12:19:07.000 14017 AUDIT ceilometer.pipeline [-] Flush
 pipeline degree.temperature.current
 2013-12-03 12:19:07.001 14017 AUDIT ceilometer.pipeline [-] Flush
 pipeline meter_pipeline
 2013-12-03 12:19:07.001 14017 AUDIT ceilometer.pipeline [-] Flush
 pipeline cpu_pipeline
 2013-12-03 12:19:07.001 14017 AUDIT ceilometer.pipeline [-] Flush
 pipeline instance_pipeline
 2013-12-03 12:19:07.002 14017 AUDIT ceilometer.pipeline [-] Flush
 pipeline degree.temperature.current
 2013-12-03 12:19:07.002 14017 AUDIT ceilometer.pipeline [-] Flush
 pipeline meter_pipeline
 2013-12-03 12:19:07.002 14017 AUDIT ceilometer.pipeline [-] Flush
 pipeline cpu_pipeline
 2013-12-03 12:19:07.002 14017 AUDIT ceilometer.pipeline [-] Flush
 pipeline instance_pipeline

 I am facing the same issue with the below mentioned Compute notifications
 too:
 compute.instance.delete.start/.end
 compute.instance.shutdown.start/.end
 compute.instance.power_off.start/.end


 Please find my Configuration setup in the below mentioned files:

 [nova.conf]

 firewall_driver = nova.virt.libvirt.firewall.IptablesFirewallDriver
 compute_driver = libvirt.LibvirtDriver
 libvirt_cpu_mode = none
 libvirt_type = qemu
 rabbit_password = root
 rabbit_host = <IP>
 rpc_backend = nova.openstack.common.rpc.impl_kombu
 notification_driver = nova.openstack.common.notifier.rpc_notifier
 notification_driver = ceilometer.compute.nova_notifier
 notify_on_state_change = vm_and_task_state
 notification_topics = notifications
 topics = notifications
 control_exchange = openstack
 notify_api_faults = true


 [ceilometer.conf]

 verbose = True
 debug = True
 notification_topics = notifications
 rabbit_password = root
 rabbit_host = <IP>
 rpc_backend = ceilometer.openstack.common.rpc.impl_kombu
 nova_control_exchange = nova
 default_notification_level=INFO
 notification_driver = nova.openstack.common.notifier.rpc_notifier

 So, what changes can be done for Ceilometer to fetch the all the
 notifications which the Nova Compute sends on the notifications.info ?

 Kindly let me know if any more information is required.

 Thank You.

 Regards,
 Sravani M

 _______________________________________________
 Mailing list:
 http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack
 Post to     : openstack at lists.openstack.org
 Unsubscribe :
 http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack