[Openstack] MySQL connection gone away handling in OpenStack projects

2012-03-22 Thread Unmesh Gurjar
Hi, The current handling of the 'SQL server has gone away' is different across OpenStack projects (eg. Nova uses MySQLPingListener, whereas Glance retries the db operation to recover connection). I am curious to know if the fix implemented in https://review.openstack.org/5552 will be used

Re: [Openstack] [Nova] Unable to start nova-api

2013-02-05 Thread Unmesh Gurjar
Trinath, You probably have a wrong config setting. Please check the value of 'network_api_class' in your nova.conf and confirm that the module with the specified class exists. The default value of this parameter is nova.network.api.API, so you should expect class 'API' in nova/network/api.py of

Re: [Openstack] Nova.Scheduler TypeError: can't compare datetime.datetime to NoneType

2013-02-07 Thread Unmesh Gurjar
Greg, IMO, this qualifies as a bug. To debug what's causing this scenario is your case, I would suggest checking the database connection setting in nova.conf on your Compute Controller host. AFAIK, it either means Compute's status is not being updated (Compute service down) or its being updated

Re: [Openstack] [Glance] No Kernel_ID returned with glance add command

2013-02-21 Thread Unmesh Gurjar
Kazim, In any case, the command should have returned either a successful or failed response. It might be helpful if you paste the exact output of this command. To move forward, I would suggest having a look at the Glance API logs, which would indicate what is going wrong in your case. You might

Re: [Openstack] VM creation failure

2013-02-26 Thread Unmesh Gurjar
Javier, The stack trace you provided indicates that the allocate network call from Compute (to nova-network) timed out. I would suggest checking the nova-network logs, that might give some insight. Also, IMO, the create instance request is being served by Compute means the RabbitMQ is working.

Re: [Openstack] Cinder + Live migration

2013-04-17 Thread Unmesh Gurjar
Hi Paras, AFAIK, this should be possible in grizzly. Here is the related bug: https://bugs.launchpad.net/nova/+bug/1074054 -- Thanks Regards, Unmesh G. On Wed, Apr 17, 2013 at 10:04 PM, Paras pradhan pradhanpa...@gmail.comwrote: Hi, If we boot a instance from cinder volume. Is it

Re: [Openstack] problem in authenticating...

2013-04-23 Thread Unmesh Gurjar
Kamaill, I think that is caused because of the wrong HTTP header in the second curl command. It should be 'X-Auth-Token' instead of 'XX-Auth-Token'. Give it a try and get back if you have any issue. -Unmesh. On Tue, Apr 23, 2013 at 1:17 PM, Study Kamaill study.i...@yahoo.com wrote: THis is

Re: [Openstack] nova-network: how to remove

2013-04-26 Thread Unmesh Gurjar
Arindam, You can do it using 'nova-manage service disable --host hostname --service service' command. Similarly, you can enable the network service in controller node. -Unmesh. On Thu, Apr 25, 2013 at 9:16 PM, Arindam Choudhury arin...@live.com wrote: Hi, I mistakenly installed

Re: [Openstack] [Cinder] Loading cinder.conf

2013-07-15 Thread Unmesh Gurjar
Hi, AFAIK, there are no additional changes required (other than restarting the service so that it loads the new conf settings). Assuming you have done that, can you check what is the 'volume_driver' from the service start up logs? ~Unmesh. On Mon, Jul 15, 2013 at 10:44 AM, zan tosh

Re: [Openstack] Malformed Requests

2013-07-25 Thread Unmesh Gurjar
Hi Justin, Looking at the endpoints in the auth response (v2.0/tokens), probably the URL should be http://openstack.cloud.fandingo.org:8776/v1/4457698fa26d4ce59f1811e91521f6c4/volumes/detail instead of http://openstack.cloud.kerrygroup.net:8776/v1/4457698fa26d4ce59f1811e91521f6c4/volumes/detail.