Open Stack

This is part of what I was referencing in regards to lightening the data
stored in the token. Ideally, we would like to see an "ID only" token that
only contains the basic information to act. Some initial tests show these
tokens should be able to clock in under 1k in size. However all the details
are not fully defined yet. Coupled with this data reduction there will be
explicit definitions of the data that is meant to go into the tokens. Some
of the data we have now is a result of convenience of accessing the data.

I hope to have this token change available during Juno development cycle.

There is a lot of work to be done to ensure this type of change goes
smoothly. But this is absolutely on the list of things we would like to
address.

Cheers,
Morgan

Sent via mobile

On Wednesday, May 21, 2014, Kurt Griffiths <kurt.griffiths at rackspace.com>
wrote:

> > adding another ~10kB to each request, just to save a once-a-day call to
> >Keystone (ie uuid tokens) seems to be a really high price to pay for not
> >much benefit.
>
> I have the same concern with respect to Marconi. I feel like KPI tokens
> are fine for control plane APIs, but don’t work so well for high-volume
> data APIs where every KB counts.
>
> Just my $0.02...
>
> --Kurt
>
> _______________________________________________
> OpenStack-dev mailing list
> OpenStack-dev at lists.openstack.org <javascript:;>
> http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.openstack.org/pipermail/openstack-dev/attachments/20140521/7d88ad45/attachment.html>