Loosely speaking, resource pools are similar to OpenStack projects the way I see it. And those were originally introduced for multi-tenancy and resource pooling associated with that (in addition to identity and RBAC).
You would use them to separate nodes that different people use for different purposes.
For example:
1) resource pool 1: nodes in DC pods [0, 2] - Cloud Region 1;
2) resource pool 2: nodes in DC pods [3, 5] - Cloud Region 2;
3) resource pool 3: John Doe's NUC playground.
You may have a different set of availability zones for each resource pool but not necessarily (similar to how network spaces may span fabrics - those are just different concepts).
rharding,
Loosely speaking, resource pools are similar to OpenStack projects the way I see it. And those were originally introduced for multi-tenancy and resource pooling associated with that (in addition to identity and RBAC).
You would use them to separate nodes that different people use for different purposes.
For example:
1) resource pool 1: nodes in DC pods [0, 2] - Cloud Region 1;
2) resource pool 2: nodes in DC pods [3, 5] - Cloud Region 2;
3) resource pool 3: John Doe's NUC playground.
You may have a different set of availability zones for each resource pool but not necessarily (similar to how network spaces may span fabrics - those are just different concepts).