Ask Your Question

gans-developer's profile - activity

2016-09-25 22:53:03 -0500 commented answer What is the difference between root_gb, disk_gb and ephemeral_gb

Thanks a lot for taking time to answer !!!

2016-09-25 22:52:27 -0500 received badge  Scholar (source)
2016-09-25 22:52:24 -0500 received badge  Supporter (source)
2016-09-24 01:32:37 -0500 received badge  Famous Question (source)
2016-09-23 05:05:17 -0500 received badge  Enthusiast
2016-09-23 01:58:31 -0500 received badge  Notable Question (source)
2016-09-23 00:26:03 -0500 received badge  Popular Question (source)
2016-09-22 23:16:14 -0500 asked a question What is the difference between root_gb, disk_gb and ephemeral_gb

I am using ceilometer to get notification data for compute.instance.* events.While configuring traits in event_definitions.yml file, i came across 3 different attributes for storage/size of vm: disk_gb, root_gb, ephemeral_gb.

I was not able to find details or significant difference between these attributes.

Someone please help me with why should i keep all the three in my reports.

[update1] Here is the link where i got the details of attributes to configure.

                        http://paste.openstack.org/show/54140/
2016-09-20 23:11:01 -0500 commented question openstack ansible fails to install additional neutron pip packages

Launch a VM and do what? Question is how to install additional pip packages?

2014-12-09 20:22:09 -0500 received badge  Famous Question (source)
2014-08-07 04:14:57 -0500 received badge  Notable Question (source)
2014-07-24 05:53:58 -0500 received badge  Popular Question (source)
2014-07-11 03:52:11 -0500 received badge  Taxonomist
2013-11-13 04:16:59 -0500 answered a question Found a potential bug while setting up multiple cinder-volume instances on single cinder node

Please ignore this question. My code was not returing the volume backend name correctly in the update_volume_stats function and it was causing the whole trouble.

2013-11-13 04:16:45 -0500 answered a question Found a potential bug while setting up multiple cinder-volume instances on single cinder node

Please ignore this question. My code was not returing the volume backend name correctly in the update_volume_stats function and it was causing the whole trouble.

2013-11-11 09:53:27 -0500 answered a question Found a potential bug while setting up multiple cinder-volume instances on single cinder node

Is this a bug or am i in a wrong way?

2013-11-08 06:41:15 -0500 asked a question Found a potential bug while setting up multiple cinder-volume instances on single cinder node

I was trying to setup multiple cinder-volume instances on a single node setup.I edited the cinder.conf file as per the instructions given in the openstack docs for multi-backend cinder.

http://docs.openstack.org/admin-guide...

I setup two backends and was able to see both the backend hosts in cinder service-list.

PART 1 : I tried to create a volume using the volume-type(configures for the backends), but it failed saying "No valid host was found". I tried to debug the code and got the point where the process was stalling.

cinder/openstack/common/scheduler/filter.py : get_filtered_objects :

for filter_cls in filter_classes: objs = filter_cls().filter_all(objs, filter_properties) return list(objs)

In these lines of code, the objs will contain the list of hosts as per the filter classes. In my case , the code was able to find the list of host for one of the classes in the first iteration only and in second and third iteration the list was empty.As the return is after the loop is over , it was always sending the empty list and hence the error : "No valid host found"

I changed the code to this and it was then returning the list of hosts. Changed code : for filter_cls in filter_classes: objs = filter_cls().filter_all(objs, filter_properties) if objs: return list(objs) return list(objs)

PART 2 : After making the above changes , i tried to create the volume using one of the volume-type and got success. Then i tried to use the other volume-type to create the volume , but it used the other host and not the host associated with this volume-type.

I went through the logs and found that it was discovering both the hosts in the file cinder/cinder/scheduler : filter_scheduler.py : _get_weighted_candidates : line 222

after getting the hosts list it was choosing the first host in the list in file cinder/cinder/scheduler : filter_scheduler.py : _schedule : line 239

My doubts: ==> was the host list filtered as per the volume-type provided during the create volume process? ==> Why we are using the first host from the "weighed_hosts" list?

2013-11-08 06:41:15 -0500 answered a question Found a potential bug while setting up multiple cinder-volume instances on single cinder node

I was trying to setup multiple cinder-volume instances on a single node setup.I edited the cinder.conf file as per the instructions given in the openstack docs for multi-backend cinder.

http://docs.openstack.org/admin-guide...

I setup two backends and was able to see both the backend hosts in cinder service-list.

PART 1 : I tried to create a volume using the volume-type(configures for the backends), but it failed saying "No valid host was found". I tried to debug the code and got the point where the process was stalling.

cinder/openstack/common/scheduler/filter.py : get_filtered_objects :

for filter_cls in filter_classes: objs = filter_cls().filter_all(objs, filter_properties) return list(objs)

In these lines of code, the objs will contain the list of hosts as per the filter classes. In my case , the code was able to find the list of host for one of the classes in the first iteration only and in second and third iteration the list was empty.As the return is after the loop is over , it was always sending the empty list and hence the error : "No valid host found"

I changed the code to this and it was then returning the list of hosts. Changed code : for filter_cls in filter_classes: objs = filter_cls().filter_all(objs, filter_properties) if objs: return list(objs) return list(objs)

PART 2 : After making the above changes , i tried to create the volume using one of the volume-type and got success. Then i tried to use the other volume-type to create the volume , but it used the other host and not the host associated with this volume-type.

I went through the logs and found that it was discovering both the hosts in the file cinder/cinder/scheduler : filter_scheduler.py : _get_weighted_candidates : line 222

after getting the hosts list it was choosing the first host in the list in file cinder/cinder/scheduler : filter_scheduler.py : _schedule : line 239

My doubts: ==> was the host list filtered as per the volume-type provided during the create volume process? ==> Why we are using the first host from the "weighed_hosts" list?

Please help me out here.

2013-09-12 13:14:10 -0500 received badge  Necromancer (source)
2013-09-12 13:14:10 -0500 received badge  Teacher (source)
2013-08-30 02:02:36 -0500 commented answer Cinder : Volume creation Issue

Thanks, will take care next time :)

2013-08-29 09:57:00 -0500 answered a question Cinder : Volume creation Issue

Check the cinder-volume log and trace the error.

2013-08-29 05:20:56 -0500 answered a question What is the quickest method for deploying a multi-node install?

I have a multi node setup for which i used Devstack.

Please find details at this : http://networkstatic.net/openstack-multi-node-devstack-nova-network-tutorial/

2013-08-20 00:35:30 -0500 commented answer Error installing devstack grizzly

I tried with 12.04 but getting the same error. I had one old distribution of devstack which worked fine with the installation process .