Create an Instance
Create an Instance for Tenant.
Org must have a Tenant entity. User must have authorization role with TENANT_ADMIN suffix.
Authentication
Path parameters
Request
Optional exact-match selector applied to Machine labels during placement. Property names are arbitrary Machine label keys rather than predefined selector fields. Every supplied key/value pair must match (AND semantics). An omitted or empty object does not restrict placement.
A non-empty object requires the Tenant to have effective targetedInstanceCreation capability for the selected Site; otherwise the request is rejected with 403. When instanceTypeId is supplied, NICo selects from Ready, unassigned Machines of that Instance Type that match the selector. When machineId is supplied, the specified Machine must match the selector or the request is rejected with 400. The selector constrains placement only; it is not persisted on the created Instance.
IDs of additional VPCs the Instance should attach to through non-primary interfaces. This field may only be specified when every entry in interfaces uses vpcPrefixId or vpcId. IDs must be unique, must be valid UUIDs, and must not include the primary vpcId.
Can only be specified if allowOverride is set to true in Operating System. Limited to 32768 bytes (32 KiB), measured on the effective value NICo stores rather than the text submitted. Operating System defaults are inherited first, and when phone-home is configured the document is re-serialized with a phone_home block added. Re-serialization normalizes indentation and can grow the document, so a request just under the limit may still be rejected.
Power profile to apply to the Instance. A non-empty value requires the Site’s dpsPowerManagement capability to be true.
User-defined key-value labels
At least one interface must be specified unless autoNetwork is true. Interfaces must all be Subnet-backed or all be VPC-backed; VPC-backed interfaces may use an explicit vpcPrefixId or ask the Controller to select a prefix using vpcId and ipFamilies. Only one network can be attached over a physical interface. If only one Subnet is specified, it will be attached over a physical interface regardless of isPhysical. Mutually exclusive with autoNetwork: when autoNetwork is true this list MUST be empty.
When true, asks NICo to auto-resolve the Instance’s network interfaces from the host’s underlay (HostInband) network segments. Intended for instances on zero-DPU hosts (or hosts with their DPU in NIC mode). When true: (1) the target VPC’s networkVirtualizationType MUST be FLAT, (2) interfaces MUST be empty or omitted, and (3) secondaryVpcIds MUST be empty or omitted. Resolved interfaces surface on the Instance’s read response.
Associate one or more SpectrumX Partitions with this Instance. Each device and deviceInstance pair may appear only once, irrespective of virtualFunctionId.
Define Interfaces to associate Instance GPUs with NVLink Logical Partitions. A subset of GPUs may be specified (it is not required to include all GPUs). Each item references one GPU index (deviceInstance) and one NVLink Logical Partition. Different interfaces may reference different NVLink Logical Partitions.
Response
IDs of VPCs attached to the Instance through non-primary interfaces
User-specified Instance labels
Serial Console URL for the Instance. Format: ssh://<id>@siteSerialConsoleHostname
True when this Instance uses NICo auto-resolved networking from the host’s underlay (HostInband) network segments. When true, the caller’s request interfaces list was empty, this interfaces field remains empty on readback, and the resolved per-interface details surface under status.network.interfaces.
Date/time when the Instance was created
Date/time when the Instance was last updated