legacy "tenant" terminology still used interchangeably with "project"

[Lily Xing]

When moving to the new version of keystone, table 'tenant' is renamed to 'project', but the information in 'extra' field of table 'user' is still using the old name 'tenantId', which confused me when I moved to the new version first time.

[Dolph Mathews (dolph)]

Is this causing a failure of any kind, or is it just non-intuitive and should be migrated? I'd like to raise the priority if it's causing a failure.

[Lily Xing (llxing)]

Dolph,

I think it's the latter. No failure. But maybe it's better if someone
can clear the usage of term 'project' and 'tenant' in keystone rather
than just this one.

Thanks.

On 08/28/2013 09:06 PM, Dolph Mathews wrote:
> Is this causing a failure of any kind, or is it just non-intuitive and
> should be migrated? I'd like to raise the priority if it's causing a
> failure.
>
> ** Changed in: keystone
> Status: New => Triaged
>
> ** Changed in: keystone
> Importance: Undecided => Low
>

--

Best regards,
Lily Xing(邢莉莉)

Phone: [phone]

[Dolph Mathews (dolph)]

Agree; usage of the term "tenant" in keystone should be isolated to v2 controllers, while "project" is used everywhere else.

[Dolph Mathews (dolph)]

Unassigning to due inactivity