Dan Smith wrote:
HE> I looked a bit through the Migration Profile and found a
class
HE> that I suggest to use for this functionality. That's the
HE> description of this class: "CIM_VirtualSystemMigrationSettingData
HE> defines the parameters to control a virtual system migration
HE> implementation, as managed by a
HE> CIM_VirtualSystemMigrationService. It is expected that a migration
HE> implementation will subclass this class to add
HE> implementation-specific migration options." An instance of this
HE> class is transported to all CheckIsVSMigratable...() and
HE> MigrateVSTo...() via the MigrationSettingData parameter. So we
HE> stay absolutely conform to the Migration Profile. The Xen and KVM
HE> subclasses can check properties, that are well know to cause
HE> migration problems.
This is what I did. I extended Xen_MigrationSettingData to include
the CheckParameters[] property, which is what I pass to the check
program. There are no additional arguments to either of the CIM
methods, and this extra property of the SettingData is optional.
Sorry Dan, either I'm working too long or I should go to an optician and
let me give "very strong" glasses. I was under the impression that
MigrationService itself was extended by CheckParameters. So, I'm fine
with your integration into the model.
--
Regards
Heidi Eckhart
Software Engineer
IBM Linux Technology Center - Open Hypervisor