<div dir="ltr"><div class=""><div class=""><div class=""><div class=""><span name="Sravani Madireddy" class="">Sravani,<br><br></span></div><div class=""><span name="Sravani Madireddy" class="">We are facing the same problem and I believe that it's devstack issue. We are working on fixing it. Will let you know asap.<br>
</span></div><div class=""><span name="Sravani Madireddy" class="">Check that </span>ceilometer-agent-notification is up.<br></div><div class=""><span name="Sravani Madireddy" class=""><br>Thanks,<br></span></div><div class="">
<span name="Sravani Madireddy" class="">Nadya<br></span></div></div></div></div><span name="Sravani Madireddy" class=""></span></div><div class="gmail_extra"><br><br><div class="gmail_quote">On Tue, Dec 10, 2013 at 1:44 PM, Sravani Madireddy <span dir="ltr"><<a href="mailto:sravani.madireddy14@gmail.com" target="_blank">sravani.madireddy14@gmail.com</a>></span> wrote:<br>
<blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">Hi Eoghan,<br>
<br>
Thanks for the reply. But, I need to slightly disagree with your comments.<br>
<br>
As you have mentioned that the Ceilometer is actually interested in<br>
the following:<br>
<br>
"compute.instance.*"<br>
<br>
The below mentioned notifications are actually part of<br>
"compute.instance.*" i.e. we can write<br>
<br>
event_types = ['compute.instance.*']<br>
<br>
or<br>
<br>
event_types = ['compute.instance.create.start',<br>
'compute.instance.create.end',<br>
'compute.instance.delete.start',<br>
'compute.instance.delete.end',<br>
'compute.instance.shutdown.start',<br>
'compute.instance.shutdown.end',<br>
'compute.instance.power_off.start',<br>
'compute.instance.power_off.end',<br>
...............................................,<br>
................................................]<br>
<br>
See respectively:<br>
<br>
<a href="https://wiki.openstack.org/wiki/SystemUsageData" target="_blank">https://wiki.openstack.org/wiki/SystemUsageData</a><br>
<br>
<a href="https://github.com/openstack/ceilometer/blob/master/ceilometer/compute/notifications.py#L20" target="_blank">https://github.com/openstack/ceilometer/blob/master/ceilometer/compute/notifications.py#L20</a><br>
<br>
Here the file "notifications.py" has Converters for producing compute<br>
sample messages from Notification Events.<br>
<br>
But the Ceilometer-collector is unable to fetch these notifications<br>
from <a href="http://notifications.info" target="_blank">notifications.info</a> queue.<br>
<br>
And so Converting these notifications into sample messages is the<br>
secondary task which the file "notifications.py" does if the<br>
notification is fetched.<br>
<br>
Thank you.<br>
<br>
Regards,<br>
Sravani M<br>
<div class="HOEnZb"><div class="h5"><br>
On 12/10/13, Eoghan Glynn <<a href="mailto:eglynn@redhat.com">eglynn@redhat.com</a>> wrote:<br>
<br>
Hi Sravani,<br>
<br>
Here are the compute notification event types that ceilometer is actually<br>
interested in (modulo wildcard expansion):<br>
<br>
* 'compute.instance.*'<br>
<br>
* 'compute.instance.delete.samples'<br>
<br>
* 'scheduler.run_instance.scheduled'<br>
<br>
See respectively:<br>
<br>
*<br>
<a href="https://github.com/openstack/ceilometer/blob/master/ceilometer/compute/notifications.py#L73" target="_blank">https://github.com/openstack/ceilometer/blob/master/ceilometer/compute/notifications.py#L73</a><br>
<br>
*<br>
<a href="https://github.com/openstack/ceilometer/blob/master/ceilometer/compute/notifications.py#L161" target="_blank">https://github.com/openstack/ceilometer/blob/master/ceilometer/compute/notifications.py#L161</a><br>
<br>
*<br>
<a href="https://github.com/openstack/ceilometer/blob/master/ceilometer/compute/notifications.py#L54" target="_blank">https://github.com/openstack/ceilometer/blob/master/ceilometer/compute/notifications.py#L54</a><br>
<br>
So, clearly ceilometer is only interested in a subset of these<br>
notifications,<br>
hence that's all that it processes.<br>
<br>
Cheers,<br>
Eoghan<br>
<br>
<br>
----- Original Message -----<br>
Hi All,<br>
<br>
I'm trying to catch Nova Compute Notifications in Ceilometer<br>
<br>
I have Openstack installed on Ubuntu 13.04 using devstack.<br>
<br>
While launching an instance, Nova Compute is sending the required<br>
notifications to <a href="http://notifications.info" target="_blank">notifications.info</a> queue.<br>
<br>
<br>
The same could be seen in the Nova Compute logs:<br>
<br>
2013-12-03 12:19:07.617 DEBUG nova.openstack.common.rpc.amqp<br>
[req-32a523c5-ebeb-4885-88e9-986918ab7f86 demo demo]<br>
Sending compute.instance.create.start on <a href="http://notifications.info" target="_blank">notifications.info</a> from<br>
(pid=5418) notify<br>
/opt/stack/nova/nova/openstack/common/rpc/amqp.py:621<br>
..<br>
....<br>
<br>
2013-12-03 12:19:11.313 DEBUG nova.openstack.common.rpc.amqp<br>
[req-32a523c5-ebeb-4885-88e9-986918ab7f86 demo demo]<br>
Sending compute.instance.create.end on <a href="http://notifications.info" target="_blank">notifications.info</a> from<br>
(pid=5418) notify<br>
/opt/stack/nova/nova/openstack/common/rpc/amqp.py:621<br>
<br>
<br>
But the ceilometer is unable to fetch these notifications from<br>
<a href="http://notifications.info" target="_blank">notifications.info</a>. Instead it is fetching only<br>
compute.instance.update notification.<br>
<br>
The same could be seen in the ceilometer-agent-notification:<br>
<br>
2013-12-03 12:19:06.999 14017 DEBUG ceilometer.notification [-]<br>
notification u'compute.instance.update' process_notification<br>
/opt/stack/ceilometer/ceilometer/notification.py:124<br>
2013-12-03 12:19:07.000 14017 AUDIT ceilometer.pipeline [-] Flush<br>
pipeline degree.temperature.current<br>
2013-12-03 12:19:07.001 14017 AUDIT ceilometer.pipeline [-] Flush<br>
pipeline meter_pipeline<br>
2013-12-03 12:19:07.001 14017 AUDIT ceilometer.pipeline [-] Flush<br>
pipeline cpu_pipeline<br>
2013-12-03 12:19:07.001 14017 AUDIT ceilometer.pipeline [-] Flush<br>
pipeline instance_pipeline<br>
2013-12-03 12:19:07.002 14017 AUDIT ceilometer.pipeline [-] Flush<br>
pipeline degree.temperature.current<br>
2013-12-03 12:19:07.002 14017 AUDIT ceilometer.pipeline [-] Flush<br>
pipeline meter_pipeline<br>
2013-12-03 12:19:07.002 14017 AUDIT ceilometer.pipeline [-] Flush<br>
pipeline cpu_pipeline<br>
2013-12-03 12:19:07.002 14017 AUDIT ceilometer.pipeline [-] Flush<br>
pipeline instance_pipeline<br>
<br>
I am facing the same issue with the below mentioned Compute notifications<br>
too:<br>
compute.instance.delete.start/.end<br>
compute.instance.shutdown.start/.end<br>
compute.instance.power_off.start/.end<br>
<br>
<br>
Please find my Configuration setup in the below mentioned files:<br>
<br>
[nova.conf]<br>
<br>
firewall_driver = nova.virt.libvirt.firewall.IptablesFirewallDriver<br>
compute_driver = libvirt.LibvirtDriver<br>
libvirt_cpu_mode = none<br>
libvirt_type = qemu<br>
rabbit_password = root<br>
rabbit_host = <IP><br>
rpc_backend = nova.openstack.common.rpc.impl_kombu<br>
notification_driver = nova.openstack.common.notifier.rpc_notifier<br>
notification_driver = ceilometer.compute.nova_notifier<br>
notify_on_state_change = vm_and_task_state<br>
notification_topics = notifications<br>
topics = notifications<br>
control_exchange = openstack<br>
notify_api_faults = true<br>
<br>
<br>
[ceilometer.conf]<br>
<br>
verbose = True<br>
debug = True<br>
notification_topics = notifications<br>
rabbit_password = root<br>
rabbit_host = <IP><br>
rpc_backend = ceilometer.openstack.common.rpc.impl_kombu<br>
nova_control_exchange = nova<br>
default_notification_level=INFO<br>
notification_driver = nova.openstack.common.notifier.rpc_notifier<br>
<br>
So, what changes can be done for Ceilometer to fetch the all the<br>
notifications which the Nova Compute sends on the <a href="http://notifications.info" target="_blank">notifications.info</a> ?<br>
<br>
Kindly let me know if any more information is required.<br>
<br>
Thank You.<br>
<br>
Regards,<br>
Sravani M<br>
<br>
_______________________________________________<br>
Mailing list:<br>
<a href="http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack" target="_blank">http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack</a><br>
Post to : <a href="mailto:openstack@lists.openstack.org">openstack@lists.openstack.org</a><br>
Unsubscribe :<br>
<a href="http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack" target="_blank">http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack</a><br>
<br>
_______________________________________________<br>
Mailing list: <a href="http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack" target="_blank">http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack</a><br>
Post to : <a href="mailto:openstack@lists.openstack.org">openstack@lists.openstack.org</a><br>
Unsubscribe : <a href="http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack" target="_blank">http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack</a><br>
</div></div></blockquote></div><br></div>