<div dir="ltr">Steve,<div><br></div><div>This document [1] seems to indicate a preference for uwsgi over wsgi.</div><div><br></div><div>[1] <a href="https://github.com/openstack/keystone/blob/stable/mitaka/doc/source/apache-httpd.rst">https://github.com/openstack/keystone/blob/stable/mitaka/doc/source/apache-httpd.rst</a></div><div><br></div><div>Matt</div></div><div class="gmail_extra"><br><div class="gmail_quote">On Wed, Mar 23, 2016 at 2:40 PM, Steve Martinelli <span dir="ltr"><<a href="mailto:stevemar@ca.ibm.com" target="_blank">stevemar@ca.ibm.com</a>></span> wrote:<br><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex"><div><p>There are two things at play here... <br><br>1) recommended deployment: I don't recall anyone recommending uwsgi over mod_wsgi for running keystone. We've tested mod_wsgi in the gate for a while now and strongly recommend that. We only recently got uwsgi working. <br><br>2) initial setup/configuration: the new keystone-manage bootstrap command should eliminate a bunch of the previous steps that were needed. But using the ADMIN_TOKEN (the current instructions) should work, the only extra step is now we need to create a default domain too. The bootstrap option landed back in mitaka-1 and should be used in favor of the ADMIN_TOKEN option.<br><br>So, I'm fine with <a href="https://review.openstack.org/#/c/289889/" target="_blank">https://review.openstack.org/#/c/289889/</a> being abandoned and the Mitaka instructions suggesting the ADMIN_TOKEN way of configuring keystone, it should work just fine like it did for many releases.<br><br>Thanks,<br><br>Steve Martinelli<br>OpenStack Keystone Project Team Lead<br><br><img width="16" height="16" src="cid:1__=8FBBF5ECDFE292088f9e8a93df938690918c8FB@" border="0" alt="Inactive hide details for Lana Brindley ---2016/03/23 04:25:36 PM--------BEGIN PGP SIGNED MESSAGE----- Hash: SHA256"><font color="#424282">Lana Brindley ---2016/03/23 04:25:36 PM--------BEGIN PGP SIGNED MESSAGE----- Hash: SHA256</font><br><br><font size="2" color="#5F5F5F">From: </font><font size="2">Lana Brindley <<a href="mailto:openstack@lanabrindley.com" target="_blank">openstack@lanabrindley.com</a>></font><br><font size="2" color="#5F5F5F">To: </font><font size="2">Matt Kassawara <<a href="mailto:mkassawara@gmail.com" target="_blank">mkassawara@gmail.com</a>></font><br><font size="2" color="#5F5F5F">Cc: </font><font size="2">"<a href="http://enstack.org" target="_blank">enstack.org</a>" <<a href="mailto:openstack-docs@lists.openstack.org" target="_blank">openstack-docs@lists.openstack.org</a>>, Steve Martinelli/Toronto/IBM@IBMCA</font><br><font size="2" color="#5F5F5F">Date: </font><font size="2">2016/03/23 04:25 PM</font><br><font size="2" color="#5F5F5F">Subject: </font><font size="2">Re: Install Guide Testing - Update</font><br></p><hr width="100%" size="2" align="left" noshade style="color:#8091a5"><div><div class="h5"><br><br><br><tt>-----BEGIN PGP SIGNED MESSAGE-----<br>Hash: SHA256<br><br>OK, that makes sense.<br><br>Thanks,<br>L<br><br>On 24/03/16 06:24, Matt Kassawara wrote:<br>> The existing method appears to still work, so I suggest we just use it for another cycle or at least until we can get the remainder of the guide working consistently in time for release.<br>> <br>> On Wed, Mar 23, 2016 at 2:17 PM, Lana Brindley <<a href="mailto:openstack@lanabrindley.com" target="_blank">openstack@lanabrindley.com</a> <</tt><tt><a href="mailto:openstack@lanabrindley.com" target="_blank">mailto:openstack@lanabrindley.com</a></tt><tt>>> wrote:<br>> <br>> I know it's not possible to take keystone out of the book, so how do you think we should handle this?<br>> <br>> L<br>> <br>> On 24/03/16 03:58, Matt Kassawara wrote:<br>>> Keystone seems to recommend uwsgi over wsgi for Mitaka, but the deployment process is way too complex for the audience of the installation guide to adopt it. Will evaluate again for Newton.<br>> <br>>> On Mon, Mar 21, 2016 at 3:01 PM, Lana Brindley <<a href="mailto:openstack@lanabrindley.com" target="_blank">openstack@lanabrindley.com</a> <</tt><tt><a href="mailto:openstack@lanabrindley.com" target="_blank">mailto:openstack@lanabrindley.com</a></tt><tt>> <</tt><tt><a href="mailto:openstack@lanabrindley.com" target="_blank">mailto:openstack@lanabrindley.com</a></tt><tt> <</tt><tt><a href="mailto:openstack@lanabrindley.com" target="_blank">mailto:openstack@lanabrindley.com</a></tt><tt>>>> wrote:<br>> <br>>> Hi everyone,<br>> <br>>> Just wanted to update you on the progress of the Install Guide Testing.<br>> <br>>> * The good people at Suse have verified the OpenSuse version of the guide against M3<br>>> * The RDO guide is currently being tested, but isn't finished yet<br>>> * The Ubuntu guide is untested so far, as they only just released M3 packages<br>> <br>>> The main problem we're facing right now is some Keystone problems with the bootstrap mechanism, which is making the Identity chapter untestable.<br>> <br>>> Any assistance would be greatly appreciated, as we're now getting to crunch time.<br>> <br>>> Lana<br>> <br>> <br>> <br>> <br>> <br>> <br><br>- -- <br>Lana Brindley<br>Technical Writer<br>Rackspace Cloud Builders Australia<br></tt><tt><a href="http://lanabrindley.com" target="_blank">http://lanabrindley.com</a></tt><tt><br>-----BEGIN PGP SIGNATURE-----<br>Version: GnuPG v2<br>Comment: Using GnuPG with Thunderbird - </tt><tt><a href="http://www.enigmail.net/" target="_blank">http://www.enigmail.net/</a></tt><tt><br><br>iQEcBAEBCAAGBQJW8vu0AAoJELppzVb4+KUyzbIH/3eF9j1XciZwRP1gzPDq+Snb<br>8SxcL9HldL1OmjXYT+5UnKWb8ioXaDDZjvb8OGcb64wOkKQkkvgPQfuNEBf2J8ts<br>41zbgY94+FOEUT+A1RqR305GRkHuzCKVxOk3lRHTkO0gJcoE7Jz4Df9KxV6DxY1v<br>0/ysZc8ZYwrgM79pRCAv4EUmhwYRd7ZamQAdjZvumJQU1iUhHWAWG1DUUdo2/6bY<br>TpKB5K5SjR6fh5BthniVgJp5t18cDQ7MGpqcxCksWOm80/kATq1QShO50SDPyNlQ<br>D409lKLPHaT2yFPpufKBW1MFrrRXhqul+x4lzOAJrBbqo2I9QOAHvD8rkFXoqrk=<br>=Os+/<br>-----END PGP SIGNATURE-----<br><br></tt><br><br><br>
</div></div><p></p></div>
</blockquote></div><br></div>