Dynamia ascend-device-plugin Chart 0.3.0
Release date: 2026-10-26
| Version | Previous | Current |
|---|---|---|
| Chart | 0.2.2 | 0.3.0 |
| appVersion | v1.4.2 | v1.4.3 |
This minor Chart release delivers application v1.4.3 and commercial libvnpu v1.4.3. The application adds per-card resource control across multiple NPUs. The published Chart retains the force compute-policy default; its ENPU deployment configuration is completed by the Chart 0.3.1 patch.
Open-source baselines
This release selectively integrates the following feature baselines while retaining Enterprise resource management and runtime extensions.
| Component | Open-source baseline | Delivery scope |
|---|---|---|
| Ascend Device Plugin | ab41bec | Per-card quotas and monitoring, shared virtual-device counts, and backend selection. The published Chart has the deployment limitations described below. |
| hami-vnpu-core | 98ec21f, with HostArgs support from 86b120e | Per-device runtime state, spatial compute control, and additional memory-allocation and launch hooks. |
HAMi Enterprise compatibility
| Feature or mode | Minimum HAMi Enterprise version | Companion requirements and upgrade guidance |
|---|---|---|
| Template-based hardware partitioning | v2.9.0-rc0 | The existing scheduler can be retained. |
hami-core static soft partitioning, including Enterprise compute policies, task priority, and Turbo | v2.10.0-r2 | Upgrade Enterprise first if using an earlier version, and complete license activation. Application v1.4.3 requires the companion runtime authorization provided by this release. |
| Automatic memory expansion | v2.10.0-r2 | Requires an ordinary container explicitly using hami-core with one vNPU, expansion approval, and admission protection. The companion Chart requires Kubernetes 1.30 or later. Multi-NPU allocation does not extend automatic expansion to multiple NPUs. |
The application includes an ENPU backend, but this Chart package lacks its runtime and configuration mounts. Use Chart 0.3.1 for the completed deployment configuration and its Enterprise companion requirements.
Enterprise extensions
The following capabilities were delivered in earlier commercial releases and remain available:
- Automatic memory expansion raises a single-vNPU container's memory limit only after HAMi Enterprise approval. It does not change the Pod resource request or AI Core quota.
NPU_CORE_UTILIZATION_POLICY=forcelimits the average compute duty cycle. SmallerNPU_TASK_PRIORITYvalues have higher priority at cooperative submission boundaries. Submitted work finishes naturally; fixed preemption latency is not guaranteed, and sustained high-priority demand can delay lower-priority work.NPU_TURBO_MODE=truedisables compute throttling and priority arbitration while retaining memory limits, accounting, and approved expansion. Use it only for trusted, compute-exclusive workloads.- Image pinning with
image.digestand thevnpuMonitormetrics service, ServiceMonitor, and PrometheusRule configuration remain available.
Changes
Chart changes
- [Upstream sync] Renames the bundled configuration field and Helm value from
vnpuDeviceSplitCounttodeviceSplitCount, retaining the default of10. A positive node-levelvDeviceCounttakes precedence. Source: ascend-device-plugin #144. - [Enterprise feature] Changes the default
image.tagfromv1.4.2to an empty value, so the image template followsappVersion. An explicitimage.tagorimage.digeststill overrides that selection.
Application changes
- [Upstream sync] Supports memory and compute quotas per physical NPU across multi-card allocations. Each card receives its own quota rather than the sum across cards. A container's allocated cards must have equal effective memory and compute quotas; unequal quotas are rejected. Monitoring follows the allocated physical devices. Sources: ascend-device-plugin #147, hami-vnpu-core #44.
- [Upstream sync] Adds spatial compute control and the
dynamic,fixed, andoverdraftscheduling policies. Spatial control sets cooperative Cube/Vector budgets through CANN; it does not create exclusive hardware partitions or guarantee proportional inference throughput. The published Chart still injectsforceby default. Sources: ascend-device-plugin #145, hami-vnpu-core #43, #44. - [Upstream sync] Extends quota accounting to cached/configured and runtime HBM allocation paths. Allocation identity and retained physical handles prevent duplicate charges and incorrect refunds; failed native allocations roll back their reservations. Source: hami-vnpu-core #46.
- [Upstream sync] Accounts for ACL HostArgs eager launches through the same compute-admission path as other intercepted submissions. Source: hami-vnpu-core #41.
- [Enterprise feature] Adds runtime authorization to
hami-coreworkloads. Complete Enterprise license activation before creating workloads; recreate Pods after license renewal so they receive the updated authorization.
Upgrade guidance
Prepare the companion and runtime
- For
hami-core, first upgrade HAMi Enterprise tov2.10.0-r2if needed and complete license activation. Use UTC in the soft-partitioned workload containers. - Record each workload's actual shared-memory paths and host mount mappings. Stop the old soft-partitioned workloads being migrated and confirm that all processes using their shared state have exited.
- Back up the affected state and use fresh local and global paths, or remove only the old files owned by those stopped workloads. The new runtime uses
.device-<physical-device-ID>files for each card. Default local files are under/usr/local/hami-vnpu-core/containers/<Pod-UID>_<container-name>/on the host; the new default global files are/usr/local/hami-shared-region/global_registry.device-<physical-device-ID>. Use the effective paths if mounts orHOOK_PATHare customized. Do not remove live mappings or mix old and new libraries on the same files. - Upgrade the plugin, confirm that the matching libvnpu
v1.4.3library is installed on the nodes, and recreate the workloads. Rolling the plugin alone does not update the library and mounts already used by running containers.
Review configuration
- Rename a custom Helm value
vnpuDeviceSplitCounttodeviceSplitCount, preserving its value. With the defaultconfig.create=false, update the actual shared-device ConfigMap. The application accepts the old device-configuration field as a fallback; if both fields are present,deviceSplitCountwins. A node-levelvDeviceCountstill takes precedence. Restart the plugin after changing its configuration. - Check
image.tagandimage.digest. Keeping an explicitv1.4.2tag or its digest prevents the new application from reaching the nodes; the target default image isghcr.io/dynamia-ai/ascend-device-plugin:v1.4.3. - Review manually supplied
NPU_MEMORY_LIMIT_MB,NPU_COMPUTE_LIMIT, and legacy quota variables. Limits now apply per card; when canonical and legacy aliases are both provided, their numeric values must agree. An omitted or zero-corerequest remains memory-only best effort and does not reserve or guarantee full compute capacity. - The Chart's
hamiVnpuCore.coreUtilizationPolicyremainsforce. Use the 0.3.1 patch guidance when adopting the completed backend configuration or thedefault/spatialdefaults.
Existing users of automatic memory expansion must retain its approval and admission configuration, explicit huawei.com/vnpu-mode: hami-core, and one allocated vNPU per ordinary container. Init containers and multi-vNPU containers are outside that expansion scope.
Values reference
The parameter descriptions below are preserved from the README bundled with Chart 0.3.0. The original values.yaml from that package defines its defaults.
Expand values table
| Key | Type | Default | Description |
|---|---|---|---|
| config.create | bool | false | Create the bundled device configuration ConfigMap for an installation without HAMi. Leave disabled when HAMi owns the device configuration. |
| config.deviceConfigMapName | string | "hami-scheduler-device" | Name of the device configuration ConfigMap created when config.create=true. |
| config.existingDeviceConfigMapName | string | "hami-scheduler-device" | HAMi-managed device configuration ConfigMap to reuse when config.create=false. The ConfigMap must be in the release namespace. |
| daemonSet.args[0] | string | "--config_file" | |
| daemonSet.args[1] | string | "/device-config.yaml" | |
| daemonSet.args[2] | string | "--v=4" | |
| daemonSet.args[3] | string | "--node_config_file" | |
| daemonSet.args[4] | string | "/node-config.yaml" | |
| daemonSet.name | string | "hami-ascend-device-plugin" | Device plugin DaemonSet name. |
| deviceSplitCount | int | 10 | Number of virtual devices advertised per physical Ascend NPU in soft-slicing mode when this chart creates the device configuration. A positive node-level vDeviceCount overrides it. |
| fullnameOverride | string | "" | Override the fully qualified resource name. |
| hamiVnpuCore.coreUtilizationPolicy | string | "force" | Default compute policy injected into hami-core containers that do not declare NPU_CORE_UTILIZATION_POLICY. |
| hamiVnpuCore.enabled | bool | false | Enable hami-vnpu-core in the bundled device configuration when config.create=true. This mode requires the HAMi scheduler. |
| image.digest | string | "" | Optional immutable OCI manifest digest. When set, it takes precedence over image.tag. |
| image.pullPolicy | string | "IfNotPresent" | Kubernetes image pull policy. |
| image.repository | string | "ghcr.io/dynamia-ai/ascend-device-plugin" | Container image repository. |
| image.tag | string | "" | Container image tag. Defaults to the chart appVersion when empty. |
| nameOverride | string | "" | Override the chart name used in resource names. |
| nodeConfig | string | "nodes: []" | Per-node hami-vnpu-core configuration written to the node ConfigMap. |
| nodeConfigMap.create | bool | true | Create the per-node configuration ConfigMap. |
| nodeConfigMap.name | string | "hami-device-node-config" | Per-node configuration ConfigMap name. |
| nodeSelector.ascend | string | "on" | Node label value used to schedule the device plugin. |
| rbac.name | string | "hami-ascend" | Name shared by the chart-managed RBAC resources. |
| resources.limits.cpu | string | "500m" | |
| resources.limits.memory | string | "500Mi" | |
| resources.requests.cpu | string | "500m" | |
| resources.requests.memory | string | "500Mi" | |
| runtimeClass.create | bool | true | Create the Ascend RuntimeClass. |
| runtimeClass.handler | string | "ascend" | Container runtime handler used by the RuntimeClass. |
| runtimeClass.name | string | "ascend" | RuntimeClass resource name. |
| serviceAccount.create | bool | true | Create a ServiceAccount for the device plugin. |
| serviceAccount.name | string | "hami-ascend" | ServiceAccount name. |
| vnpuMonitor.enabled | bool | false | Expose device plugin metrics and create optional Prometheus Operator resources. |
| vnpuMonitor.prometheusRule.create | bool | true | Create a PrometheusRule when vnpuMonitor.enabled=true. |
| vnpuMonitor.prometheusRule.groupLabels.vendor | string | "ascend" | |
| vnpuMonitor.prometheusRule.groupName | string | "ascend-vnpu" | Recording-rule group name. |
| vnpuMonitor.prometheusRule.interval | string | "15s" | Recording-rule evaluation interval. |
| vnpuMonitor.prometheusRule.labels.release | string | "prometheus" | |
| vnpuMonitor.prometheusRule.labels.role | string | "recording-rules" | |
| vnpuMonitor.prometheusRule.labels.vendor | string | "ascend" | |
| vnpuMonitor.prometheusRule.name | string | "hami-ascend-vnpu-monitor" | PrometheusRule resource name. |
| vnpuMonitor.prometheusRule.namespace | string | "monitoring" | Namespace for the PrometheusRule. |
| vnpuMonitor.service.name | string | "hami-ascend-device-plugin-metrics" | Headless Service that exposes the device plugin metrics port. |
| vnpuMonitor.serviceMonitor.create | bool | true | Create a ServiceMonitor when vnpuMonitor.enabled=true. |
| vnpuMonitor.serviceMonitor.interval | string | "15s" | Prometheus scrape interval. |
| vnpuMonitor.serviceMonitor.labels.release | string | "prometheus" | |
| vnpuMonitor.serviceMonitor.name | string | "hami-ascend-vnpu-monitor" | ServiceMonitor resource name. |
| vnpuMonitor.serviceMonitor.namespace | string | "monitoring" | Namespace for the ServiceMonitor. |
| vnpuMonitor.serviceMonitor.path | string | "/metrics" | Metrics HTTP path. |