"BMC和intel DCMI 1.5规范及WS-CIM映射规范介绍"

需积分: 5 148 浏览量更新于2024-01-23 收藏 464KB PDF 举报

本文介绍了两个规范文档，分别是BMC DCMI 1.5 Spec和Intel DCMI 1.5 Spec。同时还涉及了WS-CIM Mapping Specification文档。 BMC DCMI是基本管理控制器（Baseboard Management Controller，简称BMC）规范的一个版本，版本号为1.5。该规范是用于定义基本管理控制器硬件接口的标准。BMC是一种位于服务器主板上的芯片或模块，用于监控和管理服务器的硬件和软件功能。BMC DCMI 1.5 Spec详细规定了BMC的功能和接口，以及与其他硬件和软件组件的交互方式。 Intel DCMI 1.5 Spec是Intel开发的一种管理接口规范，用于与BMC进行通信和管理。Intel DCMI 1.5 Spec与BMC DCMI 1.5 Spec相互配合，共同定义了服务器管理的标准。Intel DCMI 1.5 Spec文档提供了详细的接口定义、数据结构和管理命令，帮助开发人员实现高效的服务器管理功能。 WS-CIM Mapping Specification 是一个文档类型规范，定义了WS-CIM之间的映射标准。WS-CIM（Web Services for Common Information Model）是一种基于Web服务的管理框架，用于管理和监控分布式计算环境中的各种资源和服务。WS-CIM Mapping Specification详细描述了WS-CIM的数据模型和接口，以及如何与其他管理系统进行集成。以上这些规范文档的使用有助于提高服务器的管理和监控能力。BMC DCMI和Intel DCMI定义了服务器硬件和管理接口的规范，使得不同厂商的服务器可以实现统一的管理功能。WS-CIM Mapping Specification通过定义标准的数据模型和接口，简化了不同管理系统的集成过程，提高了管理的效率和便捷性。总之，这些规范文档为服务器管理领域的开发人员提供了一种标准化的方法和指南，有助于实现高效、灵活和可扩展的服务器管理系统。通过遵循这些规范，服务器管理功能可以更加稳定、可靠和易于维护，从而提高了企业和系统管理的效率和可靠性。这些规范文档的使用对于推动服务器管理和互操作性方面的发展具有重要的意义。

WS-CIM Mapping Specification DSP0230

16 DMTF Standard Version 1.1.0

The rules shown in Table 7 should be used to convert cimDateTime elements on the client side to their 441

representation in CIM. 442

Table 7 – Rules for Converting cimDateTime to datetime 443

cim:cimDateTime

Element Representation of datetime in CIM

Interval

CIM datetime that is an Interval. Fields that are not significant shall be replaced with

asterisks. For example, an interval of 2 days 23 hours would be converted to

0000000223****.******:000

Datetime

CIM datetime that is a time stamp. The mapping of timezone offset is left to the implementer

to either normalize it to zero or preserve it in translation. Note that the resulting CIM datetime

string does not contain any asterisks, because this XML element is used only when the original

CIM datetime satisfies this condition.

Time

CIM datetime that is a time stamp. The mapping of timezone offset is left to the implementer to

either normalize it to zero or preserve it in translation. Note that the resulting CIM datetime

string does not contain any asterisks in the hhmmss.mmmmmm portion, and contains only

asterisks in the yyyymmdd portion, because this XML element is used only when the original CIM

datetime satisfies this condition.

Date

CIM datetime that is a time stamp. The mapping of timezone offset is left to the implementer to

either normalize it to zero or preserve it in translation. Note that the resulting CIM datetime

string does not contain any asterisks in the yyyymmdd portion, and contains only asterisks in the

hhmmss.mmmmmm portion, because this XML element is used only when the original CIM

datetime satisfies this condition.

CIM_DateTime

CIM datetime with a string equal to the XML element text.

8.3 CIM References 444

The cim:cimReference datatype is defined as follows: 445

<xs:complexType name="cimReference"> 446

<xs:sequence> 447

<xs:any namespace="##other" maxOccurs="unbounded" processContents="lax"/> 448

</xs:sequence> 449

<xs:anyAttribute namespace="##any" processContents="lax"/> 450

</xs:complexType> 451

The xs:any element in this definition represents a structure of a single transport reference that uniquely 452

identifies a location to which messages may be directed for the referenced entity. This structure may be 453

either a single element that expresses the complete transport reference or a sequence of elements, if the 454

transport reference requires multiple elements to uniquely identify a location. In the case of Addressing 455

(see Web Services Addressing (WS-Addressing) 1.0 – Core

and DSP0226, "Management Addressing" 456

clause), the xs:any element shall be replaced by the required wsa:EndpointReference child elements 457

defined by Addressing recommendations, as if the property element were of type 458

wsa:EndpointReferenceType. These requirements for the representation of the reference datatype 459

supersede any requirements specified in DSP0004

regarding the syntactical representation of a value of 460

type reference. 461

The attribute maxOccurs="unbounded" shall not be misconstrued as allowing multiple transport 462

references. 463

EXAMPLE: An example of the use of Addressing versions as a transport reference, mapped to the 464

AssociatedComponent property, is as follows: 465

<xs:element name="AssociatedComponent" type="cim:cimReference"/> 466

DSP0230 WS-CIM Mapping Specification

Version 1.1.0 DMTF Standard 17

The reference could appear in an XML instance document as in either of the following examples: 467

<AssociatedComponent 468

xmlns:wsa="http://www.w3.org/2005/08/addressing"> 469

<wsa:Address>. . .</wsa:Address> 470

. . .  471

</AssociatedComponent> 472

473

<AssociatedComponent 474

xmlns:wsa="http://schemas.xmlsoap.org/ws/2004/08/addressing"> 475

<wsa:Address>. . .</wsa:Address> 476

. . .  477

</AssociatedComponent> 478

8.4 cimAnySimpleType Datatype 479

WS-CIM also introduces a special type built on xs:anySimpleType, cimAnySimpleType. 480

cimAnySimpleType extends xs:anySimpleType with the facility to add any attribute to an instance of 481

this type in an XML instance document. This special datatype is required in the mapping of CIM 482

properties with ValueMaps containing ranges because of a restriction in the XML Schema specification. 483

CIM properties with ValueMaps containing ranges are mapped as restrictions of a WS-CIM datatype 484

where the restriction contains an xs:union consisting of an explicit enumeration of any discrete values 485

(if any) and the specific ranges specified by the ValueMap (see 9.2.3 for the mapping rules for properties 486

with ValueM

aps). However, XML Schema currently requires that the content of a restriction be the same 487

as or be derived from the content type of the parent complex type that is being restricted. Because an 488

XSD union can be of any XSD simple type, XML Schema restricts the use of a union in a derivation by 489

restriction to a parent type whose content is of any simple type. Thus, CIM properties with ValueMaps 490

containing ranges are mapped to XSD elements of the cimAnySimpleType datatype. 491

However, this mapping overrides the normal datatype mapping of the CIM property (as mapped in 492

Table 5). Using the cimAn

ySimpleType datatype means that standard WS-CIM datatyping information 493

is lost for the property. Consequently, the following normative rule governs the use of this special 494

datatype: 495

The cimAnySimpleType datatype shall be used only for mapping CIM properties with ValueMaps 496

containing ranges. Any other use of this datatype is considered non-conformant to the WS-CIM 497

specification. 498

8.5 Derivation by Restriction 499

The purpose of the WS-CIM datatypes is to provide the ability to add any attributes to CIM data in the 500

instance document where those attributes are not defined in the XSD definition of the data. For example: 501

. . . 502

<this:Name xns:AdditionalAttribute=". . . "> 503

myName 504

</this:Name> 505

. . . 506

where AdditionalAttribute is a global attribute defined in a namespace (xns) and is not explicitly specified 507

in the type definition of Name. Including the AdditionalAttribute attribute in the instance document is valid 508

based on the presence of the following wildcard specification in the definition of the type for this data: 509

<xs:anyAttribute namespace="##any" processContents="lax"/> 510

WS-CIM Mapping Specification DSP0230

18 DMTF Standard Version 1.1.0

However, the anyAttribute wildcard is not inherited by a type definition that is derived by restriction from a 511

parent type containing the wildcard. Therefore, the following normative rule applies to all derivations by 512

restriction: 513

To preserve attribute extensibility, the anyAttribute wildcard shall be specified in any derivation by 514

restriction from a WS-CIM datatype. 515

NOTE: All mapping rules involving a derivation by restriction in this specification explicitly stipulate the inclusion of 516

the anyAttribute wildcard in the mapping. 517

8.6 WS-CIM Canonical Values 518

The WS-CIM specification maps a CIM Boolean to an XSD Boolean. According to XSD data types 519

(http://www.w3.org/TR/2001/REC-xmlschema-2-20010502/#boolean

), a Boolean value can be one of four 520

possible values: true, false, 1, or 0. 521

To promote interoperability, the WS-CIM specification requires adoption of canonical representation by 522

W3C XPath spec for XSD Boolean type. The implementations shall use the values of TRUE and FALSE 523

as the canonical values for Boolean type. 524

9 CIM Class to XML Schema Mappings 525

This clause contains the normative rules for mapping CIM elements into structures of XML Schema. Each 526

clause provides the following information: 527

• complete normative rules 528

• an example of the use of those rules 529

• runtime normative rules and examples, if necessary, to address runtime consideration 530

9.1 Class Namespace 531

Each CIM class has an assigned XML namespace, the class namespace. This clause defines the class 532

namespace, and subsequent clauses define how the class namespace is used in the mapping. 533

The rules for specifying the XSD namespace of a CIM class are as follows: 534

• Each CIM class shall be assigned its own namespace in the XML schema. 535

'http://schemas.dmtf.org/wbem/wscim/' wscim-major-version '/cim-schema/' cim-schema-major-536

version '/' cim-class-schema ‘_’ cim-class-name 537

Where: 538

wscim-major-version is the major version number of this specification. Note that this 539

version number changes only if there are incompatible changes in the specification. 540

cim-schema-major-version is the major version number of the CIM schema version to 541

which the class being converted belongs. Note that this version number changes only if 542

there are incompatible changes in the CIM schema. 543

cim-class-schema is the CIM schema name of the class (for example, "CIM"). Note that the 544

schema name may be vendor specific in the case of vendor extensions to CIM classes. 545

cim-class-name is the name of the CIM class. 546

• The process and rules for the publication of the schema documents that define class 547

namespaces are defined in DSP4009

. 548

DSP0230 WS-CIM Mapping Specification

Version 1.1.0 DMTF Standard 19

EXAMPLE: The CIM_ComputerSystem class that belongs to version 2.11.0 of the CIM schema would 549

have the following namespace: 550

http://schemas.dmtf.org/wbem/wscim/1/cim-schema/2/CIM_ComputerSystem 551

9.2 Properties 552

This clause describes the general principles for converting CIM properties to XSD. It also describes 553

specific principles for converting array properties, value maps, octetstrings, and embedded objects and 554

instances. 555

9.2.1 General Principles 556

This clause defines and illustrates the normative rules that apply to the mapping of all CIM properties to 557

XSD. 558

9.2.1.1 General Rules 559

The rul

es for mapping CIM properties to XML Schema are as follows: 560

• Every property of a CIM class shall be represented by a global element definition. Note that 561

this rule applies to properties locally defined on the class itself and properties inherited 562

from superclasses (see 9.4). The GED that corresponds to a CIM property shall exhibit the 563

following features

: 564

– The GED shall be defined in the namespace of the class in the XML Schema (see 9.1). 565

–

The name of the GED shall be the same as the name of the CIM property. 566

– The type of the GED shall comply with the datatype conversion table defined in clause 8. 567

wever, in some cases, depending on what qualifiers apply to the CIM property, it is 568

necessary to restrict the default type of the GED element. The complete specification of the 569

type of the GED shall comply with the normative rules for mapping qualifiers. (See 11.2 for 570

the norm

ative rules for mapping specific qualifiers to XSD structures.) 571

• The GED of properties that are not arrays shall be specified with nillable="true", if 572

the CIM property has a Key or Required qualifier with an effective value of false. The 573

GED of properties that are not arrays shall be specified without the nillable attribute 574

(the default of nillable is false), if the CIM property has a Key or Required qualifier 575

with an effective value of true. (See 11.3 for rules regarding the inheritance of qualifiers.) 576

NOTE: These rules do not apply to array properties. All GEDs that represent array properties shall be 577

specified with nillable="true". 578

• The CIM Schema may assign default initializer values directly to properties, as, for 579

example, in the MOF construct uint16 EnabledState=3 (see DSP0004

). Default 580

initializer values shall be mapped to a metadata fragment using <cim:DefaultValue>. 581

Default initializer values shall not be mapped to the xs:default attribute, which carries 582

different semantics than CIM Schema default values. 583

The metadata fragment shall contain the xsi:type attribute, which specifies the primitive 584

datatype of the default initializer value. The specified datatype shall be the same as the base 585

type of the WS-CIM defined datatype of the XSD element that represents the CIM property 586

(see clause 8). The base type of a WS-CIM defined da

tatype shall be determined from its 587

datatype definition in the common namespace. In the case of the cimDateType datatype, 588

xsi:type shall specify the primitive datatype of the element that is used to express the value 589

of cimDateType. 590

WS-CIM Mapping Specification DSP0230

20 DMTF Standard Version 1.1.0

NOTE: This rule precludes specifying default initializer values for REF properties (cimReference 591

elements in XSD mapping). However, specifying such default initializer values is also unsupported in CIM. 592

Values for cimReference elements can be provided only at runtime. 593

The GEDs that represent CIM properties are referenced by child elements within the element to which the 594

CIM class that owns the properties is mapped (see 9.3). Rules for specifying the minOccurs and 595

maxOccurs attribute

s of the elements that reference the GEDs are provided in 9.3.1. 596

EXAMPLE: As an example of the preceding rules, consider the following MOF fragment that defines the 597

(hypothetical) class EX_BaseComponent. The complete definition of this class is presented in B.1.1. 598

class EX_BaseComponent { 599

datetime InstallDate; 600

[

…

601

Required, MaxLen ( 1024 ) ] 602

string Name; 603

string StatusDescriptions[]; 604

string HealthStatus; 605

}; 606

Four GEDs need to be generated to represent the four properties of this class. Based on the preceding 607

rules, the first two properties are mapped as follows: 608

<xs:element name="InstallDate" type="cim:cimDateTime" nillable="true"/> 609

<xs:element name="Name"> 610

<xs:complexType> 611

<xs:simpleContent> 612

<xs:restriction base="cim:cimString"> 613

<xs:maxLength value="1024"/> 614

<xs:anyAttribute namespace="##any" processContents="lax"/> 615

</xs:restriction> 616

</xs:simpleContent> 617

</xs:complexType 618

</xs:element> 619

The complete mapping of this class is presented in B.2.1. For an example of a default initializer value 620

metadata fra

gment, see B.4.2. 621

9.2.1.2 Runtime Rules for Attribute Value Assignment 622

The occu

rrence of properties in an XML instance document may be subject to the following rule: 623

• If a Key qualifier that has an effective value of true is associated with the CIM property, 624

the cim:Key attribute may be applied to the corresponding element in the XML instance 625

document. Use of the cim:Key attribute shall conform to the following rules: 626

– If the attribute is present, its value shall be assigned as true in the XML instance. 627

– If the application decides to apply the cim:Key attribute to the property, it shall apply it to 628

all properties in the class that have a Key qualifier with an effective value of true 629

associated with them. If a Key qualifier is not associated with the CIM property, this 630

attribute shall be omitted. 631

The Name property can be designated with a Key qualifier in CIM: 632

class EX_SomeClass { 633

…

634

[

…

Key] 635

string Name; 636

} 637

剩余101页未读，继续阅读

dongdundun

粉丝: 4
资源: 9

"BMC和intel DCMI 1.5规范及WS-CIM映射规范介绍"

DCMI spec v1.5

Data Center Manageability Interface Specification v1.5 Revision

BMC150_spec

重置bmc查询bmc时间设置bmc时间 的脚本

如果BMC要实现一个eMMC存储器中存储两个BMC镜像存储功能，如何将BMC镜像存储到eMMC中用于引导BMC系统启动

BMC virtual usb 怎么通过BMC virtual usb controller禁用

BMC如何通过ESPI接口与HOST通信？BMC操作espi接口的流程是什么？

ping不通bmc地址

BMC与HOST通过LPC总线通信过程中BMC作为主设备还是从设备工作？

最新资源

重置bmc查询bmc时间设置bmc时间的脚本