<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">+1 to #2</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"> Vladimir Kuklin [mailto:<a href="mailto:vkuklin@mirantis.com">vkuklin@mirantis.com</a>] <br><b>Sent:</b> Tuesday, August 04, 2015 6:25 AM<br><b>To:</b> OpenStack Development Mailing List (not for usage questions) <<a href="mailto:openstack-dev@lists.openstack.org">openstack-dev@lists.openstack.org</a>><br><b>Subject:</b> Re: [openstack-dev] [Fuel] SSL for master node API</span></p><p class="MsoNormal"> </p><div><p class="MsoNormal">I am for 2nd option for 7.0 and for 3rd for 8.0</p><div><p class="MsoNormal"> </p></div><div><p class="MsoNormal">But I would suggest that we add an option to astute.yaml that a user can set to true to force ssl and then he will need to install updated nailgun-agent for older environments. In this case user will do this concisely, knowing about potential caveats of forcing SSL.</p></div></div><div><p class="MsoNormal"> </p><div><p class="MsoNormal">On Tue, Aug 4, 2015 at 1:45 PM, Evgeniy L <<a href="mailto:eli@mirantis.com" target="_blank">eli@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><div><p class="MsoNormal">Hi,</p></div><div><p class="MsoNormal"> </p></div><p class="MsoNormal">+1 to 2nd solution, in this case old environments will work without additional</p><div><p class="MsoNormal">actions. Agents for new environments, CLI and UI will use SSL.</p></div><div><p class="MsoNormal">But probably for UI we will have to perform redirect on JS level.</p></div><div><p class="MsoNormal"> </p></div><div><p class="MsoNormal">Thanks,</p></div></div><div><p class="MsoNormal"> </p><div><div><div><p class="MsoNormal">On Tue, Aug 4, 2015 at 1:32 PM, Stanislaw Bogatkin <<a href="mailto:sbogatkin@mirantis.com" target="_blank">sbogatkin@mirantis.com</a>> wrote:</p></div></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><div><div><p class="MsoNormal">Hi guys,</p><div><p class="MsoNormal">in overall movement of Fuel to use secure sockets we think about wrapping master node UI and API calls to SSL. But there are next caveat:</p></div><div><p class="MsoNormal"> </p></div><div><p class="MsoNormal">a) fuel-nailgun-agent cannot work via SSL now and need to be rewritten a little. But if it will be rewritten in 7.0 and HTTPS on master node will be forced by default, it will break upgrade from previous releases to 7.0 due fact that after master node upgrade from 6.1 to 7.0 we will have HTTPS by default and fuel-nailgun-agent on all environments won't upgraded, so it won't be able to connect to master node after upgrade. It breaks seamless upgrade procedure.</p></div><div><p class="MsoNormal"> </p></div><div><p class="MsoNormal">What options I see there:</p></div><div><p class="MsoNormal">1. We can forcedly enable SSL for master node and rewrite clients in 7.0 to be able to work over it. In release notes for 7.0 we will write forewarning that clients which want to upgrade master node from previous releases to 7.0 must also install new fuel-nailgun-agent to all nodes in all deployed environments.</p></div><div><p class="MsoNormal"> </p></div><div><p class="MsoNormal">2. We can have both SSL and non-SSL versions enabled by default and rewrite fuel-nailgun-client in 7.0 such way that it will check SSL availability and be able to work in plain HTTP for legacy mode. So, for all new environments SSL will be used by default and for old ones plain HTTP will continue to work too. Master node upgrade will not be broken in this case.</p></div><div><p class="MsoNormal"> </p></div><div><p class="MsoNormal">3. We can do some mixed way by gradually rewrite fuel-nailgun-client, save both HTTP and HTTPS for master node in 7.0 and drop plain HTTP in next releases. It is just postponed version of first clause, so it doesn't seems valid for me, actually.</p></div><div><p class="MsoNormal"> </p></div><div><p class="MsoNormal">I would be really glad to hear what you think about this. Thank you in advance.</p></div></div><p class="MsoNormal"> </p></div></div><p class="MsoNormal" style="margin-bottom:12.0pt">__________________________________________________________________________<br>OpenStack Development Mailing List (not for usage questions)<br>Unsubscribe: <a href="http://OpenStack-dev-request@lists.openstack.org?subject:unsubscribe" target="_blank">OpenStack-dev-request@lists.openstack.org?subject:unsubscribe</a><br><a href="http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev" target="_blank">http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev</a></p></blockquote></div><p class="MsoNormal"> </p></div><p class="MsoNormal" style="margin-bottom:12.0pt"><br>__________________________________________________________________________<br>OpenStack Development Mailing List (not for usage questions)<br>Unsubscribe: <a href="http://OpenStack-dev-request@lists.openstack.org?subject:unsubscribe" target="_blank">OpenStack-dev-request@lists.openstack.org?subject:unsubscribe</a><br><a href="http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev" target="_blank">http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev</a></p></blockquote></div><p class="MsoNormal"><br><br clear="all"></p><div><p class="MsoNormal"> </p></div><p class="MsoNormal">-- </p><div><div><div><div><p class="MsoNormal">Yours Faithfully,<br>Vladimir Kuklin,<br>Fuel Library Tech Lead,<br>Mirantis, Inc.<br>+7 (495) 640-49-04<br>+7 (926) 702-39-68<br>Skype kuklinvv<br>35bk3, Vorontsovskaya Str.<br>Moscow, Russia,<br><a href="http://www.mirantis.ru/" target="_blank">www.mirantis.com</a><br><a href="http://www.mirantis.ru/" target="_blank">www.mirantis.ru</a><br><a href="mailto:vkuklin@mirantis.com" target="_blank">vkuklin@mirantis.com</a></p></div></div></div></div></div></div></body></html>