HP WBEM TC Document Number: P00100 Date: 06/02/2010 Version: 2.0.0 HP Profile Registration Profile © Copyright 2008 Hewlett-Packard Development Company, L.P. The information contained herein is subject to change without notice. The only warranties for HP products and services are set forth in the express warranty statements accompanying such products and services. Nothing herein should be construed as constituting an additional warranty.
Contents Foreword ....................................................................................................................................................... 5 Introduction.................................................................................................................................................... 6 1 Scope ....................................................................................................................................................
Figures Figure 1 – HP Profile Registration Profile: Class Diagram ........................................................................... 9 Figure 2 – HP Profile Registration Profile: Inheritance Hierarchy Diagram ................................................ 10 Figure 3 – HP PRP: Fan and Processor Object Diagram (Scoping Class Methodology)........................... 14 Figure 4 – HP PRP: Fan and Processor Object Diagram (product specific extension) ..............................
Tables Table 1 – Related Profiles ............................................................................................................................. 9 Table 2 – Operations: HP_ExtendsProfile ................................................................................................. 13 Table 3 – Operations: HP_ReferencedProfile............................................................................................ 13 Table 4 – Operations: HP_ElementConformsToProfile .....................
Foreword The HP Profile Registration Profile (P00100) was prepared by the HP WBEM TC. Version 1.0.
Introduction The information in this specification should be sufficient for a provider or consumer of this data to identify unambiguously the classes, properties, methods, and values that shall be instantiated and manipulated to represent registration of HP profiles. The target audience for this specification is implementers who are writing CIM based providers or consumers of management interfaces representing the component described in this document. 6 Version 1.0.
1 Scope The HP Profile Registration profile extends the management capability of referencing profiles by adding the capability to HP Specific Profiles. 2 Normative References The following referenced documents are indispensable for the application of this document. For dated references, only the edition cited applies. For undated references, the latest edition of the referenced document (including any amendments) applies. 2.1 Approved References DMTF DSP0200, CIM Operations over HTTP 1.2.
3.4 mandatory used to indicate requirements strictly to be followed in order to conform to the document and from which no deviation is permitted 3.5 may used to indicate a course of action permissible within the limits of the document 3.6 need not used to indicate a course of action permissible within the limits of the document 3.7 optional used to indicate a course of action permissible within the limits of the document 3.
Extends: DMTF DSP1033, Profile Registration Profile 1.0.0 The HP Profile Registration Profile extends DMTF DSP1033 to add the capability of registering HP specific profiles. Table 1 – Related Profiles Profile Name Organization DSP1033 – Profile Registration Profile 6 DMTF Version Relationship 1.0.
CIM_ReferencedProfile CIM_Dependency see Profile Registration Profile HP_ReferencedProfile CIM_ElementConformsToProfile see Profile Registration Profile HP_ExtendsProfile HP_ElementConformsToProfile Figure 2 – HP Profile Registration Profile: Inheritance Hierarchy Diagram 7 Implementation Requirements This section details the requirements related to the arrangement of instances and properties of instances for implementations of this profile. 7.
7.1.6 HP_RegisteredProfile.ImplementationNameSpaces This property is an indexed array that lists the namespaces for the compliant provider implementations for the associated class name listed in ImplementationCentralClassNames. This property shall be set to the namespaces of the providers that directly implement the profile. 7.2 HP_ExtendsProfile This association shall be made between each extension profile registration and the parent profile it extends.
Associators AssociatorNames References ReferenceNames EnumerateInstances EnumerateInstanceNames A compliant implementation shall support all the operations in the default list for each class, unless the Requirements column states something other than Mandatory. 8.2 HP_RegisteredProfile All operations are supported as described by DSP200 v1.2. 12 Version 1.0.
8.3 HP_ExtendsProfile Table 2 lists operations that either have special requirements beyond those from DSP0200 or shall not be supported. All other operations may be supported as defined in DSP0200. Table 2 – Operations: HP_ExtendsProfile Operation Requirement Messages Associators Unspecified None AssociatorNames Unspecified None References Unspecified None ReferenceNames Unspecified None 8.
HP Base Server 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.
Figure 4 shows adds an extended profile from the HP Fan profile to show that profile can be extended to differing levels of specificity. In this example, the namespace implements an instance of HP_x86Fan which conforms to the DMTF Fan profile and the HP Fan profile. It additionally conforms to a very specific profile defining fans specific to x86 platforms.
Figure 5 shows the same implementation using the central class methodology for registering profiles. Each profile is associated to its central class via a CIM_ElementConformsToProfile (for DMTF profiles) or an HP_ElementConformsToProfile (for HP Profiles) association. Notice that a single central class instance can be associated to multiple profiles if the central class has been extended via an HP extension profile.
HP_ComputerSystem: system1 HP_ComputerSystemPackage HP_ComputerSystemChassis: chassis1 HP_SystemPhysicalFan HP_SystemFan mod1: HP_FanModule fan1: HP_Fan HP_RealizesFan HP_SystemPhysicalProcessor CPU2: HP_Processor proc1: HP_ProcessorChip HP_RealizesProcessor HP_SystemProcessor prof3: CIM_RegisteredProfile CIM_ElementConformsToProfile HP_ExtendsProfile CIM_ReferencedProfile RegisteredOrg: DMTF (2) RegisteredName: Base Server CIM_ReferencedProfile CIM_ReferencedProfile prof2: CIM_RegisteredProfile
Likewise for the DMTF CPU profile. The DMTF Physical Asset profile is extended to include HP CPU physical assets. The HP CPU Consolidated Status profile is an HP specific component profile that is referenced by the HP Base Server extension profile. Notice that neither of the profile reference the CPU Consolidated Status profile. Autonomous profiles or profiles that extend autonomous profiles associate to referenced profiles and not second tier component profiles or the profiles that extend them.
HP_ComputerSystemPackage HP_ComputerSystem: system1 HP_ComputerSystemChassis: chassis1 HP_ProcessorGroupHostedCollection HP_SystemPhysicalProcessor HP_SystemProcessor HP_ProcessorCollection: collection1 HP_PhysicalMemberOfProcessorCollection HP_LogicalMemberOfProcessorCollection HP_Processor: proc1 HP_ProcessorChip: procchip1 HP_RealizesProcessor HP_Processor: proc2 HP_ProcessorChip: procchip2 HP_RealizesProcessor CIM_ElementConformsToProfile prof3: CIM_RegisteredProfile RegisteredOrg: DMTF (2)
Figure 7 – HP PRP: HP Processor and Consolidated Status Figure 8 shows is an example of an implementation of the HP Fan and HP Base Server profiles and a direct implementation of the DMTF OS Status profile. Prof4 is the instance of the HP Base Server profile and prof6 is the instance of the HP Fan profile. Both of these profiles are directly implemented, thus their instances set values for the ImplementationCentralClassNames and the ImplementationNameSpaces properties.
System1:HP_ComputerSystem: SMX_ComputerSystem HP_SystemFan Fan1:HP_Fan:SMX_Fan CIM_RunningOS Os1:CIM_OperatingSystem: SMX_OperatingSystem CIM_ElementConformsToProfile prof3: CIM_RegisteredProfile HP_ExtendsProfile RegisteredOrg: DMTF (2) RegisteredName: Base Server CIM_ReferencedProfile CIM_ReferencedProfile prof2: CIM_RegisteredProfile prof1: CIM_RegisteredProfile RegisteredOrg: DMTF (2) RegisteredName: OS Status ImplementationCentralClassNames[0]:”SMX _OperatingSystem” ImplementationNameSpaces[0
For each association instance found in previous step 9.3 If the association instance is a HP_ExtendsProfile If HP_ExtendsProfile.dependent property equals the REF of this instance of HP_RegisteredProfile, then this profile is an extension profile. The client can determine the profile being extended by following the antecedent property of the found HP_ExtendsProfile association instance.
Table 5 – CIM Elements – HP Profile Registration Profile Element Name Requirement Description Classes HP_RegisteredProfile Mandatory see Section 7.1 HP_ReferencedProfile Conditional see Section 7.3 HP_ExtendsProfile Conditional see Section 7.2 HP_ElementConformsToProfile Conditional see Section 7.4 Indications None defined. 10.1 HP_RegisteredProfile HP_RegisteredProfile represents an HP defined profile registered in the interop namespace.
10.4 HP_ElementConformsToProfile This association is used associate a profile registered in the interop namespace with its central class that implements the profile in the implementation namespace. Table 9 – Class: HP_ElementConformsToProfile Properties Requirement Notes ConformantStandard M REF:HP_RegisteredProfile – reference to the HP profile registered in the interop namespace.
ANNEX A (normative) Change Log Version Date 0.1 3/15/06 Version 1.0.
ANNEX B (informative) Acknowledgments 26 Version 1.0.
ANNEX C (informative) Included WBEM TC CR Numbers CR Number Date CR00100 5/3/06 Version 1.0.
Bibliography This section contains a list of the external references and dependencies for this specification. 28 Version 1.0.