Re: [Sblim-devel] LVM_Device.mof.snia error !!

[Viktor M. <mih...@de...>]

Hi Arvid,

well it seems that we have to revise the classes as I fear Heidi had
some good reasons to include the additional keys. Thanks for pointing
that out, maybe you could try to modify the MOFs to remove the offending
key qualifiers. BTW: did the other MOF files pass the test under
OpenWBEM? 


>                     Arvind Jain
>                     <arv...@iv...       To:     "'sbl...@ww...'"
>                     m>                             <sbl...@ww...>
>                     Sent by:                      cc:
>                     sblim-devel-admin@www-1       Subject:     [Sblim-devel] LVM_Device.mof.snia error !!
>                     26.ibm.com
> 
> 
>                     11/07/01 12:43 AM
>                     Please respond to
>                     Arvind Jain
> 
> 
> 
> When I try to compile the mof file LVM_Device.mof.snia using:
> 
> owmofc http://localhost:5988 /root LVM_Device.mof.snia
> 
> I get the following error:
> 
> File: LVM_Device.mof.snia Line: 0: Starting parsing
> File: LVM_Device.mof.snia Line: 387: Finished parsing
> File: LVM_Device.mof.snia Line: 37: Processing class: LVM_VolumeGroup
> File: LVM_Device.mof.snia Line: 37: Updated class: LVM_VolumeGroup
> File: LVM_Device.mof.snia Line: 91: Processing class: LVM_LogicalVolume
> Recoverable error in file: LVM_Device.mof.snia on line: 91: Received error
> from CIMOM: class does not exist (class does not exist (Parent class has
> keys. Child cannot have additional key properties: LVM_LogicalVolume))
> File: LVM_Device.mof.snia Line: 138: Processing class: LVM_PhysicalVolume
> Recoverable error in file: LVM_Device.mof.snia on line: 138: Received error
> from CIMOM: class does not exist (class does not exist (Parent class has
> keys. Child cannot have additional key properties: LVM_PhysicalVolume))
> File: LVM_Device.mof.snia Line: 193: Processing class: LVM_PVExtentRange
> Recoverable error in file: LVM_Device.mof.snia on line: 193: Received error
> from CIMOM: class does not exist (class does not exist (Parent class has
> keys. Child cannot have additional key properties: LVM_PVExtentRange))
> File: LVM_Device.mof.snia Line: 218: Processing class: LVM_ResidesOnExtent
> File: LVM_Device.mof.snia Line: 218: Updated class: LVM_ResidesOnExtent
> File: LVM_Device.mof.snia Line: 241: Processing class: LVM_Mapping
> File: LVM_Device.mof.snia Line: 241: Updated class: LVM_Mapping
> File: LVM_Device.mof.snia Line: 265: Processing class:
> LVM_PVExtentPartOfPhysicalVolume
> File: LVM_Device.mof.snia Line: 265: Updated class:
> LVM_PVExtentPartOfPhysicalVolume
> File: LVM_Device.mof.snia Line: 289: Processing class:
> LVM_LogicalVolumeBasedOnPhysicalVolume
> File: LVM_Device.mof.snia Line: 289: Updated class:
> LVM_LogicalVolumeBasedOnPhysicalVolume
> File: LVM_Device.mof.snia Line: 310: Processing class:
> LVM_PhysicalVolumeBasedOnVolume
> File: LVM_Device.mof.snia Line: 310: Updated class:
> LVM_PhysicalVolumeBasedOnVolume
> File: LVM_Device.mof.snia Line: 335: Processing class:
> LVM_LogicalVolumeInVolumeGroup
> File: LVM_Device.mof.snia Line: 335: Updated class:
> LVM_LogicalVolumeInVolumeGroup
> File: LVM_Device.mof.snia Line: 360: Processing class:
> LVM_PhysicalVolumeInVolumeGroup
> File: LVM_Device.mof.snia Line: 360: Updated class:
> LVM_PhysicalVolumeInVolumeGroup
> Compilation finished.  3 errors occurred.
> 
> Apparently the MOF file has additional key declared in the sub class
> derived
> from a class that already has keys.
> 
> According to version 2.2 of the CIM Specification the CIMOM sub class
> should
> not additional key defined.
> 
> Here is a paragraph taken from section 4.5.5 (Title: Key Properties)
> of Version 2.2 of the CIM Specification:
> 
>      ==========================================================
>      If a new subclass is defined from a superclass, and the
>      superclass has key properties (including those inherited
>      from other classes), the new subclass _cannot_ define
>      any additional key properties. New key properties in the
>      subclass can be introduced only if all classes in the
>      inheritance chain of the new subclass are keyless.
>      ==========================================================
> 
> I am using OpenWBEM to compile the MOF file in the repository.
> I understand that SBLIM is not built for OpenWBEM from Caldera. However,
> shouldn't other CIMOM have the same checks built in?
> 
> Is there a way to get around this issue? thx, arv.
> 
> _______________________________________________
> Sblim-devel mailing list
> Sbl...@ww...
> http://www-124.ibm.com/developerworks/oss/mailman/listinfo/sblim-devel

-- 
Kind Regards / Mit freundlichen Grüßen
  Viktor Mihajlovski
  
  Linux Technology Center

  IBM Laboratory Böblingen, Germany
  Phone +49-7031-16-2560
  Email mih...@de...