intersight_gpu_policy
GPU policy configuration for Cisco Intersight
Collection: cisco.intersight
Full Name: cisco.intersight.intersight_gpu_policy
Synopsis
GPU policy configuration for Cisco Intersight
Parameters
| Name | Type | Required | Default | Description |
|---|---|---|---|---|
| api_private_key | string | Filename (absolute path) or string of PEM formatted private key data to be used for Intersight API authentication. If a string is used, Ansible vault should be used to encrypt string data. Ex. ansible-vault encrypt_string –vault-id tme@/Users/dsoper/Documents/vault_password_file ‘—–BEGIN EC PRIVATE KEY—– | ||
| api_uri | string | https://intersight.com/api/v1 | URI used to access the Intersight API. If not set, the value of the INTERSIGHT_API_URI environment variable is used. | |
| api_key_id | string | Public API Key ID associated with the private key. If not set, the value of the INTERSIGHT_API_KEY_ID environment variable is used. Required if I(api_bearer_token) is not provided. | ||
| api_bearer_token | string | Bearer token for OAuth2 authentication with the Intersight API. When provided, I(api_key_id) and I(api_private_key) are not required and the C(cryptography) Python library is not needed. If not set, the value of the INTERSIGHT_API_BEARER_TOKEN environment variable is used. Secret value; omitted from logs and results. | ||
| validate_certs | bool | true | Boolean control for verifying the api_uri TLS certificate | |
| use_proxy | bool | true | If C(no), it will not use a proxy, even if one is defined in an environment variable on the target hosts. | |
| state | string | present | If C(present), will verify the resource is present and will create if needed. If C(absent), will verify the resource is absent and will delete if needed. Choices: present, absent | |
| organization | string | default | The name of the Organization this resource is assigned to. Profiles and Policies that are created within a Custom Organization are applicable only to devices in the same Organization. | |
| name | string | yes | The name assigned to the GPU policy. The name must be between 1 and 64 alphanumeric characters, allowing special characters :-_. | |
| description | string | The user-defined description of the GPU policy. | ||
| tags | list | List of tags in Key: | ||
| gpu_mode | string | compute | The operating mode for GPUs in the server. C(graphics) configures GPUs for standard graphics/display use. C(compute) configures GPUs for compute workloads (CUDA, inference, training). Choices: graphics, compute | |
| mig_enabled | bool | false | Enable or disable Multi-Instance GPU (MIG) partitioning. When enabled, each physical GPU can be partitioned into multiple isolated GPU instances. MIG is supported on NVIDIA A100, H100, B200 and newer architectures. | |
| mig_profiles | list | List of MIG partition profiles to apply when mig_enabled is true. Each entry defines the partition configuration for a GPU slot. If fewer profiles are specified than available GPUs, remaining GPUs use the default profile. Nested options: slot_id (int) required; partition_profile (str) required; instance_count (int) default=1 | ||
| gpu_thermal_threshold | int | GPU thermal throttle threshold temperature in Celsius. When GPU temperature exceeds this threshold, performance will be throttled to prevent damage. Valid range depends on GPU model. Typical values are 80-95 for data center GPUs. Set to 0 to use the platform default. | ||
| power_capping_enabled | bool | false | Enable or disable GPU power capping. When enabled, GPU power consumption is limited to the power_cap_watts value. | |
| power_cap_watts | int | Maximum power consumption per GPU in watts when power_capping_enabled is true. Valid range depends on GPU model (e.g., H100 SXM supports 300-700W). Set to 0 to use the platform default TDP. |
Example
yaml
- cisco.intersight.intersight_gpu_policy:
api_key_id: '{{ api_key_id }}'
api_private_key: '{{ api_private_key }}'
description: Standard GPU compute mode for inference
gpu_mode: compute
name: gpu-compute-default
organization: AI-Factory
name: Create GPU compute policy without MIG
- cisco.intersight.intersight_gpu_policy:
api_key_id: '{{ api_key_id }}'
api_private_key: '{{ api_private_key }}'
description: MIG partitioned for multi-tenant inference
gpu_mode: compute
mig_enabled: true
mig_profiles:
- instance_count: 2
partition_profile: 3g.40gb
slot_id: 1
- instance_count: 1
partition_profile: 7g.80gb
slot_id: 2
name: gpu-mig-inference
name: Create GPU policy with MIG partitioning for H100
- cisco.intersight.intersight_gpu_policy:
api_key_id: '{{ api_key_id }}'
api_private_key: '{{ api_private_key }}'
description: Power-managed GPU policy for dense deployments
gpu_mode: compute
gpu_thermal_threshold: 85
name: gpu-power-managed
power_cap_watts: 400
power_capping_enabled: true
name: Create GPU policy with thermal and power limits
- cisco.intersight.intersight_gpu_policy:
api_key_id: '{{ api_key_id }}'
api_private_key: '{{ api_private_key }}'
name: gpu-compute-default
state: absent
name: Delete GPU policy