[openstack-dev] [Nova] Changing the default value of xenapi_disable_agent

Andrew Laski andrew.laski at rackspace.com
Thu May 9 20:41:35 UTC 2013


On 05/09/13 at 05:35pm, John Garbutt wrote:
>Hi,
>
>I have a patch cooking here:
>https://review.openstack.org/#/c/28665/
>
>Below is an example of the confusion caused by the current default.
>Basically, I would like to change the XenAPI driver so it defaults to
>not waiting for the XenAPI Agent to be present during the server boot
>process.
>
>Later in Havana I am looking at moving the XenAPI driver from relying
>so much on the XenAPI agent, as part of this blueprint:
>https://blueprints.launchpad.net/nova/+spec/xenapi-guest-agent-cloud-init-interop
>
>Just trying to work out the best way not to confuse our users. In this
>case, I think the correct answer is to change the default. Any
>thoughts?

I think users are going to be confused either way, because changing the 
default means some features may not work by default.  But given that 
there's a move towards cloud-init and config-drive over the agent I 
think it makes sense for a deployer to choose to use the agent, rather 
than having to turn it off.  


>
>John
>
>---------- Forwarded message ----------
>From: Gonzalo Alvarez <gonzaloab at gmail.com>
>Date: 9 May 2013 11:38
>Subject: [Openstack] Failed to query agent version
>To: OpenStack <openstack at lists.launchpad.net>
>
>
>Hi all,
>
>    I've managed to install OpenStack (Version 2012.1.1-18) on top of
>a XenServer installation. Instances are created fine, but it takes
>really long for Openstack to realize that the instance is up and
>running. In the nova-compute.log I see the following messages:
>
>2013-05-09 05:19:47 DEBUG nova.virt.xenapi_conn [-] Got exception:
>['XENAPI_PLUGIN_FAILURE', 'version', 'PluginError', 'TIMEOUT: No
>response from agent within 30 seconds.'] from (pid=3047)
>_unwrap_plugin_exceptions
>/usr/lib/python2.7/dist-packages/nova/virt/xenapi_conn.py:612
>2013-05-09 05:19:47 ERROR nova.virt.xenapi.vmops
>[req-80868dbf-a0ec-4e5c-ba1c-40073407a69e
>e2d41ace30d1492ebb24edfbf30b9089 136c4d2c8f3e4c74a0a4a4ef0e45a901]
>TIMEOUT: The call to version timed out. VM
>id=a1978a21-7598-4d5e-984b-a9ca858f7237; args={'path': '', 'dom_id':
>'4', 'id': '957d7359-1632-4b38-bf19-8bfd0d45aca5', 'host_uuid':
>'c38359bb-7a82-ac2b-0ee6-4a6dd68c5285'}
>2013-05-09 05:19:47 ERROR nova.virt.xenapi.vmops
>[req-80868dbf-a0ec-4e5c-ba1c-40073407a69e
>e2d41ace30d1492ebb24edfbf30b9089 136c4d2c8f3e4c74a0a4a4ef0e45a901]
>Failed to query agent version: {'message': 'TIMEOUT: No response from
>agent within 30 seconds.', 'returncode': 'timeout'}
>
>These three messages are repeated 5 times, until I get these messages:
>
>2013-05-09 05:24:20 DEBUG nova.compute.manager
>[req-80868dbf-a0ec-4e5c-ba1c-40073407a69e
>e2d41ace30d1492ebb24edfbf30b9089 136c4d2c8f3e4c74a0a4a4ef0e45a901]
>[instance: a1978a21-7598-4d5e-984b-a9ca858f7237] Checking state from
>(pid=3047) _get_power_state
>/usr/lib/python2.7/dist-packages/nova/compute/manager.py:272
>2013-05-09 05:24:20 INFO nova.virt.xenapi.vm_utils
>[req-80868dbf-a0ec-4e5c-ba1c-40073407a69e
>e2d41ace30d1492ebb24edfbf30b9089 136c4d2c8f3e4c74a0a4a4ef0e45a901]
>(VM_UTILS) xenserver vm state -> |Running|
>2013-05-09 05:24:20 INFO nova.virt.xenapi.vm_utils
>[req-80868dbf-a0ec-4e5c-ba1c-40073407a69e
>e2d41ace30d1492ebb24edfbf30b9089 136c4d2c8f3e4c74a0a4a4ef0e45a901]
>(VM_UTILS) xenapi power_state -> |1|
>
>And then the dashboard properly shows the instance as running. But the
>instance was up and running long ago. The instace takes about 30
>seconds until command prompt, but OpenStack waits about 4 minutes to
>mark it as 'Running'.
>
>Is there any way to fix this?
>
>Thanks in advance.
>
>Regards,
>Gonzalo Alvarez.
>---
>GonzaloAlvarez.es
>Ponzano 80, 6º 6 - 28003 - Madrid
>Mail | Facebook | Linkedin
>Tel: +34 678 252 458
>
>_______________________________________________
>Mailing list: https://launchpad.net/~openstack
>Post to     : openstack at lists.launchpad.net
>Unsubscribe : https://launchpad.net/~openstack
>More help   : https://help.launchpad.net/ListHelp
>
>_______________________________________________
>OpenStack-dev mailing list
>OpenStack-dev at lists.openstack.org
>http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev



More information about the OpenStack-dev mailing list