Mailing List Archive: status of xen api

Hello,

I've been developing an application for managing VMs in Perl, using the
Xen API as described in docs/xen-api.

My current version of Xen is bf8eacda088f, "Added tag 3.1.2-rc1 for
changeset 3855356c701d623daf2e8bef13dd4471f a9b3c91".

However, I'm finding a lot of dificulties:

* Some methods are still not implemented, like VM.name_description, but
those aren't very important.

* I can't get the VDIs for a VBD (nor the VDIs for a SR). How am I
supposed to get the backend of a VM's vbd?

If I call the VBD.get_VDI, I get an empty value for the ref
(communication attached).

* my network object has no PIFs, is this normal?

* In an older version of Xend (3.0.3), the host.get_log didn't escape
the log correctly. Is this fixed? I can't reproduce on my host, but it
could be something missing in my log.

Is there any documentation about the correct procedure and values for:

1. creating a VM, vbd or a vif;
2. attaching/detaching vbds/vifs from VMs.

Thank you for your help.

Regards,
Luciano Rocha

--
lfr
0/0

On Fri, Oct 26, 2007 at 03:53:02PM +0100, Luciano Rocha wrote:
> If I call the VBD.get_VDI, I get an empty value for the ref
> (communication attached).

The communication:

POST / HTTP/1.1
TE: deflate,gzip;q=0.3
Connection: TE, close
Host: localhost:9363
User-Agent: XenAPI/0.1
Content-Length: 285
Content-Type: text/xml

<?xml version="1.0" encoding="us-ascii"?><methodCall><methodName>VBD.get_VDI</methodName><params><param><value><string>0bfc383e-7fe7-e11b-5285-8a06d03277f6</string></value></param><param><value><string>1f211a23-83ce-94c3-b17e-cf48e5987760</string></value></param></params></methodCall>

HTTP/1.1 200 OK
Server: BaseHTTP/0.3 Python/2.5
Date: Fri, 26 Oct 2007 14:36:34 GMT
Content-Type: text/xml
Content-Length: 277

<?xml version='1.0'?>
<methodResponse>
<params>
<param>
<value><struct>
<member>
<name>Status</name>
<value><string>Success</string></value>
</member>
<member>
<name>Value</name>
<value><string></string></value>
</member>
</struct></value>
</param>
</params>
</methodResponse>

--
lfr
0/0