[Libvirt-cim] about 'CreationClassName' key in VirtualSystemIsMigratableToHost method

Dan Smith danms at us.ibm.com
Wed Jan 23 17:04:18 UTC 2008


GY> If the "Name" key is set "Wrong", it will report expected error
GY> "Missing key (Name) in ComputerSystem".  Then does the other key
GY> "CreationClassName" need to verify also? At now, either wrong key
GY> name or wrong value of CreationClassName, such as
GY> "CreationClassName!@#$$$" instead of "CreationClassName",it can
GY> still return expected result. So is it a provider's bug?  Do we
GY> need to add some verification of "CreationClassName" key in
GY> provider code below?

I think this is probably a reasonable instance where such a check
actually adds value.  Assuming you have two domains called "meep", one
a KVM domain and another a Xen domain, you could potentially pass a
reference of the Xen one to the KVM_VirtualSystemMigrationService.
This would result in moving a different domain than intended.
Granted, this would be a client error, of course, but it seems like
something we could easily help prevent from the provider side.

Thanks!

-- 
Dan Smith
IBM Linux Technology Center
Open Hypervisor Team
email: danms at us.ibm.com
-------------- next part --------------
A non-text attachment was scrubbed...
Name: not available
Type: application/pgp-signature
Size: 188 bytes
Desc: not available
URL: <http://listman.redhat.com/archives/libvirt-cim/attachments/20080123/f6b5ffac/attachment.sig>


More information about the Libvirt-cim mailing list