Openstack service tenant name in MOS different from Openstack Upstream.

[Ayrat KHAYRETDINOV]

Openstack service tenant name in MOS different from Openstack Upstream.

We want to confirm if this behaviour is bug or just specific to MOS.

According to Openstack docs, http://docs.openstack.org/juno/install-guide/install/yum/content/keystone-users.html, service
tenant name is "service" and will look something like following:

#keystone tenant-get service
+-------------+----------------------------------+
| Property | Value |
+-------------+----------------------------------+
| description | |
| enabled | True |
| id | f12342a17806488f892a73bb8de5aaaa|
| name | service |
+-------------+----------------------------------+

And in MOS/Fuel 6.1 for example it is "services":
#keystone tenant-get services
+-------------+-----------------------------------+
| Property | Value |
+-------------+-----------------------------------+
| description | Tenant for the openstack services |
| enabled | True |
| id | d09b9514d67d4696bc2b6675b7bf6bda |
| name | services |
+-------------+-----------------------------------+

We understand that this is minor problem, though it affected our Migration tools as it is expected that "service" is default name.

[Timur Nurlygayanov (tnurlygayanov)]

Workaround:
We can create new service user and then reconfigure all OpenStack components to use this new user/tenant - so, it is easy to fix it manually if some user want to migrate some resources.

[Vitaly Sedelnik (vsedelnik)]

Puppet team, please check if it makes sense to change service tenant name

[Denis Egorenko (degorenko)]

It seems like we can do this and i have only one doubt for this case:

if we will have upgrade from fuel-7.0 to fuel-8.0, could this change cause problems during upgrading?

[Oleg S. Gelbukh (gelbuhos)]

Changing name of this tenant between releases will require modification of the upgrade procedure. Currently we replicate DB data 'as is', and Fuel generates configurations for services based on deployment parameters. If new version of Fuel has 'service', and in DB it will be 'service', OpenStack components won't be able to authenticate with Keystone.

The exact name is not as important as that it is consistent across releases.

Note that currently deployment engineer can change the name of service tenant using deployment facts (although not directly) at the deployment time.

I would mark this as Won't Fix unless there are very good reasons to implement this change that I overlooked.