ISO/IEC 19395:2015
(Main)Information technology — Sustainability for and by information technology — Smart data centre resource monitoring and control
Information technology — Sustainability for and by information technology — Smart data centre resource monitoring and control
ISO/IEC 19395:2015 provides Messages that facilitate integrated or "smart" monitoring and control of Resources in those islands. The Messages are exchanged between the Management Function and Resources. ISO/IEC 19395:2015 acknowledges that those Resources may be composed of other Resources (e.g. a rack may contain servers, ventilators, etc.). In addition, e.g. those servers may be viewed from their computing, energy consumption or dissipation aspects which ISO/IEC 19395:2015 models as Resource Components and groups into IT, power and fluid Domains, respectively.
Technologies de l'information — Durabilité pour et par les technologies de l'information — Surveillance des ressources et contrôle des centres de données intelligents
General Information
Standards Content (Sample)
INTERNATIONAL ISO/IEC
STANDARD 19395
First edition
2015-01-15
Information technology —
Sustainability for and by information
technology — Smart data centre
resource monitoring and control
Technologies de l’information — Durabilité pour et par les
technologies de l’information — Surveillance des ressources et
contrôle des centres de données intelligents
Reference number
ISO/IEC 19395:2015(E)
©
ISO/IEC 2015
---------------------- Page: 1 ----------------------
ISO/IEC 19395:2015(E)
COPYRIGHT PROTECTED DOCUMENT
© ISO/IEC 2015
All rights reserved. Unless otherwise specified, no part of this publication may be reproduced or utilized otherwise in any form
or by any means, electronic or mechanical, including photocopying, or posting on the internet or an intranet, without prior
written permission. Permission can be requested from either ISO at the address below or ISO’s member body in the country of
the requester.
ISO copyright office
Case postale 56 • CH-1211 Geneva 20
Tel. + 41 22 749 01 11
Fax + 41 22 749 09 47
E-mail copyright@iso.org
Web www.iso.org
Published in Switzerland
ii © ISO/IEC 2015 – All rights reserved
---------------------- Page: 2 ----------------------
ISO/IEC 19395:2015(E)
Contents Page
Foreword .iv
Introduction .v
1 Scope . 1
2 Conformance . 2
3 Normative references . 2
4 Terms, definitions and acronyms . 3
5 Domains . 4
5.1 Introduction . 4
5.2 Base Domain . 5
5.2.1 CIM_System . 5
5.2.2 CIM_BaseMetricDefinition . 5
5.2.3 CIM_BaseMetricValue . 5
5.2.4 CIM_MetricDefForME . 6
5.2.5 CIM_MetricInstance . 6
5.2.6 CIM_RegisteredProfile . 6
5.2.7 CIM_SystemDevice . 6
5.2.8 CIM_Component . 7
5.2.9 Metrics for fluid measurements . 7
5.2.10 CIM_NumericSensor .10
5.2.11 CIM_EnabledLogicalElementCapabilities .10
5.2.12 CIM_ElementCapabilities .10
5.3 IT Domain .10
5.4 Power Domain .13
5.5 Fluid Domain .13
5.5.1 SDC_FluidConnection .15
5.5.2 SDC_FluidElement.15
5.5.3 SDC_FluidMeasurementPoint .16
5.5.4 SDC_FluidTransferPort .16
5.5.5 SDC_CoolingSystem .16
5.5.6 SDC_CoolingSettingData .16
6 Properties .16
7 Messages .22
7.1 Commands and responses .23
7.1.1 GET . .23
7.1.2 SET .23
7.2 Event subscription and notification.24
7.2.1 Event subscription.24
7.2.2 Event notification .25
Annex A (normative) ECMA-400 Edition 1 Resource configuration options .26
Annex B (informative) Resource configuration of a CRAH system’s fluid perspective .30
© ISO/IEC 2015 – All rights reserved iii
---------------------- Page: 3 ----------------------
ISO/IEC 19395:2015(E)
Foreword
ISO (the International Organization for Standardization) and IEC (the International Electrotechnical
Commission) form the specialized system for worldwide standardization. National bodies that are
members of ISO or IEC participate in the development of International Standards through technical
committees established by the respective organization to deal with particular fields of technical
activity. ISO and IEC technical committees collaborate in fields of mutual interest. Other international
organizations, governmental and non-governmental, in liaison with ISO and IEC, also take part in the
work. In the field of information technology, ISO and IEC have established a joint technical committee,
ISO/IEC JTC 1.
The procedures used to develop this document and those intended for its further maintenance are
described in the ISO/IEC Directives, Part 1. In particular the different approval criteria needed for
the different types of document should be noted. This document was drafted in accordance with the
editorial rules of the ISO/IEC Directives, Part 2 (see www.iso.org/directives).
Attention is drawn to the possibility that some of the elements of this document may be the subject
of patent rights. ISO and IEC shall not be held responsible for identifying any or all such patent rights.
Details of any patent rights identified during the development of the document will be in the Introduction
and/or on the ISO list of patent declarations received (see www.iso.org/patents).
Any trade name used in this document is information given for the convenience of users and does not
constitute an endorsement.
For an explanation on the meaning of ISO specific terms and expressions related to conformity
assessment, as well as information about ISO’s adherence to the WTO principles in the Technical Barriers
to Trade (TBT) see the following URL: Foreword - Supplementary information
ISO/IEC 19395 was prepared by Ecma International (as ECMA-400) and was adopted, under a special
“fast-track procedure”, by Joint Technical Committee ISO/IEC JTC 1, Information technology, in parallel
with its approval by national bodies of ISO and IEC.
iv © ISO/IEC 2015 – All rights reserved
---------------------- Page: 4 ----------------------
ISO/IEC 19395:2015(E)
Introduction
Operation of data centres requires management of storage, computation, communication, electrical
energy and temperature to achieve the required quality of service and efficiency parameters. Often,
however, the separate management of Information Technology (IT), electrical energy (or power) and
cooling Resource islands yields a sub-optimal result.
This International Standard provides Messages that facilitate integrated or “smart” monitoring and
control of Resources in those islands. The Messages are exchanged between the Management Function
and Resources. The International Standard acknowledges that those Resources may be composed of
other Resources (e.g. a rack may contain servers, ventilators, etc.). In addition, e.g. those servers may
be viewed from their computing, energy consumption or dissipation aspects which this International
Standard models as Resource Components and groups into IT, power and fluid Domains, respectively.
© ISO/IEC 2015 – All rights reserved v
---------------------- Page: 5 ----------------------
INTERNATIONAL STANDARD ISO/IEC 19395:2015(E)
Information technology — Sustainability for and by
information technology — Smart data centre resource
monitoring and control
1 Scope
In the Smart Data Centre, Management Functions monitor and control Resources. Resources model IT
and facility equipment, systems and components in a data centre. To monitor and control the Resources’
Properties, Management Functions exchange command, response or event Messages with Resources,
see Figure 1.
Figure 1 — Scope
Resources are made up out of Resource Components which this second edition shares Properties
with classes in Common Information Models (CIM). Messages refer to Resources and their Properties.
Messages are encoded in XML and exchanged in HTTP primitives.
Figure 1 illustrates the functionality that this second edition adds as described above.
Figure 2 — Functionality that second edition adds
Management Function(s), Resources, IT & facility equipment, systems and components themselves
are out of scope as illustrated in Figure 1, Figure 2 and Figure 3. Static information such as location,
addressing of Resources and CPU models are out of scope as well.
© ISO/IEC 2015 – All rights reserved 1
---------------------- Page: 6 ----------------------
ISO/IEC 19395:2015(E)
Figure 3 — detailed scope using CIM (UML Notation)
2 Conformance
Conformant Management Functions monitor and control Properties (Clause 6) of Resources using
Messages as specified in Clause 7.
In response to the commands, conformant responses and events from Resources use the Messages as
specified in Clause 7.
Any of the Resource configurations specified in Annex A may optionally be implemented, in addition to
any other configuration using any combination of Resources and Resource Components.
3 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.
DMTF, “CIM Schema”, http://dmtf.org/standards/cim
DMTF DSP0004, “CIM Infrastructure Specification”
DMTF DSP0200, “CIM Operations over HTTP”
DMTF DSP1009, “Sensors Profile”
DMTF DSP1011, “Physical Asset Profile”
2 © ISO/IEC 2015 – All rights reserved
---------------------- Page: 7 ----------------------
ISO/IEC 19395:2015(E)
DMTF DSP1014, “Ethernet Port Profile”
DMTF DSP1022, “CPU Profile”
DMTF DSP1027, “Power State Management Profile”
DMTF DSP1029, “OS Status Profile”
DMTF DSP1033, “Profile Registration Profile”
DMTF DSP1035, “Host LAN Network Port Profile”
DMTF DSP1042, “System Virtualization Profile”
DMTF DSP1044, “Processor Resource Virtualization Profile”
DMTF DSP1045, “Memory Resource Virtualization Profile”
DMTF DSP1047, “Storage Resource Virtualization Profile”
DMTF DSP1052, “Computer System Profile”
DMTF DSP1053, “Base Metrics Profile”
DMTF DSP1057, “Virtual System Profile”
DMTF DSP1081, “Virtual System Migration Profile”
4 Terms, definitions and acronyms
For the purposes of this document, the following terms, definitions and acronyms apply.
4.1
Common Information Model
CIM
4.2
CIM Client
emitter of CIM message requests and consumer of CIM message responses
4.3
CIM Listener
consumer of events
4.4
CIM message request
command or event request
4.5
CIM message response
response
4.6
condition query
expression on property value
© ISO/IEC 2015 – All rights reserved 3
---------------------- Page: 8 ----------------------
ISO/IEC 19395:2015(E)
4.7
Distributed Management Task Force
DMTF
Note 1 to entry: DMTF’s URL is http://www.dmtf.org/
4.8
domain
set of resource components
4.9
event description indication filter
set of conditions and associated parameters
4.10
Information Technology
IT
4.11
CIM message
command, response or event
4.12
Management Function
MF
4.13
property
resource attribute
4.14
Resource Component
RC
4.15
CIM Resource
representation of IT and facility equipment, systems or components
4.16
Smart Data Centre
SDC
arrangement of all the resources and management function(s)
5 Domains
5.1 Introduction
This International Standard specifies Resource Components (RC) which share Properties with CIM
classes, to compose Resource configurations as specified in Figure 3. The Resource Components are
grouped into IT, power, fluid and base Domains.
4 © ISO/IEC 2015 – All rights reserved
---------------------- Page: 9 ----------------------
ISO/IEC 19395:2015(E)
Figure 4 — Resource and Resource Component
In tables in this Clause, the Key indicates the identifier which shall be unique in the SDC namespace as
specified in Common Information Model (CIM) Infrastructure Specification (DSP0004). The Key uniquely
identifies each instance.
5.2 Base Domain
To construct the foundation of Resources, Resource Components from the base Domain shall be used.
5.2.1 CIM_System
See CIM Schema.
5.2.2 CIM_BaseMetricDefinition
See Base Metrics Profile (DSP1053). TimeScope is optional in DSP1053 whereas in this International
Standard, TimeScope is mandatory.
5.2.3 CIM_BaseMetricValue
The requirements in Base Metrics Profile (DSP1053) and those in Table 1 apply.
© ISO/IEC 2015 – All rights reserved 5
---------------------- Page: 10 ----------------------
ISO/IEC 19395:2015(E)
Table 1 — Class: CIM_BaseMetricValue
*1
Properties M/O Requirements on Value
TimeStamp Mandatory In case the device generating the metric instances does not have a clock
device, the TimeStamp value shall be “99990101000000.000000+000” in
case the base metric definition time scope requires that the TimeStamp
value is not NULL. “99990101000000.000000+000” is used to indicate
that the DateTime property value is not valid.
Volatile Mandatory TRUE
*1
“M/O” indicates “mandatory or optional.”
5.2.4 CIM_MetricDefForME
CIM_MetricDefForME shall be used to associate CIM_BaseMetricDefinition to SDC_
FluidMeasurementPoint. The requirements in Base Metrics Profile (DSP1053) and those in Table 2 apply.
If the CIM_BaseMetricDefinition class is implemented, CIM_MetricDefForME shall be also implemented.
Table 2 — Class: CIM_MetricDefForME
Properties M/O Requirements on value
Antecedent Mandatory Key: Shall be a reference to SDC_FluidMeasurementPoint
with Cardinality 1 indicating one reference
Dependent Mandatory Key: Shall be a reference to CIM_BaseMetricDefinition
with Cardinality 1.* indicating one or more references
MetricCollectionEnabled Optional
5.2.5 CIM_MetricInstance
CIM_MetricInstance shall be used to associate CIM_BaseMetricValue instances to CIM_BaseMetricValue
instances. See Base Metrics Profile (DSP1053).
If the CIM_BaseMetricDefinition class is implemented, CIM_MetricInstance shall be also implemented.
5.2.6 CIM_RegisteredProfile
The requirements in Profile Registration Profile (DSP1033) and those in Table 3 apply.
Table 3 — Class: CIM_RegisteredProfile
Properties M/O Requirements on value
RegisteredName Mandatory “CoolingSystem”
RegisteredVersion Mandatory “1.0.0”
RegisteredOrganization Mandatory 1 (Others)
OtherRegisteredOrganization Mandatory “Ecma_TGG”
5.2.7 CIM_SystemDevice
CIM_SystemDevice association shall be used to associate SDC_FluidElement with the CIM_System
instance of which it is a member. The requirements in CIM Schema and those in Table 4 apply.
6 © ISO/IEC 2015 – All rights reserved
---------------------- Page: 11 ----------------------
ISO/IEC 19395:2015(E)
Table 4 — Class: CIM_SystemDevice
Properties M/O Requirements on value
Antecedent Mandatory Key: Shall be a reference to CIM_System
with Cardinality 1 indicating one reference
Dependent Mandatory Key: Shall be a reference to SDC_FluidElement
with Cardinality 1.* indicating one or more references
5.2.8 CIM_Component
CIM_Component association shall be used to associate SDC_FluidElement instances of which it is
involved. The requirements in CIM Schema and those in Table 5 apply.
Table 5 — Class: CIM_Component
Properties M/O Requirements on value
Antecedent Mandatory Key: Shall be a reference to SDC_FluidElement
with Cardinality 1 indicating one reference
Dependent Mandatory Key: Shall be a reference to SDC_FluidElement
with Cardinality 1.* indicating one or more references
5.2.9 Metrics for fluid measurements
The set of fluid metrics supported by an instance of SDC_FluidMeasurementPoint is implementation
dependent. An instance of SDC_FluidMeasurementPoint may support all, none, or any combination of
these metrics. A Management Function may detect the supported metric definitions by traversing the
CIM_MetricDefForME association.
By traversing the CIM_MetricForME association, a Management Function retrieves all metrics currently
available for a given SDC_FluidMeasurementPoint instance.
The TimeStamp and Duration Properties shall be provided for all metrics where the CIM_
BaseMetricDefinition.TimeScope is equal to “Interval” (3).
5.2.9.1 Interval metrics
Interval metrics shall be used as metrics where the value applies to a time interval, e.g. the average
temperature over a given interval. For interval metrics, CIM_BaseMetricDefinition.TimeScope Property
value shall be equal to “Interval” (3). CIM_BaseMetricValue.TimeStamp and CIM_BaseMetricValue.
Duration allow the Management Function to evaluate over which interval the metric was computed.
5.2.9.1.1 AverageTemperature
AverageTemperature metric shall be used to measure average temperature at the measuring point
during a given demand interval. Table 6 specifies the requirements on the CIM_BaseMericDefinition
instance for AverageTemperature metric.
© ISO/IEC 2015 – All rights reserved 7
---------------------- Page: 12 ----------------------
ISO/IEC 19395:2015(E)
Table 6 — CIM_BaseMetricDefinition instance for AverageTemperature metric
Properties M/O Requirements on value
Id Mandatory Key
Name Mandatory “SDC:AverageTemperature ”
Description Optional “SDC standard metric for average temperature at the measuring point
during the interval.”
DataType Mandatory 5 (real64)
Units Optional “C”
ProgrammaticUnits Mandatory “degree Celcius”
IsContinuous Mandatory TRUE
ChangeType Mandatory 4 (Gauge)
TimeScope Mandatory 3 (Interval)
GatheringType Mandatory 3 (Periodic)
5.2.9.1.2 AverageHumidity
AverageHumidity metric shall be used to measure average temperature at the measuring point during a
given demand interval. Table 7 specifies the requirements on the CIM_BaseMericDefinition instance for
AverageHumidity metric.
Table 7 — CIM_BaseMetricDefinition instance for AverageHumidity metric
Properties M/O Requirements on values
Id Mandatory Key
Name Mandatory “SDC:AverageHumidity”
Description Optional “SDC standard metric for average humidity at the measuring point
during the interval.”
DataType Mandatory 5 (real64)
Units Optional “%”
ProgrammaticUnits Mandatory “percent”
IsContinuous Mandatory TRUE
ChangeType Mandatory 4 (Gauge)
TimeScope Mandatory 3 (Interval)
GatheringType Mandatory 3 (Periodic)
5.2.9.2 Point metrics
5.2.9.2.1 Temperature
Temperature metric shall be used to measure the temperature at a given instant. Table 8 specifies the
requirements on the CIM_BaseMericDefinition instance for Temperature metric.
8 © ISO/IEC 2015 – All rights reserved
---------------------- Page: 13 ----------------------
ISO/IEC 19395:2015(E)
Table 8 — CIM_BaseMetricDefinition instance for Temperature metric
Properties M/O Requirements on value
Id Mandatory Key
Name Mandatory “SDC:Temperature”
Description Optional “SDC standard metric for temperature at the measuring point at a
given point in time.”
DataType Mandatory 5 (real64)
Units Optional “C”
ProgrammaticUnits Mandatory “degree Celcius”
IsContinuous Mandatory TRUE
ChangeType Mandatory 3 (Gauge)
TimeScope Mandatory 2 (Point)
GatheringType Mandatory 4 (OnRequest)
5.2.9.2.2 Humidity
Humidity metric shall be used to measure the humidity at a given instant. Table 9 specifies the
requirements on the CIM_BaseMericDefinition instance for Humidity metric.
Table 9 — CIM_BaseMetricDefinition instance for Humidity metric
Properties M/O Requirements on value
Id Mandatory Key
Name Mandatory “SDC:Humidity”
Description Optional “SDC standard metric for humidity at the measuring point at a given
point in time.”
DataType Mandatory 5 (real64)
Units Optional “%”
ProgrammaticUnits Mandatory “percent”
IsContinuous Mandatory TRUE
ChangeType Mandatory 3 (Gauge)
TimeScope Mandatory 2 (Point)
GatheringType Mandatory 4 (OnRequest)
5.2.9.2.3 Flow rate
Flow rate metric shall be used to measure the flow rate at a given instant. Table 10 specifies the
requirements on the CIM_BaseMericDefinition instance for Flow rate metric.
© ISO/IEC 2015 – All rights reserved 9
---------------------- Page: 14 ----------------------
ISO/IEC 19395:2015(E)
Table 10 — CIM_BaseMetricDefinition instance for Flow rate metric
Properties M/O Requirements on value
Id Mandatory Key
Name Mandatory “SDC:FlowRate”
Description Optional “SDC standard metric for Flow rate at the measuring point at a given
point in time.”
DataType Mandatory 5 (real64)
Units Optional “M3/h”
ProgrammaticUnits Mandatory “cubic meters per hour”
IsContinuous Mandatory TRUE
ChangeType Mandatory 3 (Gauge)
TimeScope Mandatory 2 (Point)
GatheringType Mandatory 4 (OnRequest)
5.2.10 CIM_NumericSensor
CIM_NumericSensor is specified in Sensors Profile (DSP1009) and may be used to measure various values
including input power of servers. Figure 5 specifies the class diagram of CIM_NumericSensor.
Figure 5 — class: CIM_NumericSensor
5.2.11 CIM_EnabledLogicalElementCapabilities
CIM_EnabledLogicalElementCapabilities class is specified in Sensors Profile (DSP1009) and shall be used
to indicate support for managing the state of the system.
5.2.12 CIM_ElementCapabilities
CIM_ElementCapabilities association is specified in Sensors Profile (DSP1009) and shall be used to
associate CIM_NumericSensor with an instance of CIM_EnabledLogicalElementCapabilities that
describes the capabilities of CIM_NumericSensor.
5.3 IT Domain
The IT Domain has a set of CIM classes as specified in Table 11, Figure 6, Figure 7 and Figure 8. CIM
classes in the IT Domain shall be used to express the IT perspective of Resources.
Table 11 — CIM classes of IT Domain
Class/Association Reference
CIM_ComputerSystem DSP1052
CIM_HostedDependency DSP1052
CIM_HostedService DSP1042, DSP1081
CIM_ServiceAffectsElement DSP1081
10 © ISO/IEC 2015 – All rights reserved
---------------------- Page: 15 ----------------------
ISO/IEC 19395:2015(E)
Table 11 (continued)
Class/Association Reference
CIM_VirtualSystemMigrationService DSP1081
CIM_VirtualSystemManagementService DSP1042
CIM_Rack DSP1011
CIM_Chassis DSP1011
CIM_ChassisInRack DSP1011
CIM_ComputerSystemPackage DSP1011
CIM_SystemDevice DSP1052
CIM_ElementCapabilities DSP1057
CIM_Processor DSP1022
CIM_ProcessorCore DSP1022
CIM_ConcreteComponent DSP1022
CIM_Processor(virtual) DSP1044
CIM_OperatingSystem DSP1029
CIM_RunningOS DSP1029
CIM_StorageVolume DSP1047
CIM_BlockStorageStaticalData DSP1047
CIM_ElementStatisticalData DSP1035
CIM_NetworkPort DSP1035
CIM_NetworkPortStatistics DSP1035
CIM_VirtualComputerSystem DSP1057
CIM_VirtualSystemSettingData DSP1052
CIM_VirtualSystemSettingDataComponent DSP1052
CIM_ResourceAllocationSettingData DSP1052
CIM_SettingsDefineState DSP1052
CIM_ResourcePool DSP1044, DSP1045, DSP1047
CIM_ElementAllocatedFromPool DSP1044, DSP1045, DSP1047
CIM_Memory DSP1045
CIM_LogicalDisk DSP1047
CIM_StorageAllocationSettingData DSP1047
CIM_EthernetPort DSP1014
CIM_EthernetPortAllocationSettingData DSP1014
© ISO/IEC 2015 – All rights reserved 11
---------------------- Page: 16 ----------------------
ISO/IEC 19395:2015(E)
Figure 6 — IT Domain class schema(1)
Figure 7 — IT Domain class schema(2)
12 © ISO/IEC 2015 – All rights reserved
---------------------- Page: 17 ----------------------
ISO/IEC 19395:2015(E)
Figure 8 — IT Domain class schema(3)
5.4 Power Domain
The power Domain has a set of CIM classes as specified in Table 12 and Figure 9. CIM classes in the power
Domain shall be used to express the power perspective of Resources.
Table 12 — CIM classes of power Domain
Class/Association Reference
CIM_PowerManagementService DSP1027
CIM_AssosatedPowerManagementService:PowerState DSP1027
Figure 9 — Power Domain class schema
5.5 Fluid Domain
The fluid Domain has a set of CIM classes to express the fluid perspective of Resources.
The fluid Domain classes shall be used to construct a topology of SDC_FluidElements concerned with
thermal energy flows. Annex B shows examples of such topologies.
Figure 10 represents the class schema for the fluid Domain. For simplicity, the prefix CIM_, or SDC_ has
been removed from the names of the classes.
© ISO/IEC 2015 – All rights reserved 13
---------------------- Page: 18 ----------------------
ISO/IEC 19395:2015(E)
Figure 10 — Fluid Domain class schema
SDC_FluidMeasurementPoint represents a point to measure fluid flowing through the SDC_FluidElement.
CIM_RegisteredProfile represents the advertisement of the implementation of this schema.
Instances of CIM_BaseMetricDefinition are associated to instances of SDC_FluidMeasurementPoint
through the CIM_MetricDefForME association. The metric definition instances contain semantic
information data and meta information on metrics. Instances of this class are defined later in this
schema. The individual metric values are contained in CIM_BaseMetricValue instances.
Figure 11 represents CIM schema of cooling system. In Figure 11, SDC_CoolingSettingData represents
generic setting parameter for a cooling system.
14 © ISO/IEC 2015 – All rights reserved
---------------------- Page: 19 ----------------------
ISO/IEC 19395:2015(E)
Figure 11 — Cooling system class schema
...
Questions, Comments and Discussion
Ask us and Technical Secretary will try to provide an answer. You can facilitate discussion about the standard in here.