+1 How do we need to handle the migration reversal? https://github.com/openstack/keystone/blob/master/keystone/common/sql/migrate_repo/versions/002_token_id_hash.py -Dolph On Tue, Sep 4, 2012 at 8:55 AM, Adam Young <ayoung at redhat.com> wrote: > The PKI token change introduced an unnecessary change to the database > table for tokens. I'd like to revert it to the layout that exists in > Essex. To that end, I'd like to: > > 1. Remove the id_hash column > 2. Change the id column to sql.Column(sql.String(64), primary_key=True) > 3. Stop persisting the PKI token body in the table. > > The changes to do this are minimal. Is this an acceptable change to push > through between now and the Folsom release? Including the tokens and the > extra columns in the database long term will likely cause trouble. > > > > ______________________________**_________________ > OpenStack-dev mailing list > OpenStack-dev at lists.openstack.**org <OpenStack-dev at lists.openstack.org> > http://lists.openstack.org/**cgi-bin/mailman/listinfo/**openstack-dev<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/20120904/a3eb6408/attachment.html>