Overview
The Inventory feature provides a centralized, authoritative view of all infrastructure resources in the system, including both physical and virtual assets. It acts as the primary database for tracking and managing these resources, ensuring they are properly categorized, maintained, and available for operational activities.
By maintaining a consistent and up-to-date inventory, administrators can plan resource utilization more effectively, allocate infrastructure with confidence, and optimize overall capacity across environments.
Why use Inventory?¶
- Centralizes tracking of all infrastructure resources in one place
- Simplifies monitoring and allocation of resources
- Supports accurate capacity and usage planning
- Improves visibility and control of hardware and virtual assets
- Enables better organization and lifecycle management of devices
Inventory Sections¶
From the navigation under Inventory, the following resource types can be managed:
- Devices: Manage and track physical servers and other hardware resources
- VMs: Manage and track virtual machines
- InfiniBands: Manage InfiniBand networking components
- Switches: Manage network switch devices and their configurations
Roles and Responsibilities¶
The Inventory system is primarily used by cloud partners who manage their own GPU infrastructure. These administrators are responsible for uploading, maintaining, and tracking all physical and virtual assets within the environment.
Cloud Partner Administrators¶
Cloud partner admins manage the full lifecycle of infrastructure resources in the inventory system to support GPU-based compute provisioning.
Responsibilities:
- Upload and register GPU servers, switches, and virtual machines
- Maintain accurate, real-time inventory of available and allocated devices
- Track resource ownership and usage across tenants and projects
- Mark devices as available or in use during provisioning and teardown workflows
- Ensure infrastructure readiness for automated provisioning via developer tools
Note: End users (e.g., customers or developers) do not interact with the Inventory directly. They request compute resources through external interfaces, and the Inventory is updated automatically during provisioning.