Chassis Profile
IntersightA Chassis Profile binds a set of policies to a physical UCS Chassis, identified by its serial number. It can be created standalone with direct policy assignments, or derived from a Chassis Template which pre-wires the policies.
Location in Intersight GUI:
Profiles » UCS Chassis Profiles
Diagram
Section titled “Diagram”Classes
Section titled “Classes”compute
Section titled “compute”| Name | Type | Constraint | Mandatory | Default Value |
|---|---|---|---|---|
| intersight | Class | intersight | No |
intersight (compute)
Section titled “intersight (compute)”| Name | Type | Constraint | Mandatory | Default Value |
|---|---|---|---|---|
| organizations | List | organizations | No |
organizations (compute.intersight)
Section titled “organizations (compute.intersight)”| Name | Type | Constraint | Mandatory | Default Value |
|---|---|---|---|---|
| profiles | Class | profiles | No |
profiles (compute.intersight.organizations)
Section titled “profiles (compute.intersight.organizations)”| Name | Type | Constraint | Mandatory | Default Value |
|---|---|---|---|---|
| chassis | List | chassis | No |
chassis (compute.intersight.organizations.profiles)
Section titled “chassis (compute.intersight.organizations.profiles)”| Name | Type | Constraint | Mandatory | Default Value |
|---|---|---|---|---|
| name | String | Regex: ^[a-zA-Z0-9_ | Yes | |
| description | String | No | ||
| managed | Boolean | true, false | No | true |
| action | Choice | none, deploy, unassign | No | none |
| wait_ | Boolean | true, false | No | false |
| tags | List | tags | No | |
| serial_number | String | No | ||
| chassis_ | String | No | ||
| certificate_ | String | No | ||
| imc_ | String | No | ||
| power_policy | String | No | ||
| snmp_policy | String | No | ||
| thermal_policy | String | No |
tags (compute.intersight.organizations.profiles.chassis)
Section titled “tags (compute.intersight.organizations.profiles.chassis)”| Name | Type | Constraint | Mandatory | Default Value |
|---|---|---|---|---|
| key | String | Yes | ||
| value | String | No | ||
| type | Choice | KeyValue, PathTag | No |
Action Attribute
Section titled “Action Attribute”The action attribute controls what Terraform does beyond creating and assigning the chassis profile. Chassis profiles have no template-sync mechanism in the Intersight provider, so only three values are supported:
| Value | Deploy to hardware | Safe to leave permanently |
|---|---|---|
none (default) | No | Yes |
deploy | Yes | Yes |
unassign | Detaches the profile from the chassis | No — set temporarily |
none — Terraform creates the chassis profile and assigns it to the chassis, then stops. No configuration is pushed to hardware. Use this to stage profiles for operator review before committing.
deploy — Terraform deploys the current profile state to the physical chassis, pushing the assigned power, thermal, and SNMP policies. Safe to leave permanently because Terraform only re-deploys when the data model changes, not on a fixed schedule.
unassign — Terraform sends an explicit Unassign command to Intersight, detaching the profile from the chassis. action has no one-shot marker for this value — it is sent on every apply where it is set (the same convention deploy already follows here, and the same convention server and domain profiles follow for their own unassign), so set it, apply, then set action back to none (the same caution already given for other values with no standing-state guarantee). See the warning below before using this: in most cases, removing the chassis profile’s entry from the data model entirely (so Terraform destroys the profile) is the better, more reliable path — but see the caveat below, since chassis destroy-time waiting is less predictable than for server or domain profiles.
Warning: Commenting out or removing
serial_numberdoes not unassign the profile in Intersight.assigned_chassisis a provider-managed (optional + computed) attribute — when its underlying config block disappears, Terraform has no opinion on it and simply keeps the provider’s last-known value, so no detach is ever sent. The GUI continues to show the profile bound to its original chassis even thoughterraform applysucceeds cleanly. To actually detach the hardware, setaction: unassign(above). Removing the chassis profile’s entire entry to let Terraform destroy it is not guaranteed to wait for the Unassign workflow — this resource’swait_for_completionat destroy time reflects whateveractionandwait_for_completionwere set to on the last apply before removal, not a hardcoded wait like the server profile resource. Prefer explicitaction: unassignbefore removing a chassis entry, rather than relying on destroy alone.
Reboot risk:
deploywill not reboot the chassis itself, but changes to policies affecting IO module or power redundancy behavior may briefly disrupt chassis-level services. Verify the assigned policies before runningterraform applywithaction: deployagainst a production chassis.
wait_for_completion
Section titled “wait_for_completion”When action is deploy, deployment is an asynchronous job in Intersight. Setting wait_for_completion: true causes terraform apply to block until the chassis reports OK, which can take several minutes. When false (default), Terraform returns immediately after triggering the job and the chassis continues deploying in the background.
Examples
Section titled “Examples”Example-1: Chassis profile derived from a template, assigned to a physical chassis with environment tags.
compute: intersight: organizations: - name: MyOrg profiles: chassis: - name: prod-chassis-01 description: Production UCS Chassis chassis_template: prod-chassis-template serial_number: FOX2344ABCD tags: - key: env value: prodExample-2: Standalone chassis profile with direct policy assignments.
compute: intersight: organizations: - name: MyOrg profiles: chassis: - name: lab-chassis-01 power_policy: lab-power snmp_policy: global-snmp thermal_policy: lab-thermal serial_number: FDO2312ABCDExample-3: Chassis profile deployed to hardware on apply.
compute: intersight: organizations: - name: MyOrg profiles: chassis: - name: prod-chassis-02 chassis_template: prod-chassis-template serial_number: FOX2344EFGH action: deployExample-4: Detaching a chassis from its profile — set action: unassign, apply, then set action back to none. The profile and its data model entry remain; only the hardware assignment is removed.
compute: intersight: organizations: - name: MyOrg profiles: chassis: - name: prod-chassis-01 chassis_template: prod-chassis-template serial_number: FOX2344ABCD action: unassign