Re: [openstack-dev] [keystone] Changing the project name uniqueness constraint

2016-06-20 Thread Henry Nash
Hi So following discussion on this, I have modified the spec to try and take account of the various concerns etc. See: https://review.openstack.org/#/c/318605/ For reference, here is an extract from this spec that summarizes the level of compatibility being proposed (A “3.6 client” refers to

Re: [openstack-dev] [keystone] Changing the project name uniqueness constraint

2016-06-14 Thread Morgan Fainberg
On Jun 14, 2016 00:46, "Henry Nash" wrote: > > On 14 Jun 2016, at 07:34, Morgan Fainberg > wrote: > > > > On Mon, Jun 13, 2016 at 3:30 PM, Henry Nash wrote: > >> So, I think it depends what level of compatibility we are aiming

Re: [openstack-dev] [keystone] Changing the project name uniqueness constraint

2016-06-14 Thread Henry Nash
> On 14 Jun 2016, at 07:34, Morgan Fainberg wrote: > > > > On Mon, Jun 13, 2016 at 3:30 PM, Henry Nash > wrote: > So, I think it depends what level of compatibility we are aiming at. Let me > articulate them, and we

Re: [openstack-dev] [keystone] Changing the project name uniqueness constraint

2016-06-14 Thread Morgan Fainberg
On Mon, Jun 13, 2016 at 3:30 PM, Henry Nash wrote: > So, I think it depends what level of compatibility we are aiming at. Let > me articulate them, and we can agree which we want: > > C1) In all version of the our APIs today (v2 and v3.0 to v3.6), you have > been able to

Re: [openstack-dev] [keystone] Changing the project name uniqueness constraint

2016-06-13 Thread Henry Nash
So, I think it depends what level of compatibility we are aiming at. Let me articulate them, and we can agree which we want: C1) In all version of the our APIs today (v2 and v3.0 to v3.6), you have been able to issue an auth request which used project/tenant name as the scoping directive (with

Re: [openstack-dev] [keystone] Changing the project name uniqueness constraint

2016-06-13 Thread Clint Byrum
Excerpts from Dolph Mathews's message of 2016-06-13 20:11:57 +: > On Fri, Jun 10, 2016 at 12:20 PM Clint Byrum wrote: > > > Excerpts from Henry Nash's message of 2016-06-10 14:37:37 +0100: > > > On further reflection, it seems to me that we can never simply enable > >

Re: [openstack-dev] [keystone] Changing the project name uniqueness constraint

2016-06-13 Thread Dolph Mathews
On Fri, Jun 10, 2016 at 12:20 PM Clint Byrum wrote: > Excerpts from Henry Nash's message of 2016-06-10 14:37:37 +0100: > > On further reflection, it seems to me that we can never simply enable > either of these approaches in a single release. Even a v4.0 version of the > API

Re: [openstack-dev] [keystone] Changing the project name uniqueness constraint

2016-06-10 Thread Morgan Fainberg
On Fri, Jun 10, 2016 at 6:37 AM, Henry Nash wrote: > On further reflection, it seems to me that we can never simply enable > either of these approaches in a single release. Even a v4.0 version of the > API doesn’t help - since presumably a sever supporting v4 would want to be

Re: [openstack-dev] [keystone] Changing the project name uniqueness constraint

2016-06-10 Thread Clint Byrum
Excerpts from Henry Nash's message of 2016-06-10 14:37:37 +0100: > On further reflection, it seems to me that we can never simply enable either > of these approaches in a single release. Even a v4.0 version of the API > doesn’t help - since presumably a sever supporting v4 would want to be able

Re: [openstack-dev] [keystone] Changing the project name uniqueness constraint

2016-06-10 Thread Henry Nash
On further reflection, it seems to me that we can never simply enable either of these approaches in a single release. Even a v4.0 version of the API doesn’t help - since presumably a sever supporting v4 would want to be able to support v3.x for a signification time; and, already discussed, as

Re: [openstack-dev] [keystone] Changing the project name uniqueness constraint

2016-06-07 Thread Henry Nash
OK, so thanks for the feedback - understand the message. However, in terms of compatibility, the one thing that concerns me about the hierarchical naming approach is that even with microversioing, we might still surprise a client. An unmodified client (i.e. doesn’t understand 3.7) would still

Re: [openstack-dev] [keystone] Changing the project name uniqueness constraint

2016-06-04 Thread Monty Taylor
On 06/04/2016 01:53 AM, Morgan Fainberg wrote: > > On Jun 3, 2016 12:42, "Lance Bragstad" > wrote: >> >> >> >> On Fri, Jun 3, 2016 at 11:20 AM, Henry Nash > wrote: >>> >>> On 3 Jun 2016, at

Re: [openstack-dev] [keystone] Changing the project name uniqueness constraint

2016-06-03 Thread Henry Nash
Both proposals allow you to provide a path as the project name in auth (so you can still use domain name + project path name). The difference between the two is whether you formally represent the path in the name attribute of a project, i.e. when it is returned by GET /project. The relax name

Re: [openstack-dev] [keystone] Changing the project name uniqueness constraint

2016-06-03 Thread Morgan Fainberg
On Jun 3, 2016 12:42, "Lance Bragstad" wrote: > > > > On Fri, Jun 3, 2016 at 11:20 AM, Henry Nash wrote: >> >> >>> On 3 Jun 2016, at 16:38, Lance Bragstad wrote: >>> >>> >>> >>> On Fri, Jun 3, 2016 at 3:20 AM, Henry Nash

Re: [openstack-dev] [keystone] Changing the project name uniqueness constraint

2016-06-03 Thread Lance Bragstad
On Fri, Jun 3, 2016 at 11:20 AM, Henry Nash wrote: > > On 3 Jun 2016, at 16:38, Lance Bragstad wrote: > > > > On Fri, Jun 3, 2016 at 3:20 AM, Henry Nash wrote: > >> >> On 3 Jun 2016, at 01:22, Adam Young wrote: >>

Re: [openstack-dev] [keystone] Changing the project name uniqueness constraint

2016-06-03 Thread Henry Nash
> On 3 Jun 2016, at 16:38, Lance Bragstad wrote: > > > > On Fri, Jun 3, 2016 at 3:20 AM, Henry Nash > wrote: > >> On 3 Jun 2016, at 01:22, Adam Young > > wrote: >> >> On

Re: [openstack-dev] [keystone] Changing the project name uniqueness constraint

2016-06-03 Thread Lance Bragstad
On Fri, Jun 3, 2016 at 3:20 AM, Henry Nash wrote: > > On 3 Jun 2016, at 01:22, Adam Young wrote: > > On 06/02/2016 07:22 PM, Henry Nash wrote: > > Hi > > As you know, I have been working on specs that change the way we handle > the uniqueness of project

Re: [openstack-dev] [keystone] Changing the project name uniqueness constraint

2016-06-03 Thread Henry Nash
> On 3 Jun 2016, at 01:22, Adam Young wrote: > > On 06/02/2016 07:22 PM, Henry Nash wrote: >> Hi >> >> As you know, I have been working on specs that change the way we handle the >> uniqueness of project names in Newton. The goal of this is to better support >> project

Re: [openstack-dev] [keystone] Changing the project name uniqueness constraint

2016-06-02 Thread Adam Young
On 06/02/2016 07:22 PM, Henry Nash wrote: Hi As you know, I have been working on specs that change the way we handle the uniqueness of project names in Newton. The goal of this is to better support project hierarchies, which as they stand today are restrictive in that all project names

[openstack-dev] [keystone] Changing the project name uniqueness constraint

2016-06-02 Thread Henry Nash
Hi As you know, I have been working on specs that change the way we handle the uniqueness of project names in Newton. The goal of this is to better support project hierarchies, which as they stand today are restrictive in that all project names within a domain must be unique, irrespective of