-
- Downloads
Missing configuration for Trove single tenant
The nova_proxy_* options are not needed when Trove single tenant functionnality is not used. The current way how Kolla configure trove-taskmanager.conf is to use the user tenant so the nova_proxy_* options are not required by default. I added the "enable_trove_singletenant" option to enable the single tenant functionnality if required and complete the configuration to make it works. When enable_trove_singletenant is true, the below configuration will be applied to trove-task-manager.conf configuration file: nova_proxy_admin_pass = {{ trove_keystone_password }} nova_proxy_admin_tenant_name = services nova_proxy_admin_user = 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 Change-Id: I9858acd9486a3f6a07c1edad14fde12f49df772b Closes-Bug: #1743394
Showing
- ansible/group_vars/all.yml 1 addition, 0 deletionsansible/group_vars/all.yml
- ansible/roles/trove/templates/trove-taskmanager.conf.j2 5 additions, 0 deletionsansible/roles/trove/templates/trove-taskmanager.conf.j2
- etc/kolla/globals.yml 1 addition, 0 deletionsetc/kolla/globals.yml
- releasenotes/notes/add-trove-singletenant-dd02a7b7cc1a4f99.yaml 6 additions, 0 deletions...enotes/notes/add-trove-singletenant-dd02a7b7cc1a4f99.yaml
Loading
Please register or sign in to comment