<html><head><meta http-equiv="Content-Type" content="text/html; charset=utf-8"><meta name="Generator" content="Microsoft Word 15 (filtered medium)"><style><!--
/* Font Definitions */
@font-face
{font-family:"Cambria Math";
panose-1:2 4 5 3 5 4 6 3 2 4;}
@font-face
{font-family:Calibri;
panose-1:2 15 5 2 2 2 4 3 2 4;}
@font-face
{font-family:Cambria;
panose-1:2 4 5 3 5 4 6 3 2 4;}
/* Style Definitions */
p.MsoNormal, li.MsoNormal, div.MsoNormal
{margin:0in;
margin-bottom:.0001pt;
font-size:12.0pt;
font-family:"Times New Roman",serif;}
a:link, span.MsoHyperlink
{mso-style-priority:99;
color:blue;
text-decoration:underline;}
a:visited, span.MsoHyperlinkFollowed
{mso-style-priority:99;
color:purple;
text-decoration:underline;}
span.EmailStyle17
{mso-style-type:personal-reply;
font-family:"Cambria",serif;
color:#1F497D;}
.MsoChpDefault
{mso-style-type:export-only;
font-family:"Calibri",sans-serif;}
@page WordSection1
{size:8.5in 11.0in;
margin:1.0in 1.0in 1.0in 1.0in;}
div.WordSection1
{page:WordSection1;}
--></style></head><body lang="EN-US" link="blue" vlink="purple"><div class="WordSection1"><p class="MsoNormal"><span style="font-size:10.0pt;font-family:"Cambria",serif;color:#1f497d">I believe the last time we discussed this, the majority of people were in favor of enabling SSL by default for all public endpoints, which would be my recommendation.</span></p><p class="MsoNormal"><span style="font-size:10.0pt;font-family:"Cambria",serif;color:#1f497d"> </span></p><p class="MsoNormal"><span style="font-size:10.0pt;font-family:"Cambria",serif;color:#1f497d">As a reminder, this will mean that users will see a certificate warning the first time they access the Fuel UI. We should document this as a known user experience and provide instructions for users to swap out the self-signed certificates that are enabled by default for their own internal CA certificates/3<sup>rd</sup> party certificates.</span></p><p class="MsoNormal"><span style="font-size:10.0pt;font-family:"Cambria",serif;color:#1f497d"> </span></p><p class="MsoNormal"><b><span style="font-size:11.0pt;font-family:"Calibri",sans-serif">From:</span></b><span style="font-size:11.0pt;font-family:"Calibri",sans-serif"> Mike Scherbakov [mailto:<a href="mailto:mscherbakov@mirantis.com">mscherbakov@mirantis.com</a>] <br><b>Sent:</b> Wednesday, July 22, 2015 1:12 AM<br><b>To:</b> Stanislaw Bogatkin; Sheena Gregson<br><b>Cc:</b> OpenStack Development Mailing List (not for usage questions)<br><b>Subject:</b> Re: [Fuel] SSL feature status</span></p><p class="MsoNormal"> </p><div><p class="MsoNormal">Thanks Stas. My opinion is that it has to be enabled by default. I'd like product management to shine in here. Sheena?</p><div><p class="MsoNormal"> </p></div><div><p class="MsoNormal"> </p><div><div><p class="MsoNormal">On Tue, Jul 21, 2015 at 11:06 PM Stanislaw Bogatkin <<a href="mailto:sbogatkin@mirantis.com">sbogatkin@mirantis.com</a>> wrote:</p></div><blockquote style="border:none;border-left:solid #cccccc 1.0pt;padding:0in 0in 0in 6.0pt;margin-left:4.8pt;margin-right:0in"><div><p class="MsoNormal">Hi,</p><div><p class="MsoNormal"> </p></div><div><p class="MsoNormal">we have a spec that says we disable SSL by default and it was successfully merged with that, no one was against such decision. So, if we want to enable it by default now - we can. It should be done as a part of our usual process, I think - I'll create a bug for it and fix it.</p></div><div><p class="MsoNormal"> </p></div><div><p class="MsoNormal">Current status of feature is next:</p></div><div><p class="MsoNormal">1. All codebase for SSL is merged</p></div><div><p class="MsoNormal">2. Some tests for it writing my QA - not all of them are done yet.</p></div><div><p class="MsoNormal"> </p></div><div><p class="MsoNormal">I'll update blueprints as soon as possible. Sorry for inconvenience.</p></div></div><div><p class="MsoNormal"> </p><div><p class="MsoNormal">On Mon, Jul 20, 2015 at 8:44 PM, Mike Scherbakov <<a href="mailto:mscherbakov@mirantis.com" target="_blank">mscherbakov@mirantis.com</a>> wrote:</p><blockquote style="border:none;border-left:solid #cccccc 1.0pt;padding:0in 0in 0in 6.0pt;margin-left:4.8pt;margin-right:0in"><div><p class="MsoNormal">Hi guys,</p><div><p class="MsoNormal">did we enable SSL for Fuel Master node and OpenStack REST API endpoints by default? If not, let's enable it by default. I don't know why we should not.</p></div><div><p class="MsoNormal"> </p></div><div><p class="MsoNormal">Looks like we need to update blueprints as well [1], [2], as they don't seem to reflect current status of the feature.</p></div><div><p class="MsoNormal"> </p></div><div><p class="MsoNormal">[1] <a href="https://blueprints.launchpad.net/fuel/+spec/ssl-endpoints" target="_blank">https://blueprints.launchpad.net/fuel/+spec/ssl-endpoints</a></p></div><div><p class="MsoNormal">[2] <a href="https://blueprints.launchpad.net/fuel/+spec/fuel-ssl-endpoints" target="_blank">https://blueprints.launchpad.net/fuel/+spec/fuel-ssl-endpoints</a></p></div><div><p class="MsoNormal"> </p></div><div><p class="MsoNormal">Stas, as you've been working on it, can you please provide current status?</p></div><div><p class="MsoNormal"> </p></div><div><p class="MsoNormal">Thanks,</p></div><div><p class="MsoNormal"><span style="color:#888888"> </span></p></div></div><div><p class="MsoNormal"><span style="color:#888888">-- </span></p></div><div><p class="MsoNormal"><span style="color:#888888">Mike Scherbakov<br>#mihgen</span></p></div></blockquote></div><p class="MsoNormal"> </p></div></blockquote></div></div></div><div><p class="MsoNormal">-- </p></div><div><p class="MsoNormal">Mike Scherbakov<br>#mihgen</p></div></div></body></html>