<html>
  <head>
    <meta content="text/html; charset=UTF-8" http-equiv="Content-Type">
  </head>
  <body text="#000000" bgcolor="#FFFFFF">
    <div class="moz-cite-prefix">On 03/11/2014 01:14 PM, Nick Maslov
      wrote:<br>
    </div>
    <blockquote cite="mid:etPan.531f365d.74b0dc51.a7a5@mbp" type="cite">
      <style>body{font-family:Helvetica,Arial;font-size:13px}</style>
      <div id="bloop_customfont"
        style="font-family:Helvetica,Arial;font-size:13px; color:
        rgba(0,0,0,1.0); margin: 0px; line-height: auto;">Hi,</div>
      <div id="bloop_customfont"
        style="font-family:Helvetica,Arial;font-size:13px; color:
        rgba(0,0,0,1.0); margin: 0px; line-height: auto;"><br>
      </div>
      <div id="bloop_customfont"
        style="font-family:Helvetica,Arial;font-size:13px; color:
        rgba(0,0,0,1.0); margin: 0px; line-height: auto;">We are on
        postgres boat as well - and yes, UTF-8 is our default setting
        for all OpenStack databases.</div>
    </blockquote>
    going off topic here, were you able to run more than one api_worker
    in neutron?<br>
    <br>
    <a class="moz-txt-link-freetext" href="https://bugs.launchpad.net/neutron/+bug/1268423">https://bugs.launchpad.net/neutron/+bug/1268423</a><br>
    <br>
    <blockquote cite="mid:etPan.531f365d.74b0dc51.a7a5@mbp" type="cite">
      <div id="bloop_customfont"
        style="font-family:Helvetica,Arial;font-size:13px; color:
        rgba(0,0,0,1.0); margin: 0px; line-height: auto;"><br>
      </div>
      <div id="bloop_customfont"
        style="font-family:Helvetica,Arial;font-size:13px; color:
        rgba(0,0,0,1.0); margin: 0px; line-height: auto;">Cheers,</div>
      <div id="bloop_customfont"
        style="font-family:Helvetica,Arial;font-size:13px; color:
        rgba(0,0,0,1.0); margin: 0px; line-height: auto;">NM </div>
      <div id="bloop_customfont"
        style="font-family:Helvetica,Arial;font-size:13px; color:
        rgba(0,0,0,1.0); margin: 0px; line-height: auto;"><br>
      </div>
      <div id="bloop_sign_1394554424258871040" class="bloop_sign"><span
          style="font-family:helvetica,arial;font-size:13px"></span>-- <br>
        Nick Maslov<br>
        <span>Sent with Airmail</span></div>
      <br>
      <p style="color:#000;">On March 10, 2014 at 11:25:39 PM, gustavo
        panizzo <gfa> (<a moz-do-not-send="true"
            href="mailto:gfa@zumbi.com.ar">gfa@zumbi.com.ar</a>) wrote:</gfa></p>
      <blockquote type="cite" class="clean_bq"><span>
          <div>
            <div>adding -operators, removing -dev
              <br>
              <br>
              On 03/10/2014 02:24 PM, Chris Friesen wrote:
              <br>
              >
              <br>
              > Hi,
              <br>
              >
              <br>
              > I'm using havana and recent we ran into an issue with
              heat related to
              <br>
              > character sets.
              <br>
              >
              <br>
              > In heat/db/sqlalchemy/api.py in user_creds_get() we
              call
              <br>
              > _decrypt() on an encrypted password stored in the
              database and then
              <br>
              > try to convert the result to unicode. Today we hit a
              case where this
              <br>
              > errored out with the following message:
              <br>
              >
              <br>
              > UnicodeDecodeError: 'utf8' codec can't decode byte
              0xf2 in position 0:
              <br>
              > invalid continuation byte
              <br>
              >
              <br>
              > We're using postgres and currently all the databases
              are using
              <br>
              > SQL_ASCII as the charset.
              <br>
              >
              <br>
              > I see that in icehouse heat will complain if you're
              using mysql and
              <br>
              > not using UTF-8. There doesn't seem to be any checks
              for other
              <br>
              > databases though.
              <br>
              >
              <br>
              > It looks like devstack creates most databases as
              UTF-8 but uses latin1
              <br>
              > for nova/nova_bm/nova_cell. I assume this is because
              nova expects to
              <br>
              > migrate the db to UTF-8 later. Given that those
              migrations specify a
              <br>
              > character set only for mysql, when using postgres
              should we explicitly
              <br>
              > default to UTF-8 for everything?
              <br>
              after running openstack with postgres for a year i can
              tell you. use
              <br>
              UTF-8 on your db.
              <br>
              our db were encoded SQL_ASCII on install time and sooner
              or later we had
              <br>
              issues, recreating db on UTF-8 fixed them
              <br>
              <br>
              <br>
              -- <br>
              1AE0 322E B8F7 4717 BDEA BF1D 44BB 1BA7 9F6C 6333
              <br>
              <br>
              <br>
              _______________________________________________
              <br>
              OpenStack-operators mailing list
              <br>
              <a class="moz-txt-link-abbreviated" href="mailto:OpenStack-operators@lists.openstack.org">OpenStack-operators@lists.openstack.org</a>
              <br>
<a class="moz-txt-link-freetext" href="http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-operators">http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-operators</a>
              <br>
            </div>
          </div>
        </span></blockquote>
    </blockquote>
    <br>
    <br>
    <pre class="moz-signature" cols="72">-- 
1AE0 322E B8F7 4717 BDEA BF1D 44BB 1BA7 9F6C 6333</pre>
  </body>
</html>