broker-pool-manipulate¶

Task to allocate/deallocate machines from a pool

Drives machine allocation via the DRP pooling APIs on behalf of a Pool Broker.

Two operational modes, selected by broker-pool/allocate:

• broker-pool/allocate: false (default) — add/remove: the broker creates a per-cluster pool whose ParentPool is broker-pool/pool and moves machines into it on create. Each add pushes the source pool onto the allocated machine's broker-pool/pool-stack. On destroy (or cluster-update remove), the broker pops each machine's stack and routes the machine back to the popped pool; this supports chained Pool Broker use where a machine passed through several pools on its way into the cluster. For machines with an empty or missing stack, ParentPool inheritance is the fallback.

  Per-cluster pools are NOT deleted when the cluster is removed, in case secondary configuration has been added to them.

• broker-pool/allocate: true — allocate/release: machines remain in the shared broker-pool/pool for the lifetime of the cluster and no per-cluster pool is created. No pool-stack is maintained. Use this when multiple clusters should draw from a single shared pool without fragmenting it.

broker-pool/pool defaults to default.

The default of broker-pool/allocate was changed from true to false in v4.16 so that Pool Broker matches Context Broker behavior (see rackn/product-backlog#785).

Objects that Reference broker-pool-manipulate¶

Not used in current content packs

Objects used by broker-pool-manipulate¶

• templates setup.tmpl
• params cluster/profile
• params broker-pool/pool
• params cluster/destroy
• params broker-pool/return-workflow
• params broker-pool/return-pipeline
• params broker-pool/allocate
• params cluster/machines
• params broker/set-workflow
• params broker/set-pipeline
• params broker/set-icon
• params broker/set-color