[PATCH] html: Added additional classes to cimv216-interop.mof
# HG changeset patch # User Heidi Eckhart <heidieck@linux.vnet.ibm.com> # Date 1196935599 -3600 # Node ID 30269254841ceed6a250ea2b714c594fa30cc19e # Parent ba4bc35f508573c53e4303ce2e7a9b5299b95f38 html: Added additional classes to cimv216-interop.mof These additional classes are necessary to register Xen/KVM ComputerSystem and HostSystem classes to interop. Otherwise Pegasus refuses the registration. Signed-off-by: Heidi Eckhart <heidieck@linux.vnet.ibm.com> diff -r ba4bc35f5085 -r 30269254841c doc/libvirt-cim.html --- a/doc/libvirt-cim.html Thu Dec 06 11:06:38 2007 +0100 +++ b/doc/libvirt-cim.html Thu Dec 06 11:06:39 2007 +0100 @@ -300,6 +300,11 @@ below:</p> #pragma include ("qualifiers.mof")<br/> #pragma include ("qualifiers_optional.mof")<br/> #pragma include ("Core/CIM_ManagedElement.mof")<br/> +#pragma include ("Core/CIM_ManagedSystemElement.mof")<br/> +#pragma include ("Core/CIM_LogicalElement.mof")<br/> +#pragma include ("Core/CIM_EnabledLogicalElement.mof")<br/> +#pragma include ("Core/CIM_System.mof")<br/> +#pragma include ("System/CIM_ComputerSystem.mof")<br/> #pragma include ("Interop/CIM_RegisteredProfile.mof")<br/> #pragma include ("Interop/CIM_RegisteredSubProfile.mof")<br/> #pragma include ("Core/CIM_Dependency.mof")<br/>
Heidi Eckhart wrote:
# HG changeset patch # User Heidi Eckhart <heidieck@linux.vnet.ibm.com> # Date 1196935599 -3600 # Node ID 30269254841ceed6a250ea2b714c594fa30cc19e # Parent ba4bc35f508573c53e4303ce2e7a9b5299b95f38 html: Added additional classes to cimv216-interop.mof
These additional classes are necessary to register Xen/KVM ComputerSystem and HostSystem classes to interop. Otherwise Pegasus refuses the registration. Signed-off-by: Heidi Eckhart <heidieck@linux.vnet.ibm.com>
diff -r ba4bc35f5085 -r 30269254841c doc/libvirt-cim.html --- a/doc/libvirt-cim.html Thu Dec 06 11:06:38 2007 +0100 +++ b/doc/libvirt-cim.html Thu Dec 06 11:06:39 2007 +0100 @@ -300,6 +300,11 @@ below:</p> #pragma include ("qualifiers.mof")<br/> #pragma include ("qualifiers_optional.mof")<br/> #pragma include ("Core/CIM_ManagedElement.mof")<br/> +#pragma include ("Core/CIM_ManagedSystemElement.mof")<br/> +#pragma include ("Core/CIM_LogicalElement.mof")<br/> +#pragma include ("Core/CIM_EnabledLogicalElement.mof")<br/> +#pragma include ("Core/CIM_System.mof")<br/> +#pragma include ("System/CIM_ComputerSystem.mof")<br/> #pragma include ("Interop/CIM_RegisteredProfile.mof")<br/> #pragma include ("Interop/CIM_RegisteredSubProfile.mof")<br/> #pragma include ("Core/CIM_Dependency.mof")<br/>
Looks syntactically sound. I don't recognize a couple of those classes as dual-namespace ones, but I'm not going to second guess our CIM Compliance Officer on that. :) +1 -- -Jay
Jay Gagnon wrote:
--- a/doc/libvirt-cim.html Thu Dec 06 11:06:38 2007 +0100 +++ b/doc/libvirt-cim.html Thu Dec 06 11:06:39 2007 +0100 @@ -300,6 +300,11 @@ below:</p> #pragma include ("qualifiers.mof")<br/> #pragma include ("qualifiers_optional.mof")<br/> #pragma include ("Core/CIM_ManagedElement.mof")<br/> +#pragma include ("Core/CIM_ManagedSystemElement.mof")<br/> +#pragma include ("Core/CIM_LogicalElement.mof")<br/> +#pragma include ("Core/CIM_EnabledLogicalElement.mof")<br/> +#pragma include ("Core/CIM_System.mof")<br/> +#pragma include ("System/CIM_ComputerSystem.mof")<br/> #pragma include ("Interop/CIM_RegisteredProfile.mof")<br/> #pragma include ("Interop/CIM_RegisteredSubProfile.mof")<br/> #pragma include ("Core/CIM_Dependency.mof")<br/>
Looks syntactically sound. I don't recognize a couple of those classes as dual-namespace ones, but I'm not going to second guess our CIM Compliance Officer on that. :) +1
For my own curiosity - I'm not sure why CIM_EnabledLogicalElement.mof and CIM_Dependency.mof need to be added. I understand the need for the others though. =) -- Kaitlin Rupert IBM Linux Technology Center karupert@us.ibm.com
Kaitlin Rupert wrote:
For my own curiosity - I'm not sure why CIM_EnabledLogicalElement.mof and CIM_Dependency.mof need to be added. The derivation hierarchy for ComputerSystem is ManagedElement -> ManagedSystemElement -> LogicalElement -> EnabledLogicalElement -> System -> ComputerSystem
Dependency is not really necessary at the moment, but as ReferencedProfile derives from it and we will implement this association sooner or later, I already added this one to the list. But you are right. At the moment its not a requirement. -- Regards Heidi Eckhart Software Engineer Linux Technology Center - Open Hypervisor heidieck@linux.vnet.ibm.com ************************************************** IBM Deutschland Entwicklung GmbH Vorsitzender des Aufsichtsrats: Martin Jetter Geschaeftsfuehrung: Herbert Kircher Sitz der Gesellschaft: Boeblingen Registergericht: Amtsgericht Stuttgart, HRB 243294
Jay Gagnon wrote:
Heidi Eckhart wrote:
# HG changeset patch # User Heidi Eckhart <heidieck@linux.vnet.ibm.com> # Date 1196935599 -3600 # Node ID 30269254841ceed6a250ea2b714c594fa30cc19e # Parent ba4bc35f508573c53e4303ce2e7a9b5299b95f38 html: Added additional classes to cimv216-interop.mof
These additional classes are necessary to register Xen/KVM ComputerSystem and HostSystem classes to interop. Otherwise Pegasus refuses the registration. Signed-off-by: Heidi Eckhart <heidieck@linux.vnet.ibm.com>
diff -r ba4bc35f5085 -r 30269254841c doc/libvirt-cim.html --- a/doc/libvirt-cim.html Thu Dec 06 11:06:38 2007 +0100 +++ b/doc/libvirt-cim.html Thu Dec 06 11:06:39 2007 +0100 @@ -300,6 +300,11 @@ below:</p> #pragma include ("qualifiers.mof")<br/> #pragma include ("qualifiers_optional.mof")<br/> #pragma include ("Core/CIM_ManagedElement.mof")<br/> +#pragma include ("Core/CIM_ManagedSystemElement.mof")<br/> +#pragma include ("Core/CIM_LogicalElement.mof")<br/> +#pragma include ("Core/CIM_EnabledLogicalElement.mof")<br/> +#pragma include ("Core/CIM_System.mof")<br/> +#pragma include ("System/CIM_ComputerSystem.mof")<br/> #pragma include ("Interop/CIM_RegisteredProfile.mof")<br/> #pragma include ("Interop/CIM_RegisteredSubProfile.mof")<br/> #pragma include ("Core/CIM_Dependency.mof")<br/>
Looks syntactically sound. I don't recognize a couple of those classes as dual-namespace ones, but I'm not going to second guess our CIM Compliance Officer on that. :) +1 The registration of the classes where a RegisteredProfile is ElementConformsToProfile associated to is necessary for our checking mechanism in std_association. Otherwise CMClassPathIsA() fails, as the class is not found for the /root/interop namespace. The additional registration is only necessary for Pegasus. sfcb shares the one base schema all over its namespaces.
-- Regards Heidi Eckhart Software Engineer Linux Technology Center - Open Hypervisor heidieck@linux.vnet.ibm.com ************************************************** IBM Deutschland Entwicklung GmbH Vorsitzender des Aufsichtsrats: Martin Jetter Geschaeftsfuehrung: Herbert Kircher Sitz der Gesellschaft: Boeblingen Registergericht: Amtsgericht Stuttgart, HRB 243294
HE> # HG changeset patch HE> # User Heidi Eckhart <heidieck@linux.vnet.ibm.com> HE> # Date 1196935599 -3600 HE> # Node ID 30269254841ceed6a250ea2b714c594fa30cc19e HE> # Parent ba4bc35f508573c53e4303ce2e7a9b5299b95f38 HE> html: Added additional classes to cimv216-interop.mof I'm actually working up a patch to automate installation of the base schema, which should render the documentation about how to do it irrelevant. I've incorporated your additional classes below into my patch and will be sending it out shortly for comments. Thanks! -- Dan Smith IBM Linux Technology Center Open Hypervisor Team email: danms@us.ibm.com
participants (4)
-
Dan Smith -
Heidi Eckhart -
Jay Gagnon -
Kaitlin Rupert