On 21/10/16 04:30, Adam Young wrote:
>
> No. keep them short. We are working toward a scheme where you can
> nest the names like this"
>
>
> parent/child1/child2
>
>
> But if you make them too long, that becomes a disaster. There is a
> strict option in the config file that prevents you from ma
On 09/28/2016 11:06 PM, Adrian Turjak wrote:
Hello Keystone Devs,
Just curious as to the choice to have the project name be only 64
characters:
https://github.com/openstack/keystone/blob/master/keystone/resource/backends/sql.py#L241
Seems short, and an odd choice when the user.name field is 255
On Thu, Oct 6, 2016 at 7:06 AM, gordon chung wrote:
>
>
> On 05/10/16 07:55 AM, Sean Dague wrote:
> > Except... the 64 char field in keystone isn't required to be a uuid4.
> > Which we ran into when attempting to remove it from the URLs in Nova.
> > There is no validation anywhere that requires t
On 05/10/16 07:55 AM, Sean Dague wrote:
> Except... the 64 char field in keystone isn't required to be a uuid4.
> Which we ran into when attempting to remove it from the URLs in Nova.
> There is no validation anywhere that requires that of keystone values.
>
> For instance, Rackspace uses ints.
On 10/03/2016 10:52 AM, gordon chung wrote:
>
>
> On 28/09/2016 11:52 PM, Adrian Turjak wrote:
>>
>> Plus although there is no true official standard, most projects in
>> OpenStack seem to use 255 as the default for a lot of string fields.
>> Weirdly enough, a lot of projects seem to use 255 even
On Mon, Oct 3, 2016 at 10:52 AM, gordon chung wrote:
>
>
> the original thread died pretty quickly; it didn't seem like an issue to
> anyone or needed fixing... if only there was a global council that
> worked on such technical things :P
>
>
ah great idea, perhaps we should call it a committee :)
On 28/09/2016 11:52 PM, Adrian Turjak wrote:
>
> Plus although there is no true official standard, most projects in
> OpenStack seem to use 255 as the default for a lot of string fields.
> Weirdly enough, a lot of projects seem to use 255 even for project.id,
> which seeing as it's 64 in keystone
On Wed, Sep 28, 2016 at 10:55 PM Adrian Turjak
wrote:
> I think with PKI tokens we had worse to worry about!
>
> At any rate, would be great to know, and if there isn't a strong reason
> against it we can make project name 255 for some more flexibility.
>
It's nice for UI's like horizon and open
Hi,
At any rate, would be great to know, and if there isn't a strong reason
against it we can make project name 255 for some more flexibility.
Plus although there is no true official standard, most projects in
OpenStack seem to use 255 as the default for a lot of string fields.
Weirdly enough,
I think with PKI tokens we had worse to worry about!
At any rate, would be great to know, and if there isn't a strong reason
against it we can make project name 255 for some more flexibility.
Plus although there is no true official standard, most projects in
OpenStack seem to use 255 as the defau
We may have to ask Adam or Dolph, or pull out the history textbook for this
one. I imagine that trying to not bloat the token was definitely a concern.
IIRC User name was 64 also, but we had to increase to 255 because we're not
in control of name that comes from external sources (like LDAP).
On We
Hello Keystone Devs,
Just curious as to the choice to have the project name be only 64
characters:
https://github.com/openstack/keystone/blob/master/keystone/resource/backends/sql.py#L241
Seems short, and an odd choice when the user.name field is 255 characters:
https://github.com/openstack/keyst
12 matches
Mail list logo