On 03/14/2013 12:54 PM, Jan Safranek wrote:
On 03/14/2013 12:40 PM, Jan Synacek wrote:
> Also, I added two association classes needed to connect LMI_Mount with
> LMI_MountSetting and LMI_MountService with LMI_MountCapabilities.
> [ Association ]
> class LMI_MountElementSettingData : CIM_ElementSettingData
> {
> [ Override("ManagedElement"), Description (
> "LMI_Mount reference." ) ]
> CIM_ManagedElement REF ManagedElement
>
> [ Override("SettingData"), Description (
> "LMI_MountSetting reference." ) ]
> CIM_SettingData REF SettingData
> };
Umm, LMI_Mount is not CIM_ManagedElement. It seems we cannot inherit
CIM_ElementSettingData here. We can make LMI_MountElementSettingData
without any superclass and just pretend it behaves like
CIM_ElementSettingData.
Jan.
Attached is a slightly modified version, that doesn't use the Mount class at all.
-- Class Methods API --
class MountConfigurationService {
CreateMount(
[OUT] Job: ref CIM_ConcreteJob
[OUT] Mount: ref MountedFileSystem
[IN] Filesystem: ref CIM_FileSystem
[IN] MountPoint: string
[IN] Goal: ref MountedFileSystemSetting
)
ModifyMount(
[OUT] Job: ref CIM_ConcreteJob
[OUT] NewMount: ref MountedFileSystem
[In] Mount: ref MountedFileSystem
[IN] Goal: ref MountedFileSystemSetting
)
DeleteMount(
[OUT] Job: ref CIM_ConcreteJob
[In] Mount: ref MountedFileSystem
)
}
class MountedFileSystemCapabilities {
CreateSetting(
[OUT] Goal: ref MountedFileSystemSetting
)
}
-- Design Notes --
MountedFileSystem corresponds to a /etc/mtab entry. PermanentMount represents an
entry in /etc/fstab.
--
Jan Synacek
Software Engineer, Red Hat