Skip to content

Resource Pool

A Resource Pool defines a collection of compute resources (rack or blade servers) that can be automatically assigned to server profiles. Rather than pinning a profile to a specific serial number, a resource pool allows Intersight to allocate any available server from the pool, enabling flexible and dynamic server provisioning.

Location in Intersight GUI: Pools » Resource

Diagram
NameTypeConstraintMandatoryDefault Value
intersightClassintersightNo

NameTypeConstraintMandatoryDefault Value
organizationsListorganizationsNo

NameTypeConstraintMandatoryDefault Value
poolsClasspoolsNo

NameTypeConstraintMandatoryDefault Value
resourceListresourceNo

resource (compute.intersight.organizations.pools)

Section titled “resource (compute.intersight.organizations.pools)”
NameTypeConstraintMandatoryDefault Value
nameStringRegex: ^[a-zA-Z0-9_.:-]{1,64}$Yes
descriptionStringNo
managedBooleantrue, falseNotrue
tagsListtagsNo
pool_typeChoiceStatic, Dynamic, HybridNoStatic
resource_typeChoiceServer, Mixed, NoneNoNone
target_platformChoiceStandalone, FIAttached, UnifiedEdgeServerNo
selectorsListString[Regex: ^(/api/v1/.+)?$]No
qualification_policyStringNo

tags (compute.intersight.organizations.pools.resource)

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

Note: pool_type: Dynamic and Hybrid are fully supported, provided a qualification_policy is linked to the pool: Intersight only evaluates a pool dynamically once a Qualification Policy is associated with it via the pool’s qualification_policy field. Setting pool_type: Dynamic with selectors but no qualification_policy will not persist — Intersight silently reverts the pool to Static and clears its selectors. Hybrid pools contain a mix of resources added manually (statically) and resources added automatically by the linked Qualification Policy’s matching conditions.

Example-1: Static resource pool of rack servers for standalone server profile assignment, including tags.

compute:
intersight:
organizations:
- name: MyOrganization
pools:
resource:
- name: rack-server-pool
description: Pool of available rack servers
resource_type: Server
target_platform: Standalone
tags:
- key: env
value: prod

Example-2: Static resource pool that explicitly selects specific rack servers by an OData resource filter instead of assigning them individually.

compute:
intersight:
organizations:
- name: MyOrganization
pools:
resource:
- name: selected-rack-pool
resource_type: Server
target_platform: Standalone
selectors:
- "/api/v1/compute/RackUnits?$filter=Model eq 'UCSC-C220-M6S'"

Example-3: Reference a resource pool from a server provisioning entry instead of a fixed serial number.

compute:
servers:
- name: dynamic-node-01
provisioning:
managed_by: intersight
profile_template: web-server-template
intersight:
organization: MyOrganization
resource_pool: rack-server-pool

Example-4: Dynamic resource pool that automatically admits any rack server matched by a Qualification Policy.

compute:
intersight:
organizations:
- name: MyOrganization
policies:
qualification:
- name: any-rack-server
qualifiers:
- qualifier_type: rack_server
user_labels:
- pool-eligible
pools:
resource:
- name: dynamic-rack-pool
pool_type: Dynamic
resource_type: Server
target_platform: Standalone
qualification_policy: any-rack-server