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-devel

Re: [Xen-devel] Many same managed domain

To: Masaki Kanno <kanno.masaki@xxxxxxxxxxxxxx>
Subject: Re: [Xen-devel] Many same managed domain
From: Daniel Berrange <berrange@xxxxxxxxxx>
Date: Tue, 24 Jul 2007 14:25:06 +0100
Cc: xen-devel@xxxxxxxxxxxxxxxxxxx
Delivery-date: Tue, 24 Jul 2007 06:23:01 -0700
Envelope-to: www-data@xxxxxxxxxxxxxxxxxx
In-reply-to: <9BC7CDA074E023kanno.masaki@xxxxxxxxxxxxxx>
List-help: <mailto:xen-devel-request@lists.xensource.com?subject=help>
List-id: Xen developer discussion <xen-devel.lists.xensource.com>
List-post: <mailto:xen-devel@lists.xensource.com>
List-subscribe: <http://lists.xensource.com/cgi-bin/mailman/listinfo/xen-devel>, <mailto:xen-devel-request@lists.xensource.com?subject=subscribe>
List-unsubscribe: <http://lists.xensource.com/cgi-bin/mailman/listinfo/xen-devel>, <mailto:xen-devel-request@lists.xensource.com?subject=unsubscribe>
References: <91C7CC1E6AF558kanno.masaki@xxxxxxxxxxxxxx> <20070722144609.GA22043@xxxxxxxxxx> <9BC7CDA074E023kanno.masaki@xxxxxxxxxxxxxx>
Reply-to: "Daniel P. Berrange" <berrange@xxxxxxxxxx>
Sender: xen-devel-bounces@xxxxxxxxxxxxxxxxxxx
User-agent: Mutt/1.4.1i
Yfrom: "Daniel P. Berrange" <berrange@xxxxxxxxxx>
On Tue, Jul 24, 2007 at 12:12:24PM +0900, Masaki Kanno wrote:
> 
> >On Sun, Jul 22, 2007 at 02:09:01PM +0900, Masaki Kanno wrote:
> >
> >No that would break backwards compatability for user who rely on Xen 
> >autogenerating the UUID. 
> >
> >In order to maintain back-compatability with existing use cases, the user
> >needs to be able to update the existing VM config with 'xm new' if the name
> >or UUID match, while preventing multiple VMs with same name. So the the 
> >rules 
> >when defining a new VM need to follow this logic
> >
> >  - 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
> 
> 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.

Dan,
-- 
|=- Red Hat, Engineering, Emerging Technologies, Boston.  +1 978 392 2496 -=|
|=-           Perl modules: http://search.cpan.org/~danberr/              -=|
|=-               Projects: http://freshmeat.net/~danielpb/               -=|
|=-  GnuPG: 7D3B9505   F3C9 553F A1DA 4AC2 5648 23C1 B3DF F742 7D3B 9505  -=| 

_______________________________________________
Xen-devel mailing list
Xen-devel@xxxxxxxxxxxxxxxxxxx
http://lists.xensource.com/xen-devel