Yes, that was indeed the model originally proposed (some referred to it as
“nested domains”). Back then we didn’t have project hierarchy support in
keystone (actually the two requirements emerged together and intertwined - and
for a while there was a joint spec). Today, there are some
This actually sounds a lot like a domain per reseller, with a sub-domain per reseller customer. With the reseller themselves probably also running a sub-domain or two for themselves. Mayb even running their own external federated user system for that specific reseller domain.That or something like
OK, so I worked on the original spec for this in Keystone, based around real
world requirements we (IBM) saw. For the record, here’s the particular goal we
wanted to achieve:
1) A cloud owner (i.e. the enterprise owns and maintains the core of the
cloud), wants to attract more traffic by
questions)"
<openstack-dev@lists.openstack.org>
Subject: Re: [openstack-dev] [keystone][all] Reseller - do we need it?
On Thu, Mar 16, 2017 at 5:54 PM, Fox, Kevin M
<kevin@pnnl.gov<mailto:kevin@pnnl.gov>> wrote:
At our site, we have some larger projects that would be
On Thu, Mar 16, 2017 at 4:31 PM, John Dickinson wrote:
>
>
> On 16 Mar 2017, at 14:10, Lance Bragstad wrote:
>
> Hey folks,
>
> The reseller use case [0] has been popping up frequently in various
> discussions [1], including unified limits.
>
> For those who are unfamiliar with the
Yeah, that would probably handle the use case too.
Thanks,
Kevin
From: Lance Bragstad [lbrags...@gmail.com]
Sent: Thursday, March 16, 2017 4:23 PM
To: OpenStack Development Mailing List (not for usage questions)
Subject: Re: [openstack-dev] [keystone][all
On Thu, Mar 16, 2017 at 5:54 PM, Fox, Kevin M wrote:
> At our site, we have some larger projects that would be really nice if we
> could just give a main project all the resources they need, and let them
> suballocate it as their own internal subprojects needs change. Right
At our site, we have some larger projects that would be really nice if we could
just give a main project all the resources they need, and let them suballocate
it as their own internal subprojects needs change. Right now, we have to deal
with all the subprojects directly. The reseller concept
On 16 Mar 2017, at 14:10, Lance Bragstad wrote:
> Hey folks,
>
> The reseller use case [0] has been popping up frequently in various
> discussions [1], including unified limits.
>
> For those who are unfamiliar with the reseller concept, it came out of
> early discussions regarding hierarchical