Traditionally, quotas are a bit inconsistent in openstack.
Likewise, the openstack terraform provider is also a bit inconsistent in how to work with quotas.
See:
- https://registry.terraform.io/providers/terraform-provider-openstack/openstack/latest/docs/resources/compute_quotaset_v2
- https://registry.terraform.io/providers/terraform-provider-openstack/openstack/latest/docs/resources/networking_quota_v2
- https://registry.terraform.io/providers/terraform-provider-openstack/openstack/latest/docs/resources/blockstorage_quotaset_v2 <-- marked as deprecated, but with no known replacement
- no known way to control trove quotas, see also https://wikitech.wikimedia.org/wiki/Portal:Cloud_VPS/Admin/Trove#Adjusting_per-project_Trove_quotas
In general, quotas need to be linked to a project, so we need to get T371393: Cloud VPS: extend tofu-infra to cover projects, users and roles done first.