Comment 5 for bug 1792943

I think it's important to distinguish them from regions as regions of a cloud are roughly sets of endpoints providing independent control planes (and data planes in most cases).

For example, in OpenStack, every endpoint in a catalog has a region_id foreign key and the same Keystone catalog can be used to store endpoints of multiple control planes backed by separate databases and message queues. Region ID acts as a multiplexor for endpoints when specified in client connection parameters.

mysql> select id, region_id, url from endpoint;
# ...
| 048cd95ba5b84e51a9f79d8b15e9edea | RegionOne | http://openstack.local:80/swift|
| 05ea110348d44efe8ce8e9668309e00f | RegionOne | http://openstack.local:8774/v2/$(tenant_id)s|
| 08695cb91c1a4915a6a4b797ec9607f2 | RegionOne | http://openstack.local:8774/v2/$(tenant_id)s
# ...

In contrast, resource pools provide a way to logically group nodes within a single control plane without any MAAS API isolation.