Server

Servers are the central anchor of the compute data model. Each server entry associates a physical UCS server with a profile template and triggers provisioning through Intersight or Redfish. Servers are identified by serial number for direct assignment, or by a resource pool when hardware is allocated dynamically.

Diagram

Classes

compute

Name	Type	Constraint	Mandatory	Default Value
servers	List	[servers]	No

servers (compute)

Name	Type	Constraint	Mandatory	Default Value
name	String		Yes
provisioning	Class	[provisioning]	No

provisioning (compute.servers)

Name	Type	Constraint	Mandatory	Default Value
managed_by	Choice	intersight, redfish	Yes
profile_template	String		Yes
managed	Boolean	true, false	No	true
intersight	Class	[intersight]	No

intersight (compute.servers.provisioning)

Name	Type	Constraint	Mandatory	Default Value
organization	String		Yes
serial_number	String		No
resource_pool	String		No

Examples

Example-1: The example below demonstrates two servers assigned to the same profile template, each identified by a unique serial number.

compute:
  servers:
    - name: node-01
      provisioning:
        managed_by: intersight
        profile_template: web-server-template
        intersight:
          organization: MyOrganization
          serial_number: FCH2345V0AB

    - name: node-02
      provisioning:
        managed_by: intersight
        profile_template: web-server-template
        intersight:
          organization: MyOrganization
          serial_number: FCH2345V0AC

Example-2: The example below demonstrates a server provisioned from a resource pool, useful when the specific hardware has not yet been determined at design time.

compute:
  servers:
    - name: node-03
      provisioning:
        managed_by: intersight
        profile_template: web-server-template
        intersight:
          organization: MyOrganization
          resource_pool: server-pool-a