Servers
The Servers in Inventory Data Centers provides a centralized view to manage all physical infrastructure resources, such as GPU servers and bare metal nodes. This inventory enables efficient tracking, allocation, and planning of hardware resources across the system.
Each server entry represents a real physical node in the cloud partner’s infrastructure. These entries serve as the source of truth for provisioning compute resources to customers through isolated virtual machines and assigned GPUs.
Keeping server entries updated ensures full visibility and control over infrastructure assets, helping administrators prepare resources for provisioning and usage across environments.
Why use Servers?¶
- Maintain a complete inventory of physical compute resources
- Track details such as serial numbers, resource configurations, and tags
- Allocate and deallocate resources as needed
- Plan capacity and monitor utilization
- Gain insight into GPU and VM usage per service
- Serve as the backing source for compute provisioning workflows
Servers List View¶
From the Servers page, click the ellipsis icon at the far right of the required server and click View to access the following details:
- Properties
- Tags
- Interfaces
- GPU(s)
- VM(s)
Click the edit (pencil) icon to modify server details.
Adding a Server¶
Click + Add Server and provide the below details
Properties¶
Basic Information¶
| Field | Description | Example |
|---|---|---|
| Name | Unique device name | gpu-server-1 |
| Organization Name | Name of the associated organization | ABC Corp |
| Model | Hardware model of the device | PowerEdge R750 |
| Manufacturer | Device manufacturer (e.g., NVIDIA) | Dell |
| Serial Number | Unique hardware serial number | SN1234567890 |
| Device Type | Type of physical device (e.g., SERVER) | SERVER |
| Allocation Status | AVAILABLE or ALLOCATED | AVAILABLE |
Authentication¶
| Field | Description | Example |
|---|---|---|
| Username | Login username | admin |
| Password | Login password | ******** |
Power Management¶
| Field | Description | Example |
|---|---|---|
| BMC IP | BMC management IP | 192.168.1.10 |
| BMC Username | BMC login username | root |
| BMC Password | BMC login password | ******** |
Resource Configuration¶
| Field | Description | Example |
|---|---|---|
| Total CPU | Total number of CPU cores | 64 |
| Total Memory (MB) | RAM available in megabytes | 262144 |
| Total Storage (GB) | Local disk capacity in GB | 2048 |
Tags¶
The Tags tab allows users to apply metadata to a server to help categorize and filter servers effectively.
There are two types of tags:
- System Tags: These are managed internally by the platform and cannot be edited by the user. Example:
priority: qe - Tags: These are user-defined key-value pairs. Users must provide both the key and value to add a tag.
Click Add Tags to enter the following:
| Field | Description | Example |
|---|---|---|
| Key | The tag name or identifier | env |
| Value | The value associated with the key | prod |
Note: Both the key and value fields are mandatory. An error is shown if either field is left blank.
Node Onboarding¶
Automatic node onboarding provides a streamlined method to register newly provisioned nodes into the platform. When nodes are deployed with the required agent and labeled with the vmaas-node-onboarding tag, the platform detects and initiates the onboarding workflow without manual steps.
This capability is useful in environments where nodes are frequently created or refreshed, such as large-scale deployments or automated infrastructure pipelines. It helps maintain consistency, reduces configuration errors, and improves operational efficiency by eliminating repetitive onboarding tasks.
This feature is primarily used by platform administrators, infrastructure teams, and managed service operators who maintain fleets of compute resources and require standardized enrollment behavior across environments.
- Add Node Onboarding Tag to Server
A client-specific tag is used to trigger the automatic onboarding workflow. The tag name is determined by the onboarding template associated with the environment. For example, when using the default onboarding template, the tag vmaas-node-onboarding=true is used to indicate that the server should be onboarded.
| Tag Key | Value | Purpose |
|---|---|---|
vmaas-node-onboarding |
true |
Marks the server for onboarding workflow execution. |
Note: The exact tag name may differ based on customer-specific environment or template configurations.
- Configure Global Settings
Global settings define the onboarding template and required variables.
agents:
- edge-onboarding-agent
deviceonboarding:
template:
name: vmaas-system-node-onboarding
version: v3-node-onboarding
overrides:
variables:
"Partner API Key": <client-specific-partner-api-key>
"Ops Console Endpoint": <ops-console-endpoint>
"Processing Type": inventory-page
| Parameter | Description |
|---|---|
| Partner API Key | Authorization key used during onboarding. |
| Ops Console Endpoint | Endpoint for console communication. |
| Processing Type | Defines processing behavior for the onboarding workflow. |
- Trigger Node Onboarding
Navigation: Data Centers → Servers → Actions → Node Onboarding
This executes the onboarding workflow using:
- Onboarding agent
- Onboarding template
-
Variables from global settings
-
Automatic Host Tag Assignment
When onboarding completes, a host identifier tag is automatically added to the server.
Example:
| Tag Key | Value | Meaning |
|---|---|---|
vmaas-onboarded |
true |
Indicates successful onboarding and maps the server to a host profile. |
Once onboarding is completed, select Node Onboarding again for the server to view the onboarding status, device identifier and partner identifier details.
Interfaces¶
The Interfaces tab lists network interface details. Click Add Interface, fill in the required fields, and then click Add to save the entry.
| Field | Description | Example |
|---|---|---|
| Interface Name | Name of the network interface | eth0 |
| MAC Address | MAC address of the interface | 00:1A:2B:3C:4D:5E |
| IP Address | Assigned IP address | 10.0.0.5 |
| Label | Custom label (optional) | Primary NIC |
| Connecting Switch | Name of the connected switch | core-switch-01 |
| Switch Port | Port used on the switch | Gig1/0/24 |
GPU(s)¶
The GPU(s) tab allows you to add or view GPU assignments for the server. One or more GPUs can be attached to a single server.
Click Add GPU to input:
| Field | Description | Example |
|---|---|---|
| Model No | GPU model number | A100 |
| PCIe ID | PCIe identifier of the GPU | 0000:36:00.0 |
| Vendor Code | Identifier for the GPU vendor | 10de |
| UUID | Unique identifier for the GPU | GPU-f3f716ed |
| Type | Assignment type: - PASSTHROUGH (full GPU to one VM), - MIG (split GPU into instances), - VGPU (shared GPU across VMs) |
PASSTHROUGH |
| VM Reference | ID of the VM if the GPU is currently attached to a virtual machine | 0xa8789 |
At the top of the GPU tab, users can track the allocated and unallocated GPU count in real time.
VM(s)¶
The VM(s) tab displays the virtual machines associated with the selected server. One or more VMs can be associated with a single server.
❗ Important: VM creation is only supported via API. The UI allows viewing details of VMs already associated with the server.
Below is an example of a VM already linked to a server:
| Field | Description | Example |
|---|---|---|
| VM Name | Name of the virtual machine | paas-hello-vm |
| IP Address | IP assigned to the VM | 192.168.1.110 |
| Instance ID | VM instance ID | i-abcxyz |
| CPU Cores | CPU cores allocated | 4 |
| Memory (MB) | RAM allocated to the VM | 8192 |
| Storage (GB) | Storage allocated | 50 |
| Workspace ID | Associated workspace | 4qkolkn |
| Organization ID | Owning organization | 4qkolkn |
| Project ID | Project under which the VM runs | 4qkolkn |
| Partner ID | Partner reference | rx280ml |
Allocated and unallocated VM counts for the server are shown at the top of the tab.
Once all configuration tabs are completed, click Update Server to save changes for an existing server, or click Add Server to create a new server.
Bulk Upload Using CSV¶
To onboard multiple servers efficiently, use the Download Template and Upload CSV options available on the Servers page.
- Click Download Template to get a pre-formatted CSV file with all the required columns.
- Open the CSV file and enter server details such as:
- Name
- Model
- IP Address
- MAC Address
- Device Type
- Resource configuration, etc.
- Save the file with a
.csvextension. - Return to the Servers page and click Upload CSV.
- Select the updated file and confirm the upload.
This flow streamlines bulk onboarding of servers and is especially helpful during environment scale-outs, hardware migrations, or initial setup.
Best Practices¶
- Keep server records up-to-date
- Use tags and system tags consistently
- Regularly audit inventory for unused or outdated servers
- Remove decommissioned servers from the inventory