Re: [Xen-devel] Many same managed domain

[Daniel 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