Hi Michael,

Is anyone aware of the current state of the "service tenant" deployment model for Trove, and whether it is a viable option; or whether the historical method of customer tenants/projects are still the recommended approach?

Any and all comments/thoughts/gotchas would be most appreciated!

We've had it running in production on the Nectar cloud for the last 12 months. The work I did made it upstream, so you should be right to go from at least Queens.

You'll just need to set something like this in your Trove config:

nova_proxy_admin_user = trove

nova_proxy_admin_pass = <pass>

nova_proxy_admin_tenant_name = trove

remote_nova_client = trove.common.single_tenant_remote.nova_client_trove_admin

remote_cinder_client = trove.common.single_tenant_remote.cinder_client_trove_admin

remote_neutron_client = trove.common.single_tenant_remote.neutron_client_trove_admin

cheers,

Andy