Ask Your Question

Skylab's profile - activity

2017-03-06 04:17:08 -0500 received badge  Famous Question (source)
2017-02-03 13:42:58 -0500 received badge  Famous Question (source)
2017-02-03 13:42:58 -0500 received badge  Notable Question (source)
2017-02-03 13:42:58 -0500 received badge  Popular Question (source)
2016-08-08 09:10:21 -0500 received badge  Famous Question (source)
2016-05-31 00:16:13 -0500 commented answer Unable to collect statistics meter compute.node.cpu.* data using Ceilometer command

I updated the same way whatever you explained above, and restarted the nova services, But still same issue I am able to see.

2016-05-31 00:14:13 -0500 received badge  Enthusiast
2016-05-30 20:04:18 -0500 received badge  Notable Question (source)
2016-05-30 07:13:32 -0500 answered a question Unable to collect statistics meter compute.node.cpu.* data using Ceilometer command

Hi All.

I also see same issue. I've updated the nova.conf as per your above discussion , But still same issue with me.

[root@icmcs opt]# ceilometer statistics --meter compute.node.cpu.percent -q 'resource_id=17a282d1-19c7-48f4-8cee-d3240df594eb' +--------+--------------+------------+-----+-----+-----+-----+-------+----------+----------------+--------------+ | Period | Period Start | Period End | Max | Min | Avg | Sum | Count | Duration | Duration Start | Duration End | +--------+--------------+------------+-----+-----+-----+-----+-------+----------+----------------+--------------+ +--------+--------------+------------+-----+-----+-----+-----+-------+----------+----------------+--------------+ [root@icmcs opt]#

2016-05-30 06:42:40 -0500 commented answer Ceilometer alaram state insufficient data

I hope as per above result, I think I don't have a meter ?, If yes ? How can install the meters ?.

And I added the "evaluation_interval=60" in ceilometer.conf and restarted the servicess.

+--------------------------------------+------------------+-----------------+----------------------+ [root@ic

2016-05-30 06:41:21 -0500 commented answer Ceilometer alaram state insufficient data

[root@icmcs opt]# ceilometer meter-list -q 'resource_id=17a282d1-19c7-48f4-8cee-d3240df594eb' +---------------------+-------+----------+--------------------------------------+----------------------------------+----------------------------------+ | Name | Type | Unit | Resource ID

2016-05-30 06:41:14 -0500 commented answer Ceilometer alaram state insufficient data

[root@icmcs opt]# nova list +--------------------------------------+-------------------------------------------------------+--------+------------+-------------+---------------------------+ | ID | Name | Status | Task

2016-05-30 06:41:04 -0500 commented answer Ceilometer alaram state insufficient data

How can I check cpu_util meter present or, I seek to created one VM and I try to see the cpu_util , but its nothing showing to me.

[root@icmcs opt]# ceilometer sample-list -m cpu_util --limit 5 +-------------+------+------+--------+------+-----------+ | Resource ID | Name | Type | Volume | Unit |

2016-05-30 00:44:03 -0500 received badge  Popular Question (source)
2016-05-30 00:43:29 -0500 commented answer Ceilometer alaram state insufficient data

cpu_util more than 90% , Still its not happening.

2016-05-27 05:38:53 -0500 asked a question Ceilometer alaram state insufficient data

I try to implement the Autoscaling using with Ceilometer. I am able to create stack with heat template and I stree the CPU untilization morethan 90% . but still scaling is not happening. Also I see one issue Ceilometer alarm state is "insufficient data"

[root@icmcs ceilometer]# ceilometer alarm-list +--------------------------------------+-------------------------------------------------+-------------------+----------+---------+------------+-----------------------------------------------------------------+------------------+ | Alarm ID | Name | State | Severity | Enabled | Continuous | Alarm condition | Time constraints | +--------------------------------------+-------------------------------------------------+-------------------+----------+---------+------------+-------------------------------------------------- | cacbac69-14eb-49c1-b1b1-042f8e0d3e52 | demo-autoscaling1-cpu_alarm_low-imzkpfqywqvn | insufficient data | low | True | True | cpu-util < 15.0 during 1 x 50s | None | | d24134d8-d484-4485-93d3-acf0e1f33471 | demo-autoscaling1-cpu_alarm_high-2jmfxxkuil2o | insufficient data | low | True | True | cpu-util > 50.0 during 1 x 50s | None | +--------------------------------------+-------------------------------------------------+-------------------+----------+---------+------------+--------------------------------------------------

Ceilometer cpu_util alos not capturing. [root@icmcs ceilometer]# ceilometer statistics -m cpu_util +--------+--------------+------------+-----+-----+-----+-----+-------+----------+----------------+--------------+ | Period | Period Start | Period End | Max | Min | Avg | Sum | Count | Duration | Duration Start | Duration End | +--------+--------------+------------+-----+-----+-----+-----+-------+----------+----------------+--------------+

I appreciate help on this. thanks.

2016-05-27 05:36:33 -0500 asked a question Ceilometer alaram state "insufficient data"

I try to implement the Autoscaling using with Ceilometer. I am able to create stack with heat template and I stree the CPU untilization morethan 90% . but still scaling is not happening. Also I see one issue Ceilometer alarm state is "insufficient data"

[root@icmcs ceilometer]# ceilometer alarm-list +--------------------------------------+-------------------------------------------------+-------------------+----------+---------+------------+-----------------------------------------------------------------+------------------+ | Alarm ID | Name | State | Severity | Enabled | Continuous | Alarm condition | Time constraints | +--------------------------------------+-------------------------------------------------+-------------------+----------+---------+------------+-----------------------------------------------------------------+------------------+ | 0091a7f1-a00b-4c1e-b754-689d661e21a3 | demo-autoscaling-cpu_alarm_low-7ie2nd24qrhq | insufficient data | low | True | True | cpu_util < 15.0 during 1 x 600s | None | | 2951807e-e4d1-4813-9db0-cc1dd43967cf | demo-autoscaling-cpu_alarm_high-z6wi2fy5isjd | insufficient data | low | True | True | cpu_util > 50.0 during 1 x 60s

Ceilometer cpu_util alos not capturing. [root@icmcs ceilometer]# ceilometer statistics -m cpu_util +--------+--------------+------------+-----+-----+-----+-----+-------+----------+----------------+--------------+ | Period | Period Start | Period End | Max | Min | Avg | Sum | Count | Duration | Duration Start | Duration End | +--------+--------------+------------+-----+-----+-----+-----+-------+----------+----------------+--------------+

I appreciate help on this. thanks.

2016-02-26 00:00:52 -0500 received badge  Notable Question (source)
2016-02-25 02:24:43 -0500 received badge  Popular Question (source)
2016-02-25 00:39:21 -0500 commented answer Instance creation failing ( Block Device Mapping)

Yes as per the suggestion I've crossed checked from Cinder and Glance services logs. From those 2 services no log error.

For our Information, the logs are below.

Cinder

2016-02-25 01:37:58.630 19 INFO eventlet.wsgi.server [req-5dce23a6-bb0a-43d3-8186-4cfdd66dfb5b eda5

2016-02-25 00:32:15 -0500 commented answer Instance creation failing ( Block Device Mapping)

Launching from Boot from image. Yes value is creating perfectly.

2016-02-24 04:28:28 -0500 received badge  Supporter (source)
2016-02-23 08:33:47 -0500 answered a question Instance creation fails (Block Device Mapping)

Hi All

Even I am also facing same issue. But I checked cinder-volume running is running on single node ony. Can you help on this.

Nova Log is below.

2016-02-23 07:21:34.110 23 INFO nova.osapi_compute.wsgi.server [req-c1ab3b47-d2df-4364-b4fc-34d9cebb6a8e eda50140f7a84404af3db6c007e482b3 97bca548d2d04e7b85a5c1aeadc0e7cb - - -] 10.86.156.145 "GET /v2/97bca548d2d04e7b85a5c1aeadc0e7cb/extensions HTTP/1.1" status: 200 len: 22486 time: 2.4953480
/usr/lib64/python2.7/site-packages/sqlalchemy/engine/default.py:442: Warning: Incorrect datetime value: '2016-02-01 00:00:00+00:00' for column 'terminated_at' at row 1
  cursor.execute(statement, parameters)
/usr/lib64/python2.7/site-packages/sqlalchemy/engine/default.py:442: Warning: Incorrect datetime value: '2016-02-23 07:21:34+00:00' for column 'launched_at' at row 1
  cursor.execute(statement, parameters)
2016-02-23 07:21:34.537 23 INFO nova.osapi_compute.wsgi.server [req-6704e6f0-d0c5-4b07-acff-61aed9c24df8 eda50140f7a84404af3db6c007e482b3 97bca548d2d04e7b85a5c1aeadc0e7cb - - -] 10.86.156.145 "GET /v2/97bca548d2d04e7b85a5c1aeadc0e7cb/os-simple-tenant-usage?start=2016-02-01T00:00:00&end=2016-02-23T23:59:59&detailed=1 HTTP/1.1" status: 200 len: 217 time: 0.4085770
2016-02-23 07:21:34.593 23 INFO nova.osapi_compute.wsgi.server [req-eeacc08b-2aeb-40b6-8f57-195290416a22 eda50140f7a84404af3db6c007e482b3 97bca548d2d04e7b85a5c1aeadc0e7cb - - -] 10.86.156.145 "GET /v2/97bca548d2d04e7b85a5c1aeadc0e7cb/limits HTTP/1.1" status: 200 len: 711 time: 0.0513749
2016-02-23 07:22:09.529 25 INFO nova.osapi_compute.wsgi.server [req-292f7a33-d99a-4313-8605-6f8d6a199d7f eda50140f7a84404af3db6c007e482b3 97bca548d2d04e7b85a5c1aeadc0e7cb - - -] 10.86.156.145 "GET /v2/97bca548d2d04e7b85a5c1aeadc0e7cb/servers/detail?limit=21&project_id=97bca548d2d04e7b85a5c1aeadc0e7cb HTTP/1.1" status: 200 len: 2489 time: 1.5793769
2016-02-23 07:22:10.989 22 INFO nova.osapi_compute.wsgi.server [req-f3ffbef3-ba3a-4ff2-83ec-aa35a0ba24aa eda50140f7a84404af3db6c007e482b3 97bca548d2d04e7b85a5c1aeadc0e7cb - - -] 10.86.156.145 "GET /v2/97bca548d2d04e7b85a5c1aeadc0e7cb/flavors/detail HTTP/1.1" status: 200 len: 2297 time: 1.2844250
2016-02-23 07:22:19.252 23 INFO nova.osapi_compute.wsgi.server [req-e530c691-9ba9-448f-9d19-1c3e76859f3f eda50140f7a84404af3db6c007e482b3 97bca548d2d04e7b85a5c1aeadc0e7cb - - -] 10.86.156.145 "GET /v2/97bca548d2d04e7b85a5c1aeadc0e7cb/limits?reserved=1 HTTP/1.1" status: 200 len: 711 time: 0.0305040
2016-02-23 07:22:19.279 22 INFO nova.osapi_compute.wsgi.server [req-ea126104-ffd6-4c2a-85f0-4e2e45284929 eda50140f7a84404af3db6c007e482b3 97bca548d2d04e7b85a5c1aeadc0e7cb - - -] 10.86.156.145 "GET /v2/97bca548d2d04e7b85a5c1aeadc0e7cb/os-hypervisors/detail HTTP/1.1" status: 200 len: 1291 time: 0.0229180
2016-02-23 07:22:20.381 24 INFO nova.osapi_compute.wsgi.server [req-a66ff537-8c5f-4684-bff2-0506a0941f33 eda50140f7a84404af3db6c007e482b3 97bca548d2d04e7b85a5c1aeadc0e7cb - - -] 10.86.156.145 "GET /v2/97bca548d2d04e7b85a5c1aeadc0e7cb/extensions HTTP/1.1" status: 200 len: 22486 time: 1.0716231
2016-02-23 07:22:20.643 24 INFO nova.osapi_compute.wsgi.server [req-61b2657b-5bf0-462c-b9ad-1c7f8cc210e4 eda50140f7a84404af3db6c007e482b3 97bca548d2d04e7b85a5c1aeadc0e7cb - - -] 10.86.156.145 "GET /v2/97bca548d2d04e7b85a5c1aeadc0e7cb/os-hypervisors/detail HTTP/1.1" status: 200 len: 1291 time: 0.2494130
2016-02-23 07:22:20.699 24 INFO nova.osapi_compute.wsgi.server [req-dfae1eaa-4e6c-45b9-8222-c5203ebd36c4 eda50140f7a84404af3db6c007e482b3 97bca548d2d04e7b85a5c1aeadc0e7cb - - -] 10.86.156.145 "GET /v2/97bca548d2d04e7b85a5c1aeadc0e7cb/limits?reserved=1 HTTP/1.1" status: 200 len: 711 time: 0.0319870
2016-02-23 07:22:20.723 22 INFO nova.osapi_compute.wsgi.server [req-8c85f66d-8b58-473a-86c1-7ba346e98694 eda50140f7a84404af3db6c007e482b3 97bca548d2d04e7b85a5c1aeadc0e7cb - - -] 10.86.156.145 "GET /v2/97bca548d2d04e7b85a5c1aeadc0e7cb/os-hypervisors/detail HTTP/1.1" status: 200 len: 1291 time: 0.0200250
2016-02-23 07:30:12.380 22 INFO nova.osapi_compute.wsgi.server [req-cf564ea7-6bd1-4c99-88e7-db907fb14a5c eda50140f7a84404af3db6c007e482b3 97bca548d2d04e7b85a5c1aeadc0e7cb - - -] 10.86.156.145 "GET /v2/97bca548d2d04e7b85a5c1aeadc0e7cb/servers/e48ca233-3553-4a0a-82de-fb61f80fda8f HTTP/1.1" status: 200 len: 2486 time: 0.2452590
2016-02-23 07:30 ...
(more)
2016-02-23 08:33:47 -0500 commented question Instance creation failing ( Block Device Mapping)

Nova log is below.

2016-02-23 05:10:36.935 1 TRACE nova.openstack.common.periodic_task [u'Traceback (most recent call last):\n', u' File "/usr/lib/python2.7/site-packages/nova/conductor/manager.py", line 422, in _object_dispatch\n return getattr(target, method)(args, *kwargs)\n', u' File "/

2016-02-23 08:33:47 -0500 asked a question Instance creation failing ( Block Device Mapping)

Hi All.

I seek to install Oracle Openstack Kilo for HA.

I done all most all configuration as per the document says. But I am not able to spin of the instances from Dash_Board. I see below error.

Error: Failed to perform requested operation on instance "test06", the instance has an error status: Please try again later [Error: Build of instance e48ca233-3553-4a0a-82de-fb61f80fda8f aborted: Failure prepping block device.].

If anyone can help it would more help to me.