| Field |
Required |
Accessor |
Description |
|
name
|
|
— |
Name
|
|
status
|
|
— |
Operational status
| Import Value |
Label |
| offline |
Offline |
| active |
Active |
| planned |
Planned |
| staged |
Staged |
| failed |
Failed |
| decommissioning |
Decommissioning |
|
|
role
|
—
|
name |
Functional role
|
|
site
|
—
|
name |
Assigned site
|
|
cluster
|
—
|
name |
Assigned cluster
|
|
device
|
—
|
name |
Assigned device within cluster
|
|
tenant
|
—
|
name |
Assigned tenant
|
|
platform
|
—
|
name |
Assigned platform
|
|
vcpus
|
—
|
— |
VCPUs
|
|
memory
|
—
|
— |
Memory (MB)
|
|
disk
|
—
|
— |
Disk (MB)
|
|
description
|
—
|
— |
Description
|
|
serial
|
—
|
— |
Serial number
|
|
config_template
|
—
|
name |
Config template
|
|
comments
|
—
|
— |
Comments
|
|
tags
|
—
|
slug |
Tag slugs separated by commas, encased with double quotes (e.g. "tag1,tag2,tag3")
|
|
id
|
—
|
— |
Numeric ID of an existing object to update (if not creating a new object)
|
Required fields must be specified for all objects.
Related objects may be referenced by any unique attribute. For example, vrf.rd would identify a VRF by its route distinguisher.