From: yamamoto@valinux.co.jp (YAMAMOTO Takashi)
To: Jonathan.Ludlam@eu.citrix.com
Cc: xen-devel@lists.xensource.com
Subject: Re: XCP: python SR plugin questions
Date: Thu, 20 May 2010 10:46:01 +0900 (JST) [thread overview]
Message-ID: <20100520014601.2E35B71901@kuma.localdomain> (raw)
In-Reply-To: Your message of "Wed, 19 May 2010 11:18:40 +0100" <6CC2BAAB-E1DC-4288-BF7E-A9355591B776@eu.citrix.com>
hi,
>>>> i'm writing a python sr plugin for our product and have a few questions.
>>>>
>>>> - our product has 32-bit id, not uuid, for each volumes, which i want to map
>>>> to xcp's vdi. i generate name-based uuid from the 32-bit id in sr.scan and
>>>> vdi.create. is this a reasonable approach?
>>>>
>>>
>>> You can use the 'location' field in the VDI to contain your 32 bit id - then the uuid is irrelevant. I'd like to move more of the storage backends in this direction - currently I believe only the ISO SR does it this way.
>>
>> ok. in that case, xapi generates random uuids for me, right?
>>
>
> Actually the backends are responsible for creating the uuid.
then, what is vdi_create's uuid argument for?
(my current plugin code simply ignores the argument and
return generated uuid via vdi_info. is it ok?)
our product itself doesn't provide uuids at all. so someone should
generate ones so that xapi can use them.
i plan to make my sr plugin generate name-based uuid from our product's
32-bit id. does it sound ok for you?
i'm not sure how your suggestion to use vdi location is related to
the uuid issue. can you please elaborate a bit?
YAMAMOTO Takashi
next prev parent reply other threads:[~2010-05-20 1:46 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-05-19 2:35 XCP: python SR plugin questions YAMAMOTO Takashi
2010-05-19 9:00 ` Jonathan Ludlam
2010-05-19 9:07 ` YAMAMOTO Takashi
2010-05-19 10:18 ` Jonathan Ludlam
2010-05-20 1:46 ` YAMAMOTO Takashi [this message]
2010-05-20 8:49 ` Jonathan Ludlam
2010-05-20 9:12 ` YAMAMOTO Takashi
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20100520014601.2E35B71901@kuma.localdomain \
--to=yamamoto@valinux.co.jp \
--cc=Jonathan.Ludlam@eu.citrix.com \
--cc=xen-devel@lists.xensource.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).