Nixa's profile - activity

2017-06-23 10:25:27 -0600 received badge  Student (source)
2017-05-09 00:27:49 -0600 received badge  Famous Question (source)
2016-05-06 17:47:15 -0600 received badge  Popular Question (source)
2016-05-06 17:47:15 -0600 received badge  Notable Question (source)
2016-02-23 02:25:47 -0600 received badge  Enthusiast
2016-02-15 09:01:08 -0600 asked a question Openstack Juno - Ceilometer meter-list doesn't show all meters


I can't get network meters for instance.

When I enter command ceilometer meter-list -q 'resource_id=<instance_id>' only cpu,disk,instance,memory and vcpus meters are shown.

I've tried to change notification_driver value in neutron.conf from messaging to: notification_driver = neutron.openstack.common.notifier.rpc_notifier

But that didn't help.

Thanks in advance.

2015-09-23 03:24:41 -0600 received badge  Famous Question (source)
2015-09-18 02:09:19 -0600 received badge  Notable Question (source)
2015-09-17 06:17:03 -0600 received badge  Popular Question (source)
2015-09-16 12:56:02 -0600 asked a question Ceilometer cpu_util average


I have yaml template that creates new instances when average cpu_util is above 15% for 60s (If I put threshold above that value OpenStack doesn't create new instances)

When I run load tests top command on my instance shows cpu_util around 95-100 (I run those load tests for longer periods than 60s) In ceilometer-alarm-notifier.log I get values like 15-16 when second instance is created and than values that activate alarm slowly rise, despite that new instances are created. When I stop load test those values quickly drop down and newly created instances are deleted and in notifier log I get values like 1-2 (threshold for scalingdown policy is avg below 5% over 60s).

So my question is how Ceilometer calculates cpu_util average, since it doesn't match top command values?