Grouping and Tagging#

NVIDIA Fleet Intelligence provides two standard groupings and a free-form tagging system.

As of the 1.4.2 release and agent version 1.3, standard groupings are created at the agent and propagated to the service.

Note

Please see the Agent documentation for complete details on passing groups to the service.

Standard Groupings#

Compute Zones and Node Groups can be created to group and manage a larger number of nodes. Customers are free to use these groups as they see fit, but keep in mind that Compute Zones have a location and contain Node Groups, which themselves contain nodes. Compute Zones are intended to represent a region or data center, and Node Groups are intended to represent a cluster of nodes of similar type within that region. Nodes can only reside in a single Node Group and a single Compute Zone. Use Tags for customized groups.

The Fleet Intelligence service will allow editing the metadata of the Compute Zones, for example, contact information and GPS coordinates. Node Groups are not editable within the Fleet Intelligence service user interface.

If the compute zone or node group is not passed from the agent, it will appear as Unassigned in the Fleet Intelligence service user interface. If the node group is not passed from the agent, but the compute zone is passed, a compute zone specific unassigned node group will be created. To correct any errors in compute zone or node group assignment, you must edit the agent configuration to pass the correct compute zone or node group.

Tags#

Tags are a free-form tagging system that can be used to group and manage nodes in any way the customer wishes. For example, a “type” tag could be used to group nodes by their GPU type, or a “location” tag could be used to group nodes by their physical location.

Tags can be added to or removed from machines by clicking on the machine name. In the Details -> Basic side panel, click the tags icon (at the bottom) to open the Machine Tags dialog, where tags can be added or removed from machines/nodes.

Tags are currently set in the user interface and are not passed from the agent to the service.