Internet-Draft YANG Host Power Monitoring July 2024
Xiong, et al. Expires 9 January 2025 [Page]
Workgroup:
nmop
Internet-Draft:
draft-xiong-nmop-host-power-monitoring-yang-00
Published:
Intended Status:
Standards Track
Expires:
Authors:
R. Xiong
China Unicom
C. Liu
China Unicom
Y. Guo
China Unicom

A YANG Data Model for Host Power Monitoring

Abstract

This document will build a hierarchical YANG data model of SDN controller/management platform, router/switch and host to monitor the energy consumption of network devices and servers. SDN controller/management platform obtains data from routers/switches, and routers/switches obtain data from hosts. Therefore, in the overall hierarchical structure, the SDN controller/management platform directly obtains energy consumption data of all routers/switches, and indirectly obtains the specific energy consumption data of all hosts through routers/switches.

Status of This Memo

This Internet-Draft is submitted in full conformance with the provisions of BCP 78 and BCP 79.

Internet-Drafts are working documents of the Internet Engineering Task Force (IETF). Note that other groups may also distribute working documents as Internet-Drafts. The list of current Internet-Drafts is at https://datatracker.ietf.org/drafts/current/.

Internet-Drafts are draft documents valid for a maximum of six months and may be updated, replaced, or obsoleted by other documents at any time. It is inappropriate to use Internet-Drafts as reference material or to cite them other than as "work in progress."

This Internet-Draft will expire on 9 January 2025.

Table of Contents

1. Introduction

In the era of computing power, the energy consumption of data centers has increased exponentially, which is mainly reflected in IT equipment. IT equipments account for 45% of the overall energy consumption of data centers, of which hosts account for about 50%, storage systems account for about 35%, and network devices account for about 15%. Therefore, it is particularly important to focus on the energy consumption of network devices and hosts.

This document will build a hierarchical YANG data model of SDN controller/management platform, router/switch and host to monitor the energy consumption of network devices and servers. SDN controller/management platform obtains data from routers/switches, and routers/switches obtain data from hosts. Therefore, in the overall hierarchical structure, the SDN controller/management platform directly obtains energy consumption data of all routers/switches, and indirectly obtains the specific energy consumption data of all hosts through routers/switches.

[RFC8348] provides a model for server hardware management, and [I-D.y3bp-ivy-network-inventory-yang] is trying to extend the work to routers and other network elements. [RFC6022] already provides a model for NETCONF Monitoring, but nothing about power consumption. That gap is currently being addressed by [I-D.li-ivy-power]. At present, the YANG model for energy consumption management remains at the concept of using SDN controller/management platform as NETCONF client and router/switch as NETCONF server. Standard between router/switch and host is still a gap. This document focuses on power consumption monitoring and extends the work further to hosts.

1.1. Requirement Language

The key words "MUST", "MUST NOT", "REQUIRED", "SHALL", "SHALL NOT", "SHOULD", "SHOULD NOT", "RECOMMENDED", "NOT RECOMMENDED", "MAY", and "OPTIONAL" in this document are to be interpreted as described in BCP 14 [RFC2119] [RFC8174] when, and only when, they appear in all capitals, as shown here. These words may also appear in this document in lower case as plain English words, absent their normative meanings.

2. Model Structure

2.1. Basic Elements and Layers

Layer 1: SDN controller/management platform

SDN controller/management platform send requests to routers/switches to obtain configuration and status data, including power information of routers/switches themselves and what they have obtained from hosts.

Layer 2: Routers/switches

Routers/switches provide configuration and status data, including power information of routers/switches themselves and what they have obtained from hosts, and respond to requests from the SDN controller/management platform. In addition, routers/switches send requests to hosts to obtain configuration and status data, including power information.

Layer 3: Hosts

Agent needs to be installed to interact with routers/switches for NETCONF information. Hosts collect their energy consumption, and provide configuration and status data to routers/switches.

2.2. Relationship Between Layers

Relationship 1: Between router/switch and host

Router/switch acts as a NETCONF client and host acts as a NETCONF server. Host collects its energy consumption, and responds to the request of the upper-layer router/switch through the NETCONF agent to provide configuration and status data. Router/switch obtains energy consumption data of its lower-layer hosts.

Relationship 2: Between SDN controller/management platform and router/switch

SDN controller/management platform acts as a NETCONF client, and router/switch acts as a NETCONF server. The SDN controller/management platform obtains energy consumption data of routers/switches, and energy consumption data of hosts which has been already obtained.

2.3. Hierarchy Representation


       +--------------------------------------------------+
       |                                                  |
       |        SDN controller/management platform        |
       |                                                  |
       +----------+----------------------------+----------+
                  |                            |
       +----------+-----------+    +-----------+----------+
       |    router/switch     |    |     router/switch    |
       |          1           |    |           2          |
       +----+------------+----+    +----+------------+----+
            |            |              |            |
       +----+----+  +----+----+    +----+----+  +----+----+
       |   host  |  |   host  |    |   host  |  |   host  |
       |   1.1   |  |   1.2   |    |   2.1   |  |   2.2   |
       +---------+  +---------+    +---------+  +---------+

         Figure 1: Hierarchy representation

3. YANG Data Model

3.1. Tree Diagram

module: power-statistics
  +--ro power-statistics
     +--ro network-device-statistics* [network-device-name]
        +--ro network-device-name     string
        +--ro network-device-power    uint32
        +--ro host-statistics*        [host-name]
           +--ro host-name            string
           +--ro host-power           uint32

3.2. YANG Model

This model contains references to [RFC6991].

module power-statistics {
  description
    "Module of power statistics.";
  list network-device-statistics {
    description
      "List of network devices statistics, i.e. routers/switches.";
    key "network-device-name";
    leaf network-device-name {
      type string;
      description
        "Names of network devices.";
    }
    leaf network-device-power {
      type uint32;
      units "watts";
      description
        "The power consumption of each network devices.";
    }
    list host-statistics {
      description
        "List of hosts.";
      key "host-name";
      leaf host-name {
        type string;
        description
          "Names of hosts.";
      }
      leaf host-power {
        type uint32;
        units "watts";
        description
          "Power consumption of each host.";
      }
    }
  }
}

4. Security Considerations

YANG and other mechanisms already exist that help secure these interactions. This document extends the scope of what can be controlled by the management plane, but creates no new access paths. Besides, all nodes in this document are "config false". Once information leakage occures, the exposure of the topology of the entire network would be the worst situation.

5. IANA Considerations

This document makes no requests for IANA.

6. Normative References

[RFC8348]
Bierman, A., Bjorklund, M., Dong, J., and D. Romascanu, "A YANG Data Model for Hardware Management", RFC 8348, DOI 10.17487/RFC8348, , <https://www.rfc-editor.org/info/rfc8348>.
[I-D.y3bp-ivy-network-inventory-yang]
Yu, C., Belotti, S., Bouquier, J., Peruzzini, F., and P. Bedard, "A YANG Data Model for Network Inventory", Work in Progress, Internet-Draft, draft-y3bp-ivy-network-inventory-yang-00, , <https://datatracker.ietf.org/doc/html/draft-y3bp-ivy-network-inventory-yang-00>.
[RFC6022]
Scott, M. and M. Bjorklund, "YANG Module for NETCONF Monitoring", RFC 6022, DOI 10.17487/RFC6022, , <https://www.rfc-editor.org/info/rfc6022>.
[I-D.li-ivy-power]
Li, T. and R. Bonica, "A YANG model for Power Management", Work in Progress, Internet-Draft, draft-li-ivy-power-02, , <https://datatracker.ietf.org/doc/html/draft-li-ivy-power-02>.
[RFC6991]
Schoenwaelder, J., Ed., "Common YANG Data Types", RFC 6991, DOI 10.17487/RFC6991, , <https://www.rfc-editor.org/info/rfc6991>.
[RFC2119]
Bradner, S., "Key words for use in RFCs to Indicate Requirement Levels", BCP 14, RFC 2119, DOI 10.17487/RFC2119, , <https://www.rfc-editor.org/info/rfc2119>.
[RFC8174]
Leiba, B., "Ambiguity of Uppercase vs Lowercase in RFC 2119 Key Words", BCP 14, RFC 8174, DOI 10.17487/RFC8174, , <https://www.rfc-editor.org/info/rfc8174>.

Authors' Addresses

Ruizhe Xiong
China Unicom
Chang Liu
China Unicom
Yue Guo
China Unicom