Administrator CLI

The NVIDIA Run:ai Administrator (runai-adm) is a lightweight tool designed to support infrastructure administrators by simplifying two key tasks:

  • Collecting logs for troubleshooting and sharing with NVIDIA Run:ai support.

  • Configuring node roles in the cluster for optimal performance and reliability.

This section outlines the installation and usage of the NVIDIA Run:ai Administrator CLI to help you get started quickly.

Prerequisites

Before installing the CLI, review the following:

  • Operating system: The CLI is supported on Mac and Linux.

  • Kubectl: The Kubernetes command-line interface must be installed and configured to access your cluster. Follow the official guidearrow-up-right.

  • Cluster administrative permissions: The CLI requires a Kubernetes profile with administrative privileges.

Installation

To install the NVIDIA Run:ai Administrator CLI, ensure that the CLI version matches the version of your NVIDIA Run:ai cluster. You can either install the latest version or a specific version from the listarrow-up-right.

Installing the Latest Version

Use the following commands to download and install the latest version of the CLI:

chevron-rightMachashtag
wget --content-disposition https://app.run.ai/v1/k8s/admin-cli/darwin  
chmod +x runai-adm  
sudo mv runai-adm /usr/local/bin/runai-adm
chevron-rightLinuxhashtag

Installing a Specific Version

To install a specific version of the Administrator CLI that matches your NVIDIA Run:ai cluster version, append the version number to the download URL. Refer to the list of available versions linked above for the correct version number.

chevron-rightMachashtag
chevron-rightLinuxhashtag

Verifying Installation

Verify your installation completed successfully by running the following command:

Reference

Node Roles

To set or remove node rules using the runai-adm tool, run the following:

circle-info

Note

Use the --all flag to set or remove a role to all nodes.

Collect Logs

To collect logs using the runai-adm tool:

  1. Run the following command:

  2. Locate the generated compressed log file.

Last updated