Re: [openstack-dev] [Neutron] Rename tenant to project: discussion

Thanks guys for all the feedback. I'm happy we elaborated some plan for this topic. -- Dariusz Smigiel Intel Technology Poland > On 12/04/2015 04:26 PM, Armando M. wrote: > > > > > > On 4 December 2015 at 10:02, Kevin Benton > > wrote: > > > >

Re: [openstack-dev] [Neutron] Rename tenant to project: discussion

I'm new to this discussion, but you did ask for any feedback, so ... On 03/12/15 18:29, Smigiel, Dariusz wrote: > Hey Neutrinos (thanks armax for this word :), > Keystone is planning to deprecate V2 API (again :). This time in Mitaka [6], > and probably forever. It will stay at least four

Re: [openstack-dev] [Neutron] Rename tenant to project: discussion

On 4 December 2015 at 08:46, Neil Jerram wrote: > I'm new to this discussion, but you did ask for any feedback, so ... > > On 03/12/15 18:29, Smigiel, Dariusz wrote: > > Hey Neutrinos (thanks armax for this word :), > > Keystone is planning to deprecate V2 API (again

Re: [openstack-dev] [Neutron] Rename tenant to project: discussion

ne say anything?" Neil From: Armando M. <arma...@gmail.com> Sent: 04 December 2015 21:01 To: OpenStack Development Mailing List (not for usage questions) Subject: Re: [openstack-dev] [Neutron] Rename tenant to project: discussion On 4 December

Re: [openstack-dev] [Neutron] Rename tenant to project: discussion

On Fri, Dec 4, 2015 at 1:28 PM, Henry Gessau wrote: > Kevin Benton wrote: > > So obviously the stuff in the client can be updated since most of that is > > user-facing. However, on the server side maybe we can start out by > keeping all > > of the internal

Re: [openstack-dev] [Neutron] Rename tenant to project: discussion

> On Dec 4, 2015, at 12:40 PM, Kyle Mestery wrote: > > On Fri, Dec 4, 2015 at 1:28 PM, Henry Gessau > wrote: > Kevin Benton > wrote: > > So obviously the stuff in the client can be

Re: [openstack-dev] [Neutron] Rename tenant to project: discussion

On 4 December 2015 at 10:02, Kevin Benton wrote: > So obviously the stuff in the client can be updated since most of that is > user-facing. However, on the server side maybe we can start out by keeping > all of the internal code and DB tables the same. Then all we need to

Re: [openstack-dev] [Neutron] Rename tenant to project: discussion

silly as you claim if you knew the whole story, that's all! > > Neil > > -- > *From:* Armando M. <arma...@gmail.com> > *Sent:* 04 December 2015 21:01 > *To:* OpenStack Development Mailing List (not for usage questions) > *Subject:* Re: [o

Re: [openstack-dev] [Neutron] Rename tenant to project: discussion

On 12/04/2015 04:26 PM, Armando M. wrote: On 4 December 2015 at 10:02, Kevin Benton > wrote: So obviously the stuff in the client can be updated since most of that is user-facing. However, on the server side maybe we can start out by

Re: [openstack-dev] [Neutron] Rename tenant to project: discussion

>The whole world says 'tenant' for the 'tenant' concept, particularly in the context of networking. Changing to a different term is just silly. Except for the rest of OpenStack. Consistency is the one argument we can't use as a reason not to switch to project. Please read the blueprint and the

Re: [openstack-dev] [Neutron] Rename tenant to project: discussion

On 04/12/15 18:03, Kevin Benton wrote: > >The whole world says 'tenant' for the 'tenant' concept, particularly > in the context of networking. Changing to a different term is just > silly. > > Except for the rest of OpenStack. Do you mean OpenStack developers, OpenStack customers, or OpenStack

Re: [openstack-dev] [Neutron] Rename tenant to project: discussion

So obviously the stuff in the client can be updated since most of that is user-facing. However, on the server side maybe we can start out by keeping all of the internal code and DB tables the same. Then all we need to worry about is the API translation code to start. Once our public-facing stuff

Re: [openstack-dev] [Neutron] Rename tenant to project: discussion

>Do you mean OpenStack developers, OpenStack customers, or OpenStack code? All of them. Lots of us still say 'tenant' because that's what it was for quite a while. However, with keystone and the other projects referring to 'projects' which have 'project_ids', it creates inconsistency when Neutron

Re: [openstack-dev] [Neutron] Rename tenant to project: discussion

nt Mailing List (not for usage questions) Subject: Re: [openstack-dev] [Neutron] Rename tenant to project: discussion >Do you mean OpenStack developers, OpenStack customers, or OpenStack code? All of them. Lots of us still say 'tenant' because that's what it was for quite a while. However, wit

Re: [openstack-dev] [Neutron] Rename tenant to project: discussion

Kevin Benton wrote: > So obviously the stuff in the client can be updated since most of that is > user-facing. However, on the server side maybe we can start out by keeping all > of the internal code and DB tables the same. Then all we need to worry about > is the API