-
Notifications
You must be signed in to change notification settings - Fork 95
rename tenant to "project" #982
Comments
I'm not sure if the name "project" is really better than "tenant" :-) This name may cause some confusion in technical communications - what does it mean to "create a project"? It's kind of ambiguous to me. Personally I don't have strong concern about the name "tenant". But if most people think it's inappropriate, I'd prefer "role" or something else. |
from https://github.com/vmware/docker-volume-vsphere/blob/master/docs/features/tenancy.md e.g.
How about having it as my two-cents |
"vm-group" opens up the implementation bellow the docker host, "project"
will match well with the photon platform (they have tenants and projects).
HOw about "host-group"
…On Thu, Mar 2, 2017 at 8:43 AM, Nirdesh Shukla ***@***.***> wrote:
from https://github.com/vmware/docker-volume-vsphere/blob/
master/docs/features/tenancy.md
"vSphere Administrator can define group of one or more Docker Host (VM) as
Tenant"
e.g.
vmdkops_admin.py tenant create --name=tenant1 --vm-list=photon4
How about having it as vm-group? simply it is a logical unit of
dockerHosts to have privileges for datastore.
my two-cents
—
You are receiving this because you are subscribed to this thread.
Reply to this email directly, view it on GitHub
<#982 (comment)>,
or mute the thread
<https://github.com/notifications/unsubscribe-auth/APHseKhpOIPDfJn-PUyfAzUH65C_vHM3ks5rhjP0gaJpZM4MQRte>
.
|
@govint what does "projects" and "tenants" mean in photon platform? I think "host-group" sounds a good name. Any comments @pdhamdhere @msterin |
I agree with @govint here. |
Fixed by #1021 |
"tenant" is perceived as something related to a group of users and is confusing on out context. We need to emphasize that this is a way to limit access and privileges for a set of Vms , supposedly working on the same project. So the suggestion (from @pdhamdhere ) is to name it "project" , instead of "tenant".
this would include :
//CC @lipingxue @shaominchen @pdhamdhere
The text was updated successfully, but these errors were encountered: