1 message in com.xensource.lists.xen-cim[Xen-cim] Current code vs. DMTF model| From | Sent On | Attachments |
|---|---|---|
| Szymanski, Lukasz K | 17 May 2006 08:06 |
| Subject: | [Xen-cim] Current code vs. DMTF model |
|---|---|
| From: | Szymanski, Lukasz K (Luka...@unisys.com) |
| Date: | 05/17/2006 08:06:59 AM |
| List: | com.xensource.lists.xen-cim |
This is my understanding of the gap between the DMTF and the Xen code currently in place. I made some guesses as to where some of the classes belong in terms of the Xen model. I compared the existing code to the System Virtualization and Resource Virtualization profile documents. Please correct/modify as appropriate.
Here are classes I don't know what to do with: ---------------------------------------------------------------------- - CIM_EnabledLogicalElementCapabilities Mandatory Not Implemented
CIM_ConcreteJob Optional Not Implemented CIM_LogicalDevice (host resource) Conditional Not Implemented
These belong to either Hardware Instrumentation of Settings Configuration: ---------------------------------------------------------------------- --------------------------------- CIM_VirtualSystemManagement Capabilities Mandatory Not Implemented CIM_VirtualSystemManagementService Mandatory Not Implemented CIM_VirtualSystemSettingData Mandatory In Progress
Virtual System Hardware Instrumentation ---------------------------------------------------------------------- --- CIM_ComputerSystem Mandatory Implemented CIM_LogicalDevice (virtual resource) Mandatory Implemented
Virtual Systems Resource Settings Configuration ---------------------------------------------------------------------- -- CIM_VirtualSystemSettingDataComponent Mandatory In Progress CIM_ResourceAllocationSettingData (Current State) Mandatory In Progress CIM_ResourceAllocationSettingData (RecordedSetting) Mandatory Not Implemented
Resource Pool ----------------------- CIM_ResourcePool Mandatory Not Implemented CIM_ResourcePoolConfigurationService Mandatory Not Implemented CIM_ResourcePoolConfiguration Capabilities Mandatory Not Implemented
DMTF Profile Registration ------------------------------------- CIM_RegisteredProfile Mandatory Not Implemented
This is my understanding of the gap between the DMTF and the Xen code currently in place in terms of associations. Please correct/modify as appropriate. From the System Virtualization Profile document, Version 0.7.1
Associations CIM_AssociatedVirtualSystem ManagementService Mandatory Not Implemented CIM_ElementCapabilities Mandatory Implemented CIM_ElementConformsToProfile Mandatory Not Implemented CIM_ElementSettingData Mandatory Implemented CIM_HostedDependency Mandatory Implemented CIM_HostedService Mandatory Implemented CIM_ReferencedProfile Mandatory Not Implemented CIM_RecordedSetting Mandatory Not Implemented CIM_ServiceAffectsElement Mandatory Not Implemented CIM_ServiceComponent Mandatory Not Implemented CIM_SettingDefinesCapabilities Mandatory Not Implemented CIM_VirtualSystemSettingData Component Mandatory In Progress
From the Resource Virtualization Profile document, Version 0.8.1 Associations CIM_ElementConformsToProfile Mandatory Not Implemented CIM_AffectedJobElement Optional Not Implemented CIM_AllocatedFromPool Mandatory Not Implemented CIM_ConcreteComponent Conditional Not Implemented CIM_ElementCapabilities Mandatory Implemented CIM_ElementSettingData Mandatory Implemented CIM_HostedDependency Optional Implemented CIM_HostedResourcePool Mandatory Not Implemented CIM_HostedService Mandatory Implemented CIM_RecordedSetting Mandatory Not Implemented CIM_ServiceAffectsElement Mandatory Not Implemented CIM_SystemDevice Conditional Implemented