<div dir="ltr">On Tue, Sep 9, 2014 at 5:53 PM, Stanislaw Bogatkin <span dir="ltr"><<a href="mailto:sbogatkin@mirantis.com" target="_blank">sbogatkin@mirantis.com</a>></span> wrote:<br><div class="gmail_extra"><div class="gmail_quote"><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex"><div dir="ltr"><div>>So I think that we need to start on [3]. As this is required for OSt public<br>>endpoint SSL and also for Fuel SSL it can be quicker to make a first stage<br>
>where a self-signed certificate is managed from nailgun and a second stage<br>>with the docker CA...<br></div><div>So, yes, I think that it is good idea, cause it will be good base for [2] and [3]<br></div><div><div><div><br>[1] <a href="https://blueprints.launchpad.net/fuel/+spec/ca-deployment" target="_blank">https://blueprints.launchpad.net/fuel/+spec/ca-deployment</a><br>[2] <a href="https://blueprints.launchpad.net/fuel/+spec/fuel-ssl-endpoints" target="_blank">https://blueprints.launchpad.net/fuel/+spec/fuel-ssl-endpoints</a><br>[3] <a href="https://blueprints.launchpad.net/fuel/+spec/ssl-endpoints" target="_blank">https://blueprints.launchpad.net/fuel/+spec/ssl-endpoints</a><br></div></div></div></div></blockquote></div><br>+1 <br><br></div><div class="gmail_extra">I totally agree that we should start with [1] first and later focus on [2] and [3].<br><br></div><div class="gmail_extra">I'll also update [2] to adjust it to the plan you proposed.<br><br></div><div class="gmail_extra"><br></div><div class="gmail_extra">Best,<br></div><div class="gmail_extra">Sebastian<br></div></div>