Replace all Expected Machines
Replace the complete Expected Machine set for one Site. Entries omitted from the request are deleted, and entries in the request are created with new REST IDs. The expectedMachines array may be empty to clear the Site’s set.
Every entry must use the top-level siteId. BMC MAC addresses and chassis serial numbers must be unique within the replacement set. Referenced SKUs must exist at the Site.
Org must have an Infrastructure Provider entity and the caller must have Provider Admin access, or the caller must be a Tenant Admin with effective TargetedInstanceCreation access to the Site.
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
Full desired Expected Machine set; BMC MAC addresses and chassis serial numbers must be unique
Response
MAC address of the Expected Machine’s BMC (Baseboard Management Controller)
Serial numbers of the Expected Machine’s fallback DPUs (Data Processing Units)
SKU information for this Expected Machine (populated when includeRelation=Sku is specified)
Machine information for this Expected Machine (populated when includeRelation=Machine is specified)
Optional BMC IP address (IPv4 or IPv6). When set, pre-allocates a reserved IP for the BMC.
When true, this host is eligible for DPF-based provisioning. Returns the effective setting: true when no value is configured. An explicitly configured false value is returned as false.
User-defined key-value pairs for organizing and categorizing Expected Machines
Optional per-host lifecycle profile