Skip to content

Chassis Profile

A 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
NameTypeConstraintMandatoryDefault Value
intersightClassintersightNo

NameTypeConstraintMandatoryDefault Value
organizationsListorganizationsNo

NameTypeConstraintMandatoryDefault Value
profilesClassprofilesNo

profiles (compute.intersight.organizations)

Section titled “profiles (compute.intersight.organizations)”
NameTypeConstraintMandatoryDefault Value
chassisListchassisNo

chassis (compute.intersight.organizations.profiles)

Section titled “chassis (compute.intersight.organizations.profiles)”
NameTypeConstraintMandatoryDefault Value
nameStringRegex: ^[a-zA-Z0-9_.:-]{1,64}$Yes
descriptionStringNo
managedBooleantrue, falseNotrue
actionChoicenone, deploy, unassignNonone
wait_for_completionBooleantrue, falseNofalse
tagsListtagsNo
serial_numberStringNo
chassis_templateStringNo
certificate_management_policyStringNo
imc_access_policyStringNo
power_policyStringNo
snmp_policyStringNo
thermal_policyStringNo

tags (compute.intersight.organizations.profiles.chassis)

Section titled “tags (compute.intersight.organizations.profiles.chassis)”
NameTypeConstraintMandatoryDefault Value
keyStringYes
valueStringNo
typeChoiceKeyValue, PathTagNo

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:

ValueDeploy to hardwareSafe to leave permanently
none (default)NoYes
deployYesYes
unassignDetaches the profile from the chassisNo — 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_number does not unassign the profile in Intersight. assigned_chassis is 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 though terraform apply succeeds cleanly. To actually detach the hardware, set action: 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’s wait_for_completion at destroy time reflects whatever action and wait_for_completion were set to on the last apply before removal, not a hardcoded wait like the server profile resource. Prefer explicit action: unassign before removing a chassis entry, rather than relying on destroy alone.

Reboot risk: deploy will 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 running terraform apply with action: deploy against a production chassis.

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.

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: prod

Example-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: FDO2312ABCD

Example-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: deploy

Example-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