layout-3 layout-6 layout-1 layout-top
layout-top layout-6 layout-1

Power Compliance

The Domain Power Service (DPS) ensures power compliance through a validation system that operates at two critical stages: topology activation and resource group creation. This guide explains how DPS maintains power compliance by validating constraints and automatically adjusting policies when necessary.

Overview

DPS power compliance is achieved through:

  1. Topology Constraint Validation - Ensuring the power topology can support the defined constraints before activation
  2. Dynamic Resource Group Validation - Validating power requirements when new resource groups are created
  3. Automatic Policy Adjustment - Falling back to lower power policies when constraints cannot be met
  4. Continuous Monitoring - Ongoing validation of power consumption against defined limits

Topology Activation Compliance

Initial Validation Process

When a topology is activated, DPS performs validation to ensure all power constraints can be satisfied:

1. Power Budget Verification

  • Total Power Calculation: DPS calculates the total power requirements across all entities in the topology
  • Constraint Checking: Validates that power domains have sufficient capacity to support their child entities
  • Hierarchy Validation: Ensures power flows correctly through the entire power distribution hierarchy

2. Power Factor Validation

  • Loss Calculations: Accounts for power losses through power distribution components using defined power factors
  • Efficiency Modeling: Validates that power supply efficiency ratings are realistic for the expected loads

3. Activation Failure Scenarios

The topology activation will fail if:

  • Total power demand exceeds available power budget in any power domain
  • Power distribution components cannot handle the calculated power flows
  • Constraint violations are detected at any level of the power hierarchy

Resource Group Compliance

Dynamic Validation During Creation

When resource groups are created, DPS performs real-time compliance validation:

1. Policy Application Validation

  • Resource Allocation: DPS calculates power requirements for the specific nodes allocated to the resource group
  • Policy Integration: Applies the requested power policy to the allocated resources
  • Constraint Verification: Validates that the modified topology still satisfies all power constraints

2. Power Tree Constraint Checking

DPS validates the entire power tree with the new policy applied:

PowerDomain (Root)
├── PDU-A
│   ├── Node-01 [Applied Policy: High-Performance]
│   └── Node-02 [Applied Policy: High-Performance]
└── PDU-B
    ├── Node-03 [Default Policy]
    └── Node-04 [Default Policy]

The validation ensures:

  • The root power domain can supply the total demand
  • Each PDU can handle its assigned load
  • No thermal or electrical limits are exceeded

3. Resource Group Creation Process

  1. Initial Request: Resource group creation request with desired power policy
  2. Power Calculation: DPS calculates total power requirements with the requested policy
  3. Constraint Validation: Validates against all topology constraints
  4. Success Path: If validation passes, resource group is created with the requested policy
  5. Fallback Path: If validation fails, DPS attempts policy adjustment

Automatic Policy Adjustment

Policy Fallback Mechanism

When the requested power policy cannot be satisfied, DPS implements an intelligent fallback system:

1. Policy Hierarchy

DPS maintains a hierarchy of power policies from highest to lowest power consumption, for example:

High-Performance → Balanced → Power-Saver → Emergency

2. Automatic Adjustment Process

  1. Validation Failure: Initial policy validation fails due to power constraints
  2. Policy Downgrade: DPS automatically tries the next lower power policy
  3. Re-validation: Performs constraint validation with the lower policy
  4. Iteration: Continues until a compliant policy is found or all options are exhausted

3. Fallback Example

# Resource group creation with automatic policy adjustment
Initial Request: Policy "High-Performance" for nodes [node-01, node-02]
Validation Result: FAILED - Insufficient power budget (deficit: 2500W)

Attempting Fallback: Policy "Balanced"
Validation Result: FAILED - Insufficient power budget (deficit: 800W)

Attempting Fallback: Policy "Power-Saver"
Validation Result: SUCCESS - Resource group created with "Power-Saver" policy

Resource Group ID: rg-12345
Applied Policy: Power-Saver
Allocated Nodes: node-01, node-02
Power Consumption: 12500W (within budget)

Best Practices for Compliance

1. Topology Design

  • Conservative Budgeting: Allocate 10-15% headroom in power domains for unexpected demands
  • Realistic Power Factors: Use measured power factors rather than theoretical values
  • Hierarchical Constraints: Implement constraints at multiple levels for better granularity

2. Policy Management

  • Graduated Policies: Create policies with gradual power differences to enable smooth fallbacks
  • Emergency Policies: Always maintain ultra-low power emergency policies

3. Monitoring and Maintenance

  • Regular Validation: Periodically re-validate topology constraints as hardware changes
  • Trend Analysis: Monitor power consumption trends to predict future capacity needs

Troubleshooting Compliance Issues

Common Compliance Problems

1. Topology Activation Failures

Problem: Topology fails to activate due to power budget violations Solution:

  • Review power domain capacities and increase if necessary
  • Adjust default topology entity policies
  • Validate entity power specifications

2. Resource Group Creation Failures

Problem: All policy fallbacks fail during resource group creation Solution:

  • Review current power allocation across existing resource groups
  • Implement more aggressive power-saving policies

    Copyright © 2026  NVIDIA Corporation