While looking into this bug:
https://bugs.launchpad.net/heat/+bug/1290274
I was trying to find out why the original developers felt that tenant_ids
should be a 'varchar(256)'. In addition to moving from a regular varchar
into a text field, varchar(256) in MySQL will become a tinytext which
For posterity, I assume this thread is related to:
http://lists.openstack.org/pipermail/openstack-dev/2014-February/028125.html
Anyway, keystone itself has issued 36-char tenant ID's in the past (diablo,
I believe, if not essex as well). Something like this:
$ python -c import uuid; s =
