Class CIM_SystemPartition Qualifiers |
---|
Name | Type | Value | From Class |
---|
Experimental | boolean | true | CIM_SystemPartition |
Deprecated | string | CIM_HostedDependency | CIM_SystemPartition |
Version | string | 2.8.1000 | CIM_SystemPartition |
Description | string | A Partition is an instance of a UnitaryComputerSystem (with its own OperatingSystem and Devices dedicated to the Partition) that is supported by underlying hardware and software. A Partition is not a virtualization of a Computer System, but the segmentation of the System ’ s compute capabilities. Partitions can run independent copies of possibly different OperatingSystems and have dedicated Devices. The ’ real ’ , underlying System (perhaps a Cluster or another UnitaryComputerSystem) aggregates its Partitions. These semantics are described by the System Partition association. The use of this association has been deprecated in lieu of using HostedDependency. | CIM_SystemPartition |
Composition | boolean | true | CIM_SystemPartition |
Association | boolean | true | CIM_SystemPartition |
Aggregation | boolean | true | CIM_SystemPartition |
Composition | boolean | true | CIM_ComponentCS |
Description | string | A ComputerSystem can aggregate another ComputerSystem. This association can be used to model MPP Systems with workstation frontends, an I2O subsystem embedded in a Unitary ComputerSystem, or a System that splits functionality between two processors, potentially running different Operating Systems. For example, if a CISC Processor and its associated OperatingSystem, are used for user interface and file support, and a RISC Processor and its OS are used for complex mathematical operations, this could be modeled as two ComputerSystems where one aggregates the other. In some cases, this could be modeled as a Cluster. The difference is the focus of the relationship. ComponentCS represents that unique and distinct ComputerSystems are aggregated by a higher level CS object. However, each of the component CSs are still distinguishable entities and are only viewed as such. Alternately, with a Cluster, the ComputerSystems that participate in it are inconsequential, when viewed through the ’ Cluster System ’ . When instantiating or subclassing the ComponentCS relationship, care should be taken that the component ComputerSystem meets the definitional requirements of a ComputerSystem - ie, a functional whole that provides compute capabilities and aggregates System Devices, an OperatingSystem, etc. | CIM_ComponentCS |
Association | boolean | true | CIM_ComponentCS |
Aggregation | boolean | true | CIM_ComponentCS |
Description | string | CIM_SystemComponent is a specialization of the CIM_Component association that establishes ’ part of ’ relationships between a System and any ManagedSystemElements of which it is composed. Use this association with caution when using it instead of a subclass such as SystemDevice or a peer association such as HostedService. This class is very broadly defined, which can lead to erroneous use. For example, Access Points that are dependent on (and hosted on) a System are NOT Components of the System. The System is not made up of any AccessPoint ’ parts ’ , which is why a Dependency association, HostedAccessPoint, was defined. Similarly, a PhysicalPackage is not a ’ part ’ of a System, because the physical element exists independently of any internal components, software, and so on. In fact, again, a Dependency relationship is true where a ComputerSystem is Dependent on its packaging, as described by the ComputerSystemPackage association. | CIM_SystemComponent |
Association | boolean | true | CIM_SystemComponent |
Aggregation | boolean | true | CIM_SystemComponent |
Association | boolean | true | CIM_Component |
Aggregation | boolean | true | CIM_Component |
Description | string | CIM_Component is a generic association used to establish ’ part of ’ relationships between Managed Elements. For example, it could be used to define the components or parts of a System. | CIM_Component |