From: yamamoto@valinux.co.jp (YAMAMOTO Takashi)
To: xen-devel@lists.xensource.com
Subject: XCP: python SR plugin questions
Date: Wed, 19 May 2010 11:35:08 +0900 (JST) [thread overview]
Message-ID: <20100519023508.45D5570EF3@kuma.localdomain> (raw)
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?
- how can i get name-label specified by "xe vdi-create" in my vdi.create?
i want to pass it to our product.
if you are intersted, the "our product" is found at
http://sourceforge.net/projects/vastsky/
YAMAMOTO Takashi
next reply other threads:[~2010-05-19 2:35 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-05-19 2:35 YAMAMOTO Takashi [this message]
2010-05-19 9:00 ` XCP: python SR plugin questions Jonathan Ludlam
2010-05-19 9:07 ` YAMAMOTO Takashi
2010-05-19 10:18 ` Jonathan Ludlam
2010-05-20 1:46 ` YAMAMOTO Takashi
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=20100519023508.45D5570EF3@kuma.localdomain \
--to=yamamoto@valinux.co.jp \
--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).