Open Stack

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.

yeah, that's basically why we had to revert our attempt in Ceilometer. 
we tried to enforce uuid with some buffer and it was too difficult to 
track down every one we broke.

>
> Yes this is debt. And yes, a few things would be nicer if this was more
> constrained, but as was recently stated on twitter, we've been calling
> the 9th month the seventh month for 2000 years -
> https://twitter.com/GonzoHacker/status/781890649444519937. Some times
> the cost of fixing the thing really just isn't worth the potential
> breaks to operators that were operating within the old constraints fine.

i think this sums up my feeble attempt at initiating this as a cross 
project topic a while back. too many projects, too few participants, too 
little gain. we avoided the issue in Gnocchi and the original reason i 
brought it up became less important.

it'd be nice if we could somehow enforce new attributes/columns to 
follow uuid standards in hopes that older stuff just eventually dies 
off. that said, i'm guessing stuff like user_id and project_id columns 
are sticking around for a while...

cheers,

-- 
gord