{ "additionalProperties": false, "extends": { "$ref": "DiscoveredResource }, "id": "ComputeCollection", "module_id": "InventoryCmObj", "properties": { "_last_sync_time": { "$ref": "EpochMsTimestamp, "can_sort": true, "description": "Timestamp of last modification", "readonly": true }, "_links": { "description": "The server will populate this field when returing the resource. Ignored on PUT and POST.", "items": { "$ref": "ResourceLink }, "readonly": true, "title": "References related to this resource", "type": "array" }, "_schema": { "readonly": true, "title": "Schema for this resource", "type": "string" }, "_self": { "$ref": "SelfResourceLink, "readonly": true, "title": "Link to this resource" }, "cm_local_id": { "readonly": true, "required": true, "title": "Local Id of the compute collection in the Compute Manager", "type": "string" }, "description": { "can_sort": true, "maxLength": 1024, "title": "Description of this resource", "type": "string" }, "display_name": { "can_sort": true, "description": "Defaults to ID if not set", "maxLength": 255, "title": "Identifier to use when displaying entity in logs or GUI", "type": "string" }, "dpu_config": { "$ref": "ClusterDpuConfig, "description": "Specifies property related to cluster homogeneity for SmartNic", "readonly": true, "required": false, "title": "Configuration of homogeneous cluster" }, "external_id": { "readonly": true, "required": true, "title": "External ID of the ComputeCollection in the source Compute manager,\ne.g. mo-ref in VC\n", "type": "string" }, "origin_id": { "readonly": true, "required": true, "title": "Id of the compute manager from where this Compute Collection was discovered", "type": "string" }, "origin_properties": { "items": { "$ref": "KeyValuePair }, "readonly": true, "required": false, "title": "Key-Value map of additional specific properties of\ncompute collection in the Compute Manager\n", "type": "array" }, "origin_type": { "readonly": true, "required": true, "title": "ComputeCollection type like VC_Cluster. Here the Compute Manager\ntype prefix would help in differentiating similar named Compute\nCollection types from different Compute Managers\n", "type": "string" }, "owner_id": { "readonly": true, "required": false, "title": "Id of the owner of compute collection in the Compute Manager", "type": "string" }, "owner_nsx": { "description": "Specifies owner nsx of the compute collection. Owner nsx can be SELF, OTHER, MULTIPLE or NONE. SELF applies to when compute collection prepared by that nsx. OTHER applies to when compute collection prepared by other nsx. MULTIPLE applies to when compute collection tried to prepare by multiple nsx at a time. NONE applies to when compute collection is not prepared by any nsx.", "enum": [ "SELF", "OTHER", "MULTIPLE", "NONE" ], "readonly": true, "required": false, "title": "Specifies owner nsx of the compute collection", "type": "string" }, "resource_type": { "description": "The type of this resource.", "readonly": false, "required": true, "type": "string" }, "scope": { "description": "Specifies list of scope of discovered resource. e.g. if VHC path is associated with principal identity, who owns the discovered resource, then scope id will be VHC path and scope type will be VHC.", "items": { "$ref": "DiscoveredResourceScope }, "readonly": false, "required": false, "title": "List of scopes for discovered resource", "type": "array" }, "tags": { "items": { "$ref": "Tag }, "maxItems": 30, "title": "Opaque identifiers meaningful to the API user", "type": "array" } }, "type": "object" }