From: Jim Fehlig <jfehlig@novell.com>
To: xen-devel@lists.xensource.com
Subject: Re: Many same managed domain
Date: Tue, 24 Jul 2007 18:16:57 -0600 [thread overview]
Message-ID: <46A69679.50908@novell.com> (raw)
In-Reply-To: <9BC7CDA074E023kanno.masaki@jp.fujitsu. com> 20070724132506.GB23597@redhat.com
Daniel Berrange wrote:
[snip]
>> Thanks for your explanation.
>> I have a question to your logic. I think that the logic need a VM
>> name check when no VM with same UUID exists. Am I right?
>>
>> - If the UUID is not specified
>> - If a VM with same name exists
>> => Update the config for that existing VM
>> - Else no vm with same name exists
>> => Define a brand new VM with auto-generated UUID
>> - Else UUID is specified
>> - If a VM with same UUID exists
>> - If name is different
>> => Error
>> - Else if name is same
>> => Update the config for that existing VM
>> - Else no VM with same UUID exists
>> - => Define a branch new VM with that name
>> + - If name is different
>> + => Define a branch new VM with that name
>> + - Else if name is same
>> + => Error
>>
>
> Yes you are correct - if UUID does not clash we still need to check for
> a VM with same name, but different UUID.
>
As a side note, Xen API allows for domains with same name - in spec at
least :-).
((VM ref) Set) VM.get_by_name_label (session_id s, string label)
Return Type: (VM ref) Set
references to objects with match names
Jim
next prev parent reply other threads:[~2007-07-25 0:16 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-07-22 5:09 Many same managed domain Masaki Kanno
2007-07-22 10:30 ` Mats Petersson
2007-07-24 2:36 ` Masaki Kanno
2007-07-22 14:46 ` Daniel P. Berrange
2007-07-22 22:20 ` Mats Petersson
2007-07-24 3:12 ` Masaki Kanno
2007-07-24 13:25 ` Daniel Berrange
2007-07-24 14:47 ` Masaki Kanno
[not found] ` <9BC7CDA074E023kanno.masaki@jp.fujitsu. com>
2007-07-25 0:16 ` Jim Fehlig [this message]
2007-07-25 7:16 ` Masaki Kanno
2007-07-25 13:23 ` Daniel P. Berrange
2007-07-26 17:20 ` Jim Fehlig
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=46A69679.50908@novell.com \
--to=jfehlig@novell.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.