P00105_-_HP_Base_Server_Profile
Table Of Contents
- Foreword
- Introduction
- 1 Scope
- 2 Normative References
- 3 Terms and Definitions
- 4 Symbols and Abbreviated Terms
- 5 Synopsis
- 6 Description
- 7 Implementation Requirements
- 7.1 HP_ComputerSystem
- 7.1.1 Support of System Contact Information (optional)
- 7.1.2 HP_ComputerSystem.LocationIndicator (optional)
- 7.1.3 HP_ComputerSystem.OtherIdentifyingInfo and IdentifyingDescriptions (optional)
- 7.1.4 HP_ComputerSystem.OperationalStatus (mandatory)
- 7.1.5 HP_ComputerSystem.OperationalStatusClassNames[] (conditional)
- 7.1.6 HP_ComputerSystem.Dedicated OtherDedicatedDescription (Mandatory)
- 7.1.7 HP_ComputerSystem physical identifiers (Optional)
- 7.1 HP_ComputerSystem
- 8 Methods
- 9 Use Cases
- 10 CIM Elements
- 11 Durable Names and Correlatable IDs
- Bibliography
17 Version 1.5.1
9 Use Cases
9.1 Object Diagrams
Figure 2 shows a simple implementation of a system containing 3 fans and 2 processors. The fans,
processors, and base system have been extended via HP extension profiles. This example also shows
that the DMTF physical asset profile has been implemented and has been extended to include base
server physical asset information by the HP Base Server Physical Asset profile.
The example uses the scoping class methodology for registering compliance to profiles. Using the
methodology only one CIM_ElementConformsToProfile is required to associate the single autonomous
profile (DMTF Base Server in this case) with the central class instance (HP_ComputerSystem in this
case) in the implementation namespace. Note that even though the scoping class is of type
HP_ComputerSystem, generic SMASH based clients would see an instance of CIM_ComputerSystem
because HP_ComputerSystem sub-classed off of CIM_ComputerSystem.
The interop namespace contains the same referenced profiles as you would expect given the description
contained in the Profile Registration Profile (DSP1033). The registered DMTF Base Server profile
references the DMTF CPU, Fan and Physical Asset profiles because the implementation namespace
contains implementations for each. In addition, the interop namespace contains the registrations for
extensions to the base model because the DMTF Base Server, CPU, Physical Asset, and Fan profiles
have been extended with HP specific profiles (HP Base Server, HP CPU, HP Base Server Physical Asset
and HP Fan). From the interop namespace clients can tell which autonomous and component profiles
are implemented and which of those profiles have been extended via HP extension profiles.