Ask Your Question

Anshul Gangwar's profile - activity

2014-11-16 00:09:49 -0500 received badge  Good Question (source)
2014-10-29 09:20:13 -0500 commented question ceilometer and instance snapshots/glance images

I am not using ceilometer anymore so I am not sure whether this problem still exists or not

2014-09-11 01:43:33 -0500 received badge  Nice Question (source)
2013-11-13 22:39:03 -0500 received badge  Famous Question (source)
2013-10-22 01:31:50 -0500 received badge  Famous Question (source)
2013-10-16 14:34:47 -0500 received badge  Famous Question (source)
2013-09-20 08:29:48 -0500 received badge  Good Question (source)
2013-09-19 15:23:34 -0500 received badge  Notable Question (source)
2013-09-07 10:37:22 -0500 received badge  Notable Question (source)
2013-07-28 15:17:03 -0500 received badge  Popular Question (source)
2013-07-11 05:20:17 -0500 asked a question ceilometer and instance snapshots/glance images

I have created instance snapshot. When I am listing them through ceilometer API call, then I am getting userId: null for them.

I remember I used to get userId(who have created that snapshot) in response but I am not getting it now.

Is there any change in behaviour? or there is any extra setting required in configuration?

API call :

response :

       "resource_id": "52f814e5-fa6b-4a3c-acb7-80d13ced88da",
       "project_id": "f57362577d3b4c7c82b6bc713d0dcc25",
       "user_id": null,
           "status": "active",
           "name": "nanovmsnap",
           "deleted": "False",
           "container_format": "ami",
           "created_at": "2013-07-09T09:43:47",
           "disk_format": "ami",
           "updated_at": "2013-07-09T09:44:08",
           "protected": "False",
           "checksum": "5d8fa241f393bb8ef6eea6576671a187",
           "min_disk": "0",
           "is_public": "False",
           "deleted_at": "None",
           "min_ram": "0",
           "size": "9830400"
2013-07-08 23:02:56 -0500 received badge  Popular Question (source)
2013-07-03 06:56:12 -0500 received badge  Notable Question (source)
2013-06-24 23:59:37 -0500 asked a question ceilometer not getting nova notifications

I am not getting disk.root.size meter notifications from nova to ceilometer. I am getting all ther pollster meters but not notification meters.

Do I need to add any cron job like cinder to get notifications?

I am using devstack and below are the contents of my nova.conf.

firewall_driver = nova.virt.libvirt.firewall.IptablesFirewallDriver
compute_driver = libvirt.LibvirtDriver
flat_interface = eth0
flat_network_bridge = br100
vlan_interface = eth0
public_interface = br100
network_manager =
glance_api_servers =
rabbit_password = freebsd
rabbit_host = localhost
rpc_backend = nova.openstack.common.rpc.impl_kombu
ec2_dmz_host =
vncserver_proxyclient_address =
vncserver_listen =
vnc_enabled = true
xvpvncproxy_base_url =
novncproxy_base_url =
notification_driver = nova.openstack.common.notifier.rpc_notifier,ceilometer.compute.nova_notifier
instance_usage_audit_period = hour
instance_usage_audit = True
logging_context_format_string = %(asctime)s.%(msecs)03d %(levelname)s %(name)s %(request_id)s %(user_name)s %(project_name)s] %(instance)s%(message)s
use_syslog = True
instances_path = /opt/stack/data/nova/instances
lock_path = /opt/stack/data/nova
state_path = /opt/stack/data/nova
volume_api_class = nova.volume.cinder.API
enabled_apis = ec2,osapi_compute,metadata
instance_name_template = instance-%08x
libvirt_cpu_mode = none
libvirt_type = qemu
sql_connection = mysql://root:freebsd@localhost/nova?charset=utf8
my_ip =
osapi_compute_extension = nova.api.openstack.compute.contrib.standard_extensions
s3_port = 3333
s3_host =
default_floating_pool = public
fixed_range =
force_dhcp_release = True
dhcpbridge_flagfile = /etc/nova/nova.conf
2013-06-21 05:29:18 -0500 received badge  Famous Question (source)
2013-06-18 22:34:00 -0500 received badge  Popular Question (source)
2013-06-16 23:43:17 -0500 received badge  Editor (source)
2013-06-14 22:48:56 -0500 received badge  Nice Question (source)
2013-06-14 11:44:22 -0500 asked a question how to give security group in REST json request to create server

I am trying to create instance from REST client. I want to give security group in json request so that the instance gets created in some specified security group. I didn't find any document regarding this. I have tried giving security_group paramater as "server": {"name": "teesra", "imageRef": "082aa3ea-26dc-44bd-89db-c540e202bfce", "flavorRef": "42", "key_name": "firstkeypair" } I have tried some other ways also

"server": {"name": "teesra", "imageRef": "082aa3ea-26dc-44bd-89db-c540e202bfce", "flavorRef": "42", "key_name": "firstkeypair", "security_groups": [{"name": "default" } ] }


"server": {"name": "teesra", "imageRef": "082aa3ea-26dc-44bd-89db-c540e202bfce", "flavorRef": "42", "key_name": "firstkeypair", "security_group": "default" }

but all this is resulting in some error.

What is the correct way to give security groups(multiple ) in json request?

[edit] : It seems like other parameter, which specifies the network(quantum) is missing. How can I give that? I am not able to deploy instance without giving network if quantum is enabled.

2013-06-13 08:26:44 -0500 received badge  Student (source)
2013-06-07 09:09:03 -0500 received badge  Notable Question (source)
2013-06-03 00:46:59 -0500 received badge  Popular Question (source)
2013-06-01 11:03:43 -0500 asked a question not getting cinder volume meters/resources from ceilometer

I have created the openstack setup with devstack. I have created the volumes and instances. When I am listing resources using ;

then I am getting only instnaces not volumes. Similarly I am not getting any meters.

I tried setting


in cinder.conf and restarting cinder-volume service and ceilometer-collector service.

Still I am not getting any volume related meters. Neither they are mentioned in resources.

In c-vol screen logs I can see below kind of logs when creating and deleting volumes.

f4-8ba8-8cdac08c7b21', 'project_id': u'39587e1865d14ea991b4ddf82c1dc1ab', 'read_deleted': u'no', 'tenant': u'39587e1865d14ea991b4ddf82c1dc1ab'}
2013-05-31 16:54:24     INFO [cinder.volume.manager] volume volume-147adb04-be41-4949-9fbf-52c871593de4: deleting
2013-05-31 16:54:24    DEBUG [cinder.openstack.common.rpc.amqp] Sending volume.delete.start on
2013-05-31 16:54:24    DEBUG [cinder.openstack.common.rpc.amqp] UNIQUE_ID is fd2593f309ca45579955afa7eb20d6ca.
2013-05-31 16:54:24     INFO [cinder.volume.manager] Clear capabilities