Hi Folks,
As we have discussed in the last Keystone meeting, we created an etherpad
with the alternatives to solve this problem:
https://etherpad.openstack.org/p/reseller-project-token
We have also decided to take a vote to choose the best option in the next
Keystone Meeting (#openstack-meeting -
Sent via mobile
On Jun 9, 2015, at 05:44, Jamie Lennox jamielen...@redhat.com wrote:
- Original Message -
From: David Chadwick d.w.chadw...@kent.ac.uk
To: openstack-dev@lists.openstack.org
Sent: Saturday, 6 June, 2015 6:01:10 PM
Subject: Re: [openstack-dev]
On Mon, Jun 8, 2015 at 10:44 PM, Jamie Lennox jamielen...@redhat.com
wrote:
- Original Message -
From: David Chadwick d.w.chadw...@kent.ac.uk
To: openstack-dev@lists.openstack.org
Sent: Saturday, 6 June, 2015 6:01:10 PM
Subject: Re: [openstack-dev] [keystone][reseller] New way
- Original Message -
From: David Chadwick d.w.chadw...@kent.ac.uk
To: openstack-dev@lists.openstack.org
Sent: Saturday, 6 June, 2015 6:01:10 PM
Subject: Re: [openstack-dev] [keystone][reseller] New way to get a project
scoped token by name
On 06/06/2015 00:24, Adam Young
On 06/06/2015 00:24, Adam Young wrote:
On 06/05/2015 01:15 PM, Henry Nash wrote:
I am sure I have missed something along the way, but can someone
explain to me why we need this at all. Project names are unique
within a domain, with the exception of the project that is acting as
its domain
I am sure I have missed something along the way, but can someone explain to me
why we need this at all. Project names are unique within a domain, with the
exception of the project that is acting as its domain (i.e. they can only every
be two names clashing in a hierarchy at the domain level
On 06/03/2015 05:05 PM, Morgan Fainberg wrote:
Hi David,
There needs to be some form of global hierarchy delimiter - well more
to the point there should be a common one across OpenStack
installations to ensure we are providing a good and consistent (and
more to the point inter-operable)
First I have some questions: if we are going to add a delimiter, how can we
handle OpenStack API Stability guidelines [1]? If we add this delimiter in
keystone.conf (and having the default value being . or /), do we fall
into the same API stability problems?
Personally, I'm in favor of having a
On Thu, Jun 4, 2015 at 10:10 AM Rodrigo Duarte rodrigodso...@gmail.com
wrote:
Also, if we are going to use a delimiter, we need to update the way
projects names are returned in the GET v3/projects API to include the
hierarchy so the user (or client) knows how to request a token using the
I agree that it is better to choose one global delimiter (ideally this
should have been done from day one, when hierarchical naming should have
been used as the basic name form for Openstack). Whatever you choose now
will cause someone somewhere some pain, but perhaps the overall pain to
the whole
On 03/06/2015 14:54, Henrique Truta wrote:
Hi David,
You mean creating some kind of delimiter attribute in the domain
entity? That seems like a good idea, although it does not solve the
problem Morgan's mentioned that is the global hierarchy delimiter.
There would be no global hierarchy
Hi David,
There needs to be some form of global hierarchy delimiter - well more to
the point there should be a common one across OpenStack installations to
ensure we are providing a good and consistent (and more to the point
inter-operable) experience to our users. I'm worried a custom defined
On 02/06/2015 23:34, Morgan Fainberg wrote:
Hi Henrique,
I don't think we need to specifically call out that we want a domain, we
should always reference the namespace as we do today. Basically, if we
ask for a project name we need to also provide it's namespace (your
option #1). This
Hi David,
You mean creating some kind of delimiter attribute in the domain entity?
That seems like a good idea, although it does not solve the problem
Morgan's mentioned that is the global hierarchy delimiter.
Henrique
Em qua, 3 de jun de 2015 às 04:21, David Chadwick d.w.chadw...@kent.ac.uk
Hi Henrique,
I don't think we need to specifically call out that we want a domain, we
should always reference the namespace as we do today. Basically, if we ask
for a project name we need to also provide it's namespace (your option #1).
This clearly lines up with how we handle projects in domains
Hi folks,
In Reseller[1], we’ll have the domains concept merged into projects, that
means that we will have projects that will behave as domains. Therefore, it
will be possible to have two projects with the same name in a hierarchy,
one being a domain and another being a regular project. For
16 matches
Mail list logo