Create Expected Rack
Create an Expected Rack to pre-register a rack expected to be discovered at a Site. The rackId is an operator-supplied string identifier (not a UUID) that uniquely identifies the rack 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 Racks 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 (string, not UUID). Must be non-empty and unique within the Site.
Human-readable name of the Expected Rack
Human-readable description of the Expected Rack
User-defined key-value pairs for organizing and categorizing Expected Racks. Well-known keys (chassis.*, location.*) are used to convey chassis identity and physical location.
Ignored compatibility field. Core derives the profile from the matching ExpectedRackGroup; omit this field.
Response
Unique identifier (UUID) for the Expected Rack
Operator-supplied identifier for the rack (string, not UUID). Unique within a Site.
External rack group ID selected and persisted at creation together with rackProfileId. Null for legacy rows without a recorded group; metadata updates preserve it.
Human-readable name of the Expected Rack
Human-readable description of the Expected Rack
User-defined key-value pairs for organizing and categorizing Expected Racks. Well-known keys (chassis.*, location.*) are used to convey chassis identity and physical location.