On 06/08/2015 02:10 PM, Steve Lewis wrote:
Monday, June 8, 2015 07:10, Adam Young wrote:
2. Delegation are long lived affairs. If anything is going to take
longer than the duration of the token, it should be in the context of a
delegation, and the user should re-authenticate to prove identity.
t;>
>>> Alternately and encapsulating token
>>>
>>>
>>> > -- keeping it simple, only two levels. This
>>> protects from on the cusp expired user-tokens.
>>>
>>> Could check user quota before attempting the storage.
>>>
>>>
Monday, June 8, 2015 07:10, Adam Young wrote:
> 2. Delegation are long lived affairs. If anything is going to take
> longer than the duration of the token, it should be in the context of a
> delegation, and the user should re-authenticate to prove identity.
Requiring re-authenticating to perform
To:* openstack-dev@lists.openstack.org
*Subject:* Re: [openstack-dev] [Glance][Keystone] Glance and trusts
On 06/05/2015 10:39 AM, Dolph Mathews wrote:
On Thu, Jun 4, 2015 at 1:54 AM, David Chadwick
mailto:d.w.chadw...@kent.ac.uk>> wrote:
I did suggest another solut
M
To: openstack-dev@lists.openstack.org
Subject: Re: [openstack-dev] [Glance][Keystone] Glance and trusts
On 06/05/2015 10:39 AM, Dolph Mathews wrote:
On Thu, Jun 4, 2015 at 1:54 AM, David Chadwick wrote:
I did suggest another solution to Adam whilst we were in Vancouver, and
this mirrors what happens in the real
:11 PM
> To: openstack-dev@lists.openstack.org
> Subject: Re: [openstack-dev] [Glance][Keystone] Glance and trusts
>
> On 06/05/2015 10:39 AM, Dolph Mathews wrote:
>
> On Thu, Jun 4, 2015 at 1:54 AM, David Chadwick
> wrote:
> I did suggest another solution to Adam whilst
ck user quota before attempting the storage.
>
>
>
> Should user not have paid dues, Glance knows which objects to garbage
> collect!
>
>
>
> Regards
>
> Malini
>
>
>
> *From:*Adam Young [mailto:ayo...@redhat.com]
> *Sent:* Friday, Jun
Regards
Malini
From: Adam Young [mailto:ayo...@redhat.com]
Sent: Friday, June 05, 2015 4:11 PM
To: openstack-dev@lists.openstack.org
Subject: Re: [openstack-dev] [Glance][Keystone] Glance and trusts
On 06/05/2015 10:39 AM, Dolph Mathews wrote:
On Thu, Jun 4, 2015 at 1:54 AM, David Chadwick
mailto:d
On 06/05/2015 10:39 AM, Dolph Mathews wrote:
On Thu, Jun 4, 2015 at 1:54 AM, David Chadwick
mailto:d.w.chadw...@kent.ac.uk>> wrote:
I did suggest another solution to Adam whilst we were in
Vancouver, and
this mirrors what happens in the real world today when I order
something
On Thu, Jun 4, 2015 at 1:54 AM, David Chadwick
wrote:
> I did suggest another solution to Adam whilst we were in Vancouver, and
> this mirrors what happens in the real world today when I order something
> from a supplier and a whole supply chain is involved in creating the end
> product that I or
I did suggest another solution to Adam whilst we were in Vancouver, and
this mirrors what happens in the real world today when I order something
from a supplier and a whole supply chain is involved in creating the end
product that I ordered. This is not too dissimilar to a user requesting
a new VM.
On 06/02/2015 12:57 PM, Mikhail Fedosin wrote:
Hello! I think it's a good time to discuss implementation of trusts in
Glance v2 and v3 api.
Currently we have two different situations during image creation where
our token may expire, which leads to unsuccessful operation.
First is connection
Hello! I think it's a good time to discuss implementation of trusts in
Glance v2 and v3 api.
Currently we have two different situations during image creation where our
token may expire, which leads to unsuccessful operation.
First is connection between glance-api and glance-registry. In this case
13 matches
Mail list logo