On Sat, 28 Jul 2018 04:21:53 +0900 Matt Riedemann
wrote
> On 7/27/2018 2:14 PM, Matt Riedemann wrote:
> >> From checking the history and review discussion on [3], it seems that
> >> it was like that from staring. key_pair quota is being counted when
> >> actually creating
Oh, right, sorry, I'm keeping to think about its about the user in specific
tenant usage just like other resources. You are right, Keypair has nothing
about the tenant, only about the user. Thanks.
2018-07-26 23:22 GMT+08:00 Chris Friesen :
> On 07/25/2018 06:22 PM, Alex Xu wrote:
>
>>
>>
>>
On 2018-07-27 14:20:01 -0500 (-0500), Matt Riedemann wrote:
[...]
> Note the entries in there about how several deployments don't rely
> on nova's keypair interface because of its clunky nature, and
> other ideas about getting nova out of the keypair business
> altogether and instead let barbican
On 07/27/2018 03:21 PM, Matt Riedemann wrote:
On 7/27/2018 2:14 PM, Matt Riedemann wrote:
From checking the history and review discussion on [3], it seems
that it was like that from staring. key_pair quota is being counted
when actually creating the keypair but it is not shown in API
On 7/27/2018 2:14 PM, Matt Riedemann wrote:
From checking the history and review discussion on [3], it seems that
it was like that from staring. key_pair quota is being counted when
actually creating the keypair but it is not shown in API 'in_use' field.
Just so I'm clear which API we're
On 7/25/2018 12:43 PM, Chris Friesen wrote:
Keypairs are weird in that they're owned by users, not projects. This
is arguably wrong, since it can cause problems if a user boots an
instance with their keypair and then gets removed from a project.
Nova microversion 2.54 added support for
On 7/25/2018 4:44 AM, Ghanshyam Mann wrote:
From checking the history and review discussion on [3], it seems that it was
like that from staring. key_pair quota is being counted when actually creating
the keypair but it is not shown in API 'in_use' field.
Just so I'm clear which API we're
On Thu, 26 Jul 2018 09:19:38 -0600, Chris Friesen wrote:
On 07/25/2018 06:21 PM, Alex Xu wrote:
2018-07-26 0:29 GMT+08:00 William M Edmonds mailto:edmon...@us.ibm.com>>:
Ghanshyam Mann mailto:gm...@ghanshyammann.com>>
wrote on 07/25/2018 05:44:46 AM:
... snip ...
> 1. is
On 07/25/2018 06:22 PM, Alex Xu wrote:
2018-07-26 1:43 GMT+08:00 Chris Friesen mailto:chris.frie...@windriver.com>>:
Keypairs are weird in that they're owned by users, not projects. This is
arguably wrong, since it can cause problems if a user boots an instance with
their
On 07/25/2018 06:21 PM, Alex Xu wrote:
2018-07-26 0:29 GMT+08:00 William M Edmonds mailto:edmon...@us.ibm.com>>:
Ghanshyam Mann mailto:gm...@ghanshyammann.com>>
wrote on 07/25/2018 05:44:46 AM:
... snip ...
> 1. is it ok to show the keypair used info via API ? any original
2018-07-26 1:43 GMT+08:00 Chris Friesen :
> On 07/25/2018 10:29 AM, William M Edmonds wrote:
>
>>
>> Ghanshyam Mann wrote on 07/25/2018 05:44:46 AM:
>> ... snip ...
>> > 1. is it ok to show the keypair used info via API ? any original
>> > rational not to do so or it was just like that from
2018-07-26 0:29 GMT+08:00 William M Edmonds :
>
> Ghanshyam Mann wrote on 07/25/2018 05:44:46 AM:
> ... snip ...
> > 1. is it ok to show the keypair used info via API ? any original
> > rational not to do so or it was just like that from starting.
>
> keypairs aren't tied to a tenant/project, so
2018-07-25 17:44 GMT+08:00 Ghanshyam Mann :
> Hi All,
>
> During today API office hour, we were discussing about keypair quota usage
> bug (newton) [1]. key_pair 'in_use' quota is always 0 even when request per
> user which is because it is being set as 0 always [2].
>
> From checking the history
On 07/25/2018 10:29 AM, William M Edmonds wrote:
Ghanshyam Mann wrote on 07/25/2018 05:44:46 AM:
... snip ...
> 1. is it ok to show the keypair used info via API ? any original
> rational not to do so or it was just like that from starting.
keypairs aren't tied to a tenant/project, so how
Ghanshyam Mann wrote on 07/25/2018 05:44:46 AM:
... snip ...
> 1. is it ok to show the keypair used info via API ? any original
> rational not to do so or it was just like that from starting.
keypairs aren't tied to a tenant/project, so how could nova track/report a
quota for them on a given
Hi All,
During today API office hour, we were discussing about keypair quota usage bug
(newton) [1]. key_pair 'in_use' quota is always 0 even when request per user
which is because it is being set as 0 always [2].
From checking the history and review discussion on [3], it seems that it was
16 matches
Mail list logo
