In the case of trove, we follow service configuration as per the
official manual installation documentation [1].
It uses trove_for_trove_usage as a service tenant unlike other openstack
services which uses default service tenant. For any project service to
work, the configuration [keystone_authtoken] section should be updated
with the correct user, project, tenant and password.
Proposed change fixes this issue so Trove service configurations are
aligned with the trove admin user settings for tenant and password.
[1]: http://docs.openstack.org/developer/trove/dev/manual_install.html
Closes-bug: #1644079
Change-Id: I92a426132e20669731bc65526b20f60a3f34b348
eefe3d66c1