Create Expected Rack Group
Create an Expected Rack Group to declare racks and devices at a Site. The rackGroupId is an opaque operator-supplied string identifier (UUID syntax is not required) that uniquely identifies the group within the Site.
Org must have an Infrastructure Provider entity. User must have authorization role with PROVIDER_ADMIN suffix.
Alternatively, Tenant Admins with TargetedInstanceCreation capability can also create Expected Rack Groups if they have an account with the Site’s Infrastructure Provider.
Chassis identity and physical location information are conveyed via well-known label keys in labels:
chassis.manufacturer,chassis.serial-number,chassis.modellocation.region,location.datacenter,location.room,location.position
Authentication
export JWT_BEARER_TOKEN="<jwt-bearer-token>"
# Example org name: "acme-inc
export ORG_NAME=<org-name>
# Use the JWT bearer token in your API request auth header:
curl -v -X GET -H "Content-Type: application/json" -H "Authorization: Bearer $JWT_BEARER_TOKEN" https://nico-rest-api.nico.svc.cluster.local/v2/org/$ORG_NAME/nico/user/current
Path parameters
Request
Operator-supplied identifier for the rack group (opaque string; UUID syntax is not required). Must be non-empty and unique within the Site.
External group-level NVLink topology identifier, non-blank and at most 128 characters.
Rack fabric protocol, non-blank and at most 128 characters. NVLINK_V6 enables GB-to-VR profile topology normalization.
Ordered racks and their devices. Rack IDs and device identity tuples must be unique across the group, with case-sensitive comparison. A provided array replaces the complete list; on PATCH, omission or null preserves it and [] clears it. On create, omission or null supplies an empty list.
ASCII human-readable name, at most 256 characters. An empty string is allowed.
Human-readable description, at most 1024 UTF-8 bytes. An empty string is allowed.
User-defined key-value pairs with ASCII keys and Unicode values, each at most 255 UTF-8 bytes. Well-known keys (chassis.*, location.*) are used to convey chassis identity and physical location.
Response
Unique identifier (UUID) for the Expected Rack Group
Operator-supplied identifier for the rack group (opaque string; UUID syntax is not required). Unique within a Site.
Site details when requested through includeRelation; otherwise null.
External group-level NVLink topology identifier.
Ordered racks and their devices. Arrays are always present, including empty lists. Rack IDs and device identity tuples are unique across the group, with case-sensitive comparison.
Human-readable name of the Expected Rack Group
Human-readable description of the Expected Rack Group
User-defined key-value pairs for organizing and categorizing Expected Rack Groups. Well-known keys (chassis.*, location.*) are used to convey chassis identity and physical location.