Alauda Build of HAMi
  • English

    • Versions and Components

    This page lists the HAMi components that users need to consider when installing, upgrading, or troubleshooting Alauda Build of HAMi.

    TOC

    Current versionsProduct componentsMetrics prerequisitesACP integration pointsLifecycle tasks

    Current versions

    ComponentTypeMarketplace versionPurpose
    Alauda Build of HAMiCluster Pluginv2.9.0HAMi sharing, virtualization, and scheduling product.
    Alauda Build of HAMi-WebUICluster Pluginv1.10.3Provides an optional HAMi-specific resource overview.
    Alauda Build of HAMi Ascend Device PluginOperator Bundlev1.4.0 (Technical Preview)Deploys and manages HAMi Ascend whole-card allocation, hard slicing, and soft slicing.
    WARNING

    Use Alauda Build of HAMi-WebUI v1.10.3 with HAMi v2.9.x. HAMi-WebUI v1.10.0 queries the HAMi 2.8 metric names and can show zero utilization when it is connected to HAMi 2.9.x.

    HAMi-WebUI v1.10.3 uses the upstream HAMi-WebUI v1.2.0 application baseline. The marketplace version and the upstream application baseline are different version identifiers; select the marketplace version when installing or upgrading the plugin.

    Alauda Build of HAMi Ascend Device Plugin v1.4.0 is Technical Preview. Review the release notes before use.

    Ascend paths build on Alauda Build of NPU Operator for the Driver, OCI Runtime, and ascend RuntimeClass. Direct allocation uses its native Device Plugin; HAMi-managed allocation switches device exposure to HAMi Ascend Device Plugin. Use Compatibility for the supported product combination and environment boundaries, then Choose a HAMi Deployment Scenario before installing components.

    Install the core cluster plugin first. Add only the separately packaged components required by the selected backend and user tasks:

    Use this table as the version source of truth. Use each installation page for its package form, prerequisites, and verification procedure.

    Product components

    ComponentPurpose
    HAMi schedulerSchedules workloads that request HAMi resources.
    HAMi NVIDIA device pluginBuilt into the HAMi cluster plugin; reports NVIDIA resources to Kubernetes and maps selected NVIDIA devices into containers when Enable NVIDIA is enabled.
    HAMi Ascend Device PluginProvides Ascend device exposure and allocation for HAMi-managed workloads, including whole-card allocation, template-based hard slicing, and soft slicing.
    HAMi webhookAdjusts workload scheduling behavior for HAMi-managed resources.
    HAMi-CoreProvides in-container resource control for supported backends.
    HAMi WebUIProvides an optional HAMi-specific resource overview. It is installed as a separate cluster plugin when delivered by the target release.

    Metrics prerequisites

    Vendor metrics exporters are not HAMi components and are not versioned in this table. HAMi Ascend Device Plugin v1.4.0 also provides built-in metrics for soft slicing. See Monitor HAMi Usage for the metrics available through each backend path.

    ACP integration points

    IntegrationValue
    Default namespacekube-system for HAMi core components
    Common NVIDIA resource keysnvidia.com/gpualloc, nvidia.com/gpucores, nvidia.com/gpumem
    Common node labelsNVIDIA backend: gpu=on; Ascend backends: ascend=on
    Ascend workload RuntimeClassascend for HAMi-managed whole-card, hard-slice, and soft-slice workloads
    MonitoringACP dashboards, optional HAMi WebUI, and backend metrics components documented by the selected vendor base path
    Quota metadataConfigured through ACP accelerator resource metadata
    Optional WebUIAlauda Build of HAMi-WebUI cluster plugin

    This page lists combinations supported by Alauda delivery. Use upstream HAMi and vendor documentation for the broader backend and hardware matrix.

    Lifecycle tasks