Open Stack

The keystone team is also looking at ways to reduce the data contained in
the token. Coupled with the compression, this should get the tokens back
down to a reasonable size.

Cheers,
Morgan

Sent via mobile

On Wednesday, May 21, 2014, Adam Young <ayoung at redhat.com> wrote:

>  On 05/21/2014 11:09 AM, Chuck Thier wrote:
>
> There is a review for swift [1] that is requesting to set the max header
> size to 16k to be able to support v3 keystone tokens.  That might be fine
> if you measure you request rate in requests per minute, but this is
> continuing to add significant overhead to swift.  Even if you *only* have
> 10,000 requests/sec to your swift cluster, an 8k token is adding almost
> 80MB/sec of bandwidth.  This will seem to be equally bad (if not worse) for
> services like marconi.
>
>  When PKI tokens were first introduced, we raised concerns about the
> unbounded size of of the token in the header, and were told that uuid style
> tokens would still be usable, but all I heard at the summit, was to not use
> them and PKI was the future of all things.
>
>  At what point do we re-evaluate the decision to go with pki tokens, and
> that they may not be the best idea for apis like swift and marconi?
>
>
> Keystone tokens were slightly shrunk at the end of the last release cycle
> by removing unnecessary data from each endpoint entry.
>
> Compressed PKI tokens are enroute and will be much smaller.
>
>
>  Thanks,
>
>  --
> Chuck
>
>  [1] https://review.openstack.org/#/c/93356/
>
>
> _______________________________________________
> OpenStack-dev mailing listOpenStack-dev at lists.openstack.org <javascript:_e(%7B%7D,'cvml','OpenStack-dev at lists.openstack.org');>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/db926b99/attachment.html>