<html><head></head><body style="word-wrap: break-word; -webkit-nbsp-mode: space; -webkit-line-break: after-white-space; "><div>All:</div><div><br></div><div>I proposed a change in the OpenStack Install and Deploy manual <<a href="https://review.openstack.org/6085">https://review.openstack.org/6085</a>> to fix bug <a href="https://bugs.launchpad.net/openstack-manuals/+bug/968679">https://bugs.launchpad.net/openstack-manuals/+bug/968679</a>.</div><div><br></div><div>However, I'm not a keystone expert, and would appreciate it if somebody familiar with installing keystone could take a look and do a sanity check. I based my changes on <a href="http://www.hastexo.com/resources/docs/installing-openstack-essex-4-ubuntu-1204-precise-pangolin/step-3-install-and-configur">http://www.hastexo.com/resources/docs/installing-openstack-essex-4-ubuntu-1204-precise-pangolin/step-3-install-and-configur</a>.</div><div><br></div><div>Also, it's unclear to me whether the official recommended practice is to manually create the service catalog entries so they are stored in the database backend (as was originally documented and seems to be the default Ubuntu package setup) or to use the templated catalog file (as suggested by that blog entry and used by devstack).</div><br><div apple-content-edited="true">
<div style="word-wrap: break-word; -webkit-nbsp-mode: space; -webkit-line-break: after-white-space; "><div style="word-wrap: break-word; -webkit-nbsp-mode: space; -webkit-line-break: after-white-space; "><div>Take care,</div><div><br></div><div>Lorin</div><div>--</div><div>Lorin Hochstein</div><div>Lead Architect - Cloud Services</div><div>Nimbis Services, Inc.</div><div><a href="https://www.nimbisservices.com/">www.nimbisservices.com</a></div><div><br></div></div><br class="Apple-interchange-newline"></div><br class="Apple-interchange-newline"><br class="Apple-interchange-newline">
</div>
<br></body></html>