WARNING - OLD ARCHIVES

This is an archived copy of the Xen.org mailing list, which we have preserved to ensure that existing links to archives are not broken. The live archive, which contains the latest emails, can be found at http://lists.xen.org/
   
 
 
Xen 
 
Home Products Support Community News
 
   
 

xen-api

[Xen-API] xapi accepting commands before being fully up

To: "xen-api@xxxxxxxxxxxxxxxxxxx" <xen-api@xxxxxxxxxxxxxxxxxxx>
Subject: [Xen-API] xapi accepting commands before being fully up
From: George Dunlap <George.Dunlap@xxxxxxxxxxxxx>
Date: Mon, 12 Jul 2010 15:34:53 +0100
Delivery-date: Mon, 12 Jul 2010 07:33:18 -0700
Envelope-to: www-data@xxxxxxxxxxxxxxxxxxx
List-help: <mailto:xen-api-request@lists.xensource.com?subject=help>
List-id: Discussion of API issues surrounding Xen <xen-api.lists.xensource.com>
List-post: <mailto:xen-api@lists.xensource.com>
List-subscribe: <http://lists.xensource.com/mailman/listinfo/xen-api>, <mailto:xen-api-request@lists.xensource.com?subject=subscribe>
List-unsubscribe: <http://lists.xensource.com/mailman/listinfo/xen-api>, <mailto:xen-api-request@lists.xensource.com?subject=unsubscribe>
Sender: xen-api-bounces@xxxxxxxxxxxxxxxxxxx
User-agent: Mozilla/5.0 (X11; U; Linux i686; en-US; rv:1.9.1.10) Gecko/20100527 Thunderbird/3.0.5
It seems that xapi is up and accepting commands before everything is actually ready yet. I have a script that will wait for a host to boot by pinging and then testing listening on the ssh port; when it succeeds, the host should be up and ready.

However, if I write a command that runs that script, and then immediately tries to start a VM on that host, I get this error message:
---
There are no suitable hosts to start this VM on.
The following table provides per-host reasons for why the VM could not be started:

exile : Cannot start here [Host disabled (use 'xe host-enable' to re-enable)]
---

Subsequent attempts succeed.

It seems like xapi should either wait until all local hosts are up before accepting vm-start commands, or if they get a command that depends on certain hosts, it should wait for them to be enabled.

I think if that's not easy to do, maybe a "wait-for-host-to-be-initialized" command... :-)

 -George

_______________________________________________
xen-api mailing list
xen-api@xxxxxxxxxxxxxxxxxxx
http://lists.xensource.com/mailman/listinfo/xen-api

<Prev in Thread] Current Thread [Next in Thread>