<html>
  <head>
    <meta content="text/html; charset=ISO-8859-1"
      http-equiv="Content-Type">
  </head>
  <body text="#000000" bgcolor="#FFFFFF">
    <div class="moz-cite-prefix">On 09/04/2012 12:54 PM, Dolph Mathews
      wrote:<br>
    </div>
    <blockquote
cite="mid:CAC=h7gWHdhJbSdrNk4q63f0ksgAasSSZps1qYXEhYeYh+8fCnQ@mail.gmail.com"
      type="cite">+1
      <div><br>
      </div>
      <div>How do we need to handle the migration reversal? <a
          moz-do-not-send="true"
href="https://github.com/openstack/keystone/blob/master/keystone/common/sql/migrate_repo/versions/002_token_id_hash.py">https://github.com/openstack/keystone/blob/master/keystone/common/sql/migrate_repo/versions/002_token_id_hash.py</a><br
          clear="all">
      </div>
    </blockquote>
    <br>
    Just add another one on.  I'm writing it as part of the patch.<br>
    <br>
    <blockquote
cite="mid:CAC=h7gWHdhJbSdrNk4q63f0ksgAasSSZps1qYXEhYeYh+8fCnQ@mail.gmail.com"
      type="cite">
      <div>
      </div>
      <div><br>
      </div>
      -Dolph<br>
      <br>
      <br>
      <div class="gmail_quote">On Tue, Sep 4, 2012 at 8:55 AM, Adam
        Young <span dir="ltr"><<a moz-do-not-send="true"
            href="mailto:ayoung@redhat.com" target="_blank">ayoung@redhat.com</a>></span>
        wrote:<br>
        <blockquote class="gmail_quote" style="margin:0 0 0
          .8ex;border-left:1px #ccc solid;padding-left:1ex">
          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:<br>
          <br>
          1.  Remove the id_hash column<br>
          2.  Change the id column to  sql.Column(sql.String(64),
          primary_key=True)<br>
          3.  Stop persisting the PKI token body in the table.<br>
          <br>
          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.<br>
          <br>
          <br>
          <br>
          _______________________________________________<br>
          OpenStack-dev mailing list<br>
          <a moz-do-not-send="true"
            href="mailto:OpenStack-dev@lists.openstack.org"
            target="_blank">OpenStack-dev@lists.openstack.org</a><br>
          <a moz-do-not-send="true"
            href="http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev"
            target="_blank">http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev</a><br>
        </blockquote>
      </div>
      <br>
      <br>
      <fieldset class="mimeAttachmentHeader"></fieldset>
      <br>
      <pre wrap="">_______________________________________________
OpenStack-dev mailing list
<a class="moz-txt-link-abbreviated" href="mailto:OpenStack-dev@lists.openstack.org">OpenStack-dev@lists.openstack.org</a>
<a class="moz-txt-link-freetext" href="http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev">http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev</a>
</pre>
    </blockquote>
    <br>
  </body>
</html>