<html xmlns:v="urn:schemas-microsoft-com:vml" xmlns:o="urn:schemas-microsoft-com:office:office" xmlns:w="urn:schemas-microsoft-com:office:word" xmlns:m="http://schemas.microsoft.com/office/2004/12/omml" xmlns="http://www.w3.org/TR/REC-html40"><head><meta http-equiv=Content-Type content="text/html; charset=us-ascii"><meta name=Generator content="Microsoft Word 15 (filtered medium)"><base href="x-msg://121/"><!--[if !mso]><style>v\:* {behavior:url(#default#VML);}
o\:* {behavior:url(#default#VML);}
w\:* {behavior:url(#default#VML);}
.shape {behavior:url(#default#VML);}
</style><![endif]--><style><!--
/* Font Definitions */
@font-face
{font-family:Helvetica;
panose-1:2 11 6 4 2 2 2 2 2 4;}
@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:Tahoma;
panose-1:2 11 6 4 3 5 4 4 2 4;}
/* Style Definitions */
p.MsoNormal, li.MsoNormal, div.MsoNormal
{margin:0cm;
margin-bottom:.0001pt;
font-size:12.0pt;
font-family:"Times New Roman","serif";}
h3
{mso-style-priority:9;
mso-style-link:"Heading 3 Char";
margin-top:2.0pt;
margin-right:0cm;
margin-bottom:0cm;
margin-left:0cm;
margin-bottom:.0001pt;
page-break-after:avoid;
font-size:12.0pt;
font-family:"Calibri Light","sans-serif";
color:#1F4D78;
font-weight:normal;}
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.apple-converted-space
{mso-style-name:apple-converted-space;}
span.EmailStyle18
{mso-style-type:personal-reply;
font-family:"Calibri","sans-serif";
color:#1F497D;}
span.Heading3Char
{mso-style-name:"Heading 3 Char";
mso-style-priority:9;
mso-style-link:"Heading 3";
font-family:"Calibri Light","sans-serif";
color:#1F4D78;}
.MsoChpDefault
{mso-style-type:export-only;
font-size:10.0pt;}
@page WordSection1
{size:612.0pt 792.0pt;
margin:72.0pt 72.0pt 72.0pt 72.0pt;}
div.WordSection1
{page:WordSection1;}
--></style><!--[if gte mso 9]><xml>
<o:shapedefaults v:ext="edit" spidmax="1026" />
</xml><![endif]--><!--[if gte mso 9]><xml>
<o:shapelayout v:ext="edit">
<o:idmap v:ext="edit" data="1" />
</o:shapelayout></xml><![endif]--></head><body lang=EN-GB link=blue vlink=purple><div class=WordSection1><p class=MsoNormal><span style='font-size:11.0pt;font-family:"Calibri","sans-serif";color:#1F497D;mso-fareast-language:EN-US'>The certificate management that LBaaS requires might be slightly different to the normal flow of things in OpenStack services, after all you are talking about externally provided certificates and private keys.<o:p></o:p></span></p><p class=MsoNormal><span style='font-size:11.0pt;font-family:"Calibri","sans-serif";color:#1F497D;mso-fareast-language:EN-US'><o:p> </o:p></span></p><p class=MsoNormal><span style='font-size:11.0pt;font-family:"Calibri","sans-serif";color:#1F497D;mso-fareast-language:EN-US'>There’s already a standard for a nice way to bundle those two elements together, it’s described in PKCS#12 and you’ve likely come across it in the form of ‘.pfx’ files. I’d suggest that perhaps it would make sense for LBaaS to store pfx files in the LBaaS DB and store the key for the pfx files in Barbican. You could probably store them together in Barbican, using containers if you really wanted to (<a href="https://blueprints.launchpad.net/barbican/+spec/crud-endpoints-secret-container">https://blueprints.launchpad.net/barbican/+spec/crud-endpoints-secret-container</a>) <o:p></o:p></span></p><p class=MsoNormal><span style='font-size:11.0pt;font-family:"Calibri","sans-serif";color:#1F497D;mso-fareast-language:EN-US'><o:p> </o:p></span></p><p class=MsoNormal><span style='font-size:11.0pt;font-family:"Calibri","sans-serif";color:#1F497D;mso-fareast-language:EN-US'>-Rob<o:p></o:p></span></p><p class=MsoNormal><span style='font-size:11.0pt;font-family:"Calibri","sans-serif";color:#1F497D;mso-fareast-language:EN-US'><o:p> </o:p></span></p><div style='border:none;border-left:solid blue 1.5pt;padding:0cm 0cm 0cm 4.0pt'><div><div style='border:none;border-top:solid #E1E1E1 1.0pt;padding:3.0pt 0cm 0cm 0cm'><p class=MsoNormal><b><span lang=EN-US style='font-size:11.0pt;font-family:"Calibri","sans-serif"'>From:</span></b><span lang=EN-US style='font-size:11.0pt;font-family:"Calibri","sans-serif"'> Carlos Garza [mailto:carlos.garza@rackspace.com] <br><b>Sent:</b> 08 May 2014 04:30<br><b>To:</b> OpenStack Development Mailing List (not for usage questions)<br><b>Subject:</b> Re: [openstack-dev] [Neutron] [LBaaS][VPN][Barbican] SSL cert implementation for LBaaS and VPN<o:p></o:p></span></p></div></div><p class=MsoNormal><o:p> </o:p></p><p class=MsoNormal><o:p> </o:p></p><div><div><p class=MsoNormal>On May 7, 2014, at 10:53 AM, Samuel Bercovici <<a href="mailto:SamuelB@Radware.com">SamuelB@Radware.com</a>> wrote:<o:p></o:p></p></div><p class=MsoNormal><br><br><o:p></o:p></p><blockquote style='margin-top:5.0pt;margin-bottom:5.0pt'><div><div><p class=MsoNormal><span lang=EN-US style='font-size:11.0pt;font-family:"Calibri","sans-serif";color:#1F497D'>Hi John,</span><span lang=EN-US><o:p></o:p></span></p></div><div><p class=MsoNormal><span lang=EN-US style='font-size:11.0pt;font-family:"Calibri","sans-serif";color:#1F497D'> </span><span lang=EN-US><o:p></o:p></span></p></div><div><p class=MsoNormal><span lang=EN-US style='font-size:11.0pt;font-family:"Calibri","sans-serif";color:#1F497D'>If the user already has an SSL certificate that was acquired outside of the barbican Ordering system, how can he store it securely in Barbican as a SSL Certificate?</span><span lang=EN-US><o:p></o:p></span></p></div><div><p class=MsoNormal><span lang=EN-US style='font-size:11.0pt;font-family:"Calibri","sans-serif";color:#1F497D'>The Container stored this information in a very generic way, I think that there should be an API that formalizes a specific way in which SSL certificates can be stored and read back as SSL Certificates and not as loosely coupled container structure.</span><span lang=EN-US><o:p></o:p></span></p></div><div><p class=MsoNormal><span lang=EN-US style='font-size:11.0pt;font-family:"Calibri","sans-serif";color:#1F497D'>This such API should have RBAC that allows getting back only the public part of an SSL certificate vs. allowing to get back all the details of the SSL certificate.</span><span lang=EN-US><o:p></o:p></span></p></div></div></blockquote><div><p class=MsoNormal><o:p> </o:p></p></div><div><p class=MsoNormal> Why the need for that complexity? The X509s are public by nature and don't need to be stored in Barbican so there isn't really a private part of the certificate. The actual private key itself is what needs to be secured so I would advocate that the private key is what will be stored in barbican. I also think we should also declare that the private key need not be an RSA key as x509 supports other asymmetric encryption types so storing as a generic blob in barbican is probably a good idea.<o:p></o:p></p></div><div><p class=MsoNormal><o:p> </o:p></p></div><p class=MsoNormal><br><br><o:p></o:p></p><blockquote style='margin-top:5.0pt;margin-bottom:5.0pt'><div><div><p class=MsoNormal><span lang=EN-US style='font-size:11.0pt;font-family:"Calibri","sans-serif";color:#1F497D'> </span><span lang=EN-US><o:p></o:p></span></p></div><div><p class=MsoNormal><span lang=EN-US style='font-size:11.0pt;font-family:"Calibri","sans-serif";color:#1F497D'> </span><span lang=EN-US><o:p></o:p></span></p></div><div><p class=MsoNormal><span lang=EN-US style='font-size:11.0pt;font-family:"Calibri","sans-serif";color:#1F497D'> </span><span lang=EN-US><o:p></o:p></span></p></div><div><p class=MsoNormal><span lang=EN-US style='font-size:11.0pt;font-family:"Calibri","sans-serif";color:#1F497D'>-Sam.</span><span lang=EN-US><o:p></o:p></span></p></div><div><p class=MsoNormal><span lang=EN-US style='font-size:11.0pt;font-family:"Calibri","sans-serif";color:#1F497D'> </span><span lang=EN-US><o:p></o:p></span></p></div><div><p class=MsoNormal><span lang=EN-US style='font-size:11.0pt;font-family:"Calibri","sans-serif";color:#1F497D'> </span><span lang=EN-US><o:p></o:p></span></p></div><div><p class=MsoNormal><span lang=EN-US style='font-size:11.0pt;font-family:"Calibri","sans-serif";color:#1F497D'> </span><span lang=EN-US><o:p></o:p></span></p></div><div><div style='border:none;border-top:solid #B5C4DF 1.0pt;padding:3.0pt 0cm 0cm 0cm'><div><p class=MsoNormal><b><span lang=EN-US style='font-size:10.0pt;font-family:"Tahoma","sans-serif"'>From:</span></b><span class=apple-converted-space><span lang=EN-US style='font-size:10.0pt;font-family:"Tahoma","sans-serif"'> </span></span><span lang=EN-US style='font-size:10.0pt;font-family:"Tahoma","sans-serif"'>John Wood [mailto:john.wood@</span><a href="http://RACKSPACE.COM"><span lang=EN-US style='font-size:10.0pt;font-family:"Tahoma","sans-serif"'>RACKSPACE.COM</span></a><span lang=EN-US style='font-size:10.0pt;font-family:"Tahoma","sans-serif"'>]<span class=apple-converted-space> </span><br><b>Sent:</b><span class=apple-converted-space> </span>Thursday, May 01, 2014 11:28 PM<br><b>To:</b><span class=apple-converted-space> </span>OpenStack Development Mailing List (not for usage questions); </span><a href="mailto:os.vbvs@gmail.com"><span lang=EN-US style='font-size:10.0pt;font-family:"Tahoma","sans-serif"'>os.vbvs@gmail.com</span></a><span lang=EN-US style='font-size:10.0pt;font-family:"Tahoma","sans-serif"'><br><b>Subject:</b><span class=apple-converted-space> </span>Re: [openstack-dev] [Neutron] [LBaaS][VPN][Barbican] SSL cert implementation for LBaaS and VPN</span><span lang=EN-US><o:p></o:p></span></p></div></div></div><div><p class=MsoNormal><span lang=EN-US> <o:p></o:p></span></p></div><div><div><p class=MsoNormal><span lang=EN-US style='font-size:10.0pt;font-family:"Tahoma","sans-serif"'>Hello Samuel,</span><span lang=EN-US><o:p></o:p></span></p></div><div><div><p class=MsoNormal><span lang=EN-US style='font-size:10.0pt;font-family:"Tahoma","sans-serif"'> </span><span lang=EN-US><o:p></o:p></span></p></div></div><div><div><p class=MsoNormal><span lang=EN-US style='font-size:10.0pt;font-family:"Tahoma","sans-serif"'>Just noting that the link below shows current-state Barbican. We are in the process of designing SSL certificate support for Barbican via blueprints such as this one: </span><a href="https://wiki.openstack.org/wiki/Barbican/Blueprints/ssl-certificates" target="_blank"><span lang=EN-US style='font-size:10.0pt;font-family:"Tahoma","sans-serif";color:purple'>https://wiki.openstack.org/wiki/Barbican/Blueprints/ssl-certificates</span></a><span lang=EN-US><o:p></o:p></span></p></div></div><div><div><p class=MsoNormal><span lang=EN-US style='font-size:10.0pt;font-family:"Tahoma","sans-serif"'>We intend to discuss this feature in Atlanta to enable coding in earnest for Juno.</span><span lang=EN-US><o:p></o:p></span></p></div></div><div><div><p class=MsoNormal><span lang=EN-US style='font-size:10.0pt;font-family:"Tahoma","sans-serif"'> </span><span lang=EN-US><o:p></o:p></span></p></div></div><div><div><p class=MsoNormal><span lang=EN-US style='font-size:10.0pt;font-family:"Tahoma","sans-serif"'>The Container resource is intended to capture/store the final certificate details.</span><span lang=EN-US><o:p></o:p></span></p></div></div><div><div><p class=MsoNormal><span lang=EN-US style='font-size:10.0pt;font-family:"Tahoma","sans-serif"'> </span><span lang=EN-US><o:p></o:p></span></p></div></div><div><div><p class=MsoNormal><span lang=EN-US style='font-size:10.0pt;font-family:"Tahoma","sans-serif"'>Thanks,</span><span lang=EN-US><o:p></o:p></span></p></div></div><div><div><p class=MsoNormal><span lang=EN-US style='font-size:10.0pt;font-family:"Tahoma","sans-serif"'>John</span><span lang=EN-US><o:p></o:p></span></p></div></div><div><div><p class=MsoNormal><span lang=EN-US style='font-size:10.0pt;font-family:"Tahoma","sans-serif"'> </span><span lang=EN-US><o:p></o:p></span></p></div></div><div><div><p class=MsoNormal><span lang=EN-US style='font-size:10.0pt;font-family:"Tahoma","sans-serif"'> </span><span lang=EN-US><o:p></o:p></span></p></div><div><div class=MsoNormal align=center style='text-align:center'><span lang=EN-US><hr size=2 width="100%" align=center></span></div><div id=divRpF223864><p class=MsoNormal style='margin-bottom:12.0pt'><b><span lang=EN-US style='font-size:10.0pt;font-family:"Tahoma","sans-serif"'>From:</span></b><span class=apple-converted-space><span lang=EN-US style='font-size:10.0pt;font-family:"Tahoma","sans-serif"'> </span></span><span lang=EN-US style='font-size:10.0pt;font-family:"Tahoma","sans-serif"'>Samuel Bercovici [</span><a href="mailto:SamuelB@Radware.com"><span lang=EN-US style='font-size:10.0pt;font-family:"Tahoma","sans-serif"'>SamuelB@Radware.com</span></a><span lang=EN-US style='font-size:10.0pt;font-family:"Tahoma","sans-serif"'>]<br><b>Sent:</b><span class=apple-converted-space> </span>Thursday, May 01, 2014 12:50 PM<br><b>To:</b><span class=apple-converted-space> </span>OpenStack Development Mailing List (not for usage questions);<span class=apple-converted-space> </span></span><a href="mailto:os.vbvs@gmail.com"><span lang=EN-US style='font-size:10.0pt;font-family:"Tahoma","sans-serif";color:purple'>os.vbvs@gmail.com</span></a><span lang=EN-US style='font-size:10.0pt;font-family:"Tahoma","sans-serif"'><br><b>Subject:</b><span class=apple-converted-space> </span>Re: [openstack-dev] [Neutron] [LBaaS][VPN][Barbican] SSL cert implementation for LBaaS and VPN</span><span lang=EN-US><o:p></o:p></span></p></div><div><div><p class=MsoNormal><span lang=EN-US style='font-size:11.0pt;font-family:"Calibri","sans-serif";color:#1F497D'>Hi Vijay,</span><span lang=EN-US><o:p></o:p></span></p></div><div><p class=MsoNormal><span lang=EN-US style='font-size:11.0pt;font-family:"Calibri","sans-serif";color:#1F497D'> </span><span lang=EN-US><o:p></o:p></span></p></div><div><p class=MsoNormal><span lang=EN-US style='font-size:11.0pt;font-family:"Calibri","sans-serif";color:#1F497D'>I have looked at the Barbican APIs –</span><a href="https://github.com/cloudkeep/barbican/wiki/Application-Programming-Interface" target="_blank"><span lang=EN-US style='font-size:11.0pt;font-family:"Calibri","sans-serif";color:purple'>https://github.com/cloudkeep/barbican/wiki/Application-Programming-Interface</span></a><span lang=EN-US><o:p></o:p></span></p></div><div><p class=MsoNormal><span lang=EN-US style='font-size:11.0pt;font-family:"Calibri","sans-serif";color:#1F497D'>I was no able to see a “native” API that will accept an SSL certificate (private key, public key, CSR, etc.) and will store it.</span><span lang=EN-US><o:p></o:p></span></p></div><div><p class=MsoNormal><span lang=EN-US style='font-size:11.0pt;font-family:"Calibri","sans-serif";color:#1F497D'>We can either store the whole certificate as a single file as a secret or use a container and store all the certificate parts as secrets.</span><span lang=EN-US><o:p></o:p></span></p></div><div><p class=MsoNormal><span lang=EN-US style='font-size:11.0pt;font-family:"Calibri","sans-serif";color:#1F497D'> </span><span lang=EN-US><o:p></o:p></span></p></div><div><p class=MsoNormal><span lang=EN-US style='font-size:11.0pt;font-family:"Calibri","sans-serif";color:#1F497D'>I think that having LBaaS reference Certificates as IDs using some service is the right way to go so this might be achived by either:</span><span lang=EN-US><o:p></o:p></span></p></div><div style='margin-left:36.0pt'><p class=MsoNormal style='text-indent:-18.0pt'><span lang=EN-US style='font-size:11.0pt;font-family:"Calibri","sans-serif";color:#1F497D'>1.</span><span lang=EN-US style='font-size:7.0pt;color:#1F497D'> <span class=apple-converted-space> </span></span><span lang=EN-US style='font-size:11.0pt;font-family:"Calibri","sans-serif";color:#1F497D'>Adding to Barbican and API to store / generate certificates</span><span lang=EN-US><o:p></o:p></span></p></div><div style='margin-left:36.0pt'><p class=MsoNormal style='text-indent:-18.0pt'><span lang=EN-US style='font-size:11.0pt;font-family:"Calibri","sans-serif";color:#1F497D'>2.</span><span lang=EN-US style='font-size:7.0pt;color:#1F497D'> <span class=apple-converted-space> </span></span><span lang=EN-US style='font-size:11.0pt;font-family:"Calibri","sans-serif";color:#1F497D'>Create a new “module” that might start by being hosted in neutron or keystone that will allow to manage certificates and will use Barbican behind the scenes to store them.</span><span lang=EN-US><o:p></o:p></span></p></div><div style='margin-left:36.0pt'><p class=MsoNormal style='text-indent:-18.0pt'><span lang=EN-US style='font-size:11.0pt;font-family:"Calibri","sans-serif";color:#1F497D'>3.</span><span lang=EN-US style='font-size:7.0pt;color:#1F497D'> <span class=apple-converted-space> </span></span><span lang=EN-US style='font-size:11.0pt;font-family:"Calibri","sans-serif";color:#1F497D'>Decide on a container structure to use in Babican but implement the way to access and arrange it as a neutron library</span><span lang=EN-US><o:p></o:p></span></p></div><div><p class=MsoNormal><span lang=EN-US style='font-size:11.0pt;font-family:"Calibri","sans-serif";color:#1F497D'> </span><span lang=EN-US><o:p></o:p></span></p></div><div><p class=MsoNormal><span lang=EN-US style='font-size:11.0pt;font-family:"Calibri","sans-serif";color:#1F497D'>Was any decision made on how to proceed?</span><span lang=EN-US><o:p></o:p></span></p></div><div><p class=MsoNormal><span lang=EN-US style='font-size:11.0pt;font-family:"Calibri","sans-serif";color:#1F497D'> </span><span lang=EN-US><o:p></o:p></span></p></div><div><p class=MsoNormal><span lang=EN-US style='font-size:11.0pt;font-family:"Calibri","sans-serif";color:#1F497D'>Regards,</span><span lang=EN-US><o:p></o:p></span></p></div><div><p class=MsoNormal><span lang=EN-US style='font-size:11.0pt;font-family:"Calibri","sans-serif";color:#1F497D'> -Sam.</span><span lang=EN-US><o:p></o:p></span></p></div><div><p class=MsoNormal><span lang=EN-US style='font-size:11.0pt;font-family:"Calibri","sans-serif";color:#1F497D'> </span><span lang=EN-US><o:p></o:p></span></p></div><div><p class=MsoNormal><span lang=EN-US style='font-size:11.0pt;font-family:"Calibri","sans-serif";color:#1F497D'> </span><span lang=EN-US><o:p></o:p></span></p></div><div><p class=MsoNormal><span lang=EN-US style='font-size:11.0pt;font-family:"Calibri","sans-serif";color:#1F497D'> </span><span lang=EN-US><o:p></o:p></span></p></div><div><p class=MsoNormal><span lang=EN-US style='font-size:11.0pt;font-family:"Calibri","sans-serif";color:#1F497D'> </span><span lang=EN-US><o:p></o:p></span></p></div><div><p class=MsoNormal><b><span lang=EN-US style='font-size:10.0pt;font-family:"Tahoma","sans-serif"'>From:</span></b><span class=apple-converted-space><span lang=EN-US style='font-size:10.0pt;font-family:"Tahoma","sans-serif"'> </span></span><span lang=EN-US style='font-size:10.0pt;font-family:"Tahoma","sans-serif"'>Vijay B [</span><a href="mailto:os.vbvs@gmail.com"><span lang=EN-US style='font-size:10.0pt;font-family:"Tahoma","sans-serif";color:purple'>mailto:os.vbvs@gmail.com</span></a><span lang=EN-US style='font-size:10.0pt;font-family:"Tahoma","sans-serif"'>]<span class=apple-converted-space> </span><br><b>Sent:</b><span class=apple-converted-space> </span>Wednesday, April 30, 2014 3:24 AM<br><b>To:</b><span class=apple-converted-space> </span>OpenStack Development Mailing List (not for usage questions)<br><b>Subject:</b><span class=apple-converted-space> </span>[openstack-dev] [Neutron] [LBaaS][VPN] SSL cert implementation for LBaaS and VPN</span><span lang=EN-US><o:p></o:p></span></p></div><div><p class=MsoNormal><span lang=EN-US> <o:p></o:p></span></p></div><div><div><p class=MsoNormal><span lang=EN-US>Hi,<o:p></o:p></span></p></div><div><div><p class=MsoNormal><span lang=EN-US> <o:p></o:p></span></p></div></div><div><div><p class=MsoNormal><span lang=EN-US>It looks like there are areas of common effort in multiple efforts that are proceeding in parallel to implement SSL for LBaaS as well as VPN SSL in neutron.<o:p></o:p></span></p></div></div><div><div><p class=MsoNormal><span lang=EN-US> <o:p></o:p></span></p></div></div><div><div><p class=MsoNormal><span lang=EN-US>Two relevant efforts are listed below:<o:p></o:p></span></p></div></div><div><div><div><p class=MsoNormal><span lang=EN-US> <o:p></o:p></span></p></div></div><div><div><p class=MsoNormal><span lang=EN-US> <o:p></o:p></span></p></div></div><div><div><p class=MsoNormal><a href="https://review.openstack.org/#/c/74031/" target="_blank"><span lang=EN-US style='color:purple'>https://review.openstack.org/#/c/74031/</span></a><span class=apple-converted-space><span lang=EN-US> </span></span><span lang=EN-US> (</span><a href="https://wiki.openstack.org/wiki/Neutron/LBaaS/SSL" target="_blank"><span lang=EN-US style='color:purple'>https://wiki.openstack.org/wiki/Neutron/LBaaS/SSL</span></a><span lang=EN-US>)<o:p></o:p></span></p></div></div></div><div><div><p class=MsoNormal><span lang=EN-US> <o:p></o:p></span></p></div></div><div><div><p class=MsoNormal><a href="https://review.openstack.org/#/c/58897/" target="_blank"><span lang=EN-US style='color:purple'>https://review.openstack.org/#/c/58897/</span></a><span class=apple-converted-space><span lang=EN-US> </span></span><span lang=EN-US> (</span><a href="https://blueprints.launchpad.net/openstack/?searchtext=neutron-ssl-vpn" target="_blank"><span lang=EN-US style='color:purple'>https://blueprints.launchpad.net/openstack/?searchtext=neutron-ssl-vpn</span></a><span lang=EN-US>)<o:p></o:p></span></p></div></div><div><div><p class=MsoNormal><span lang=EN-US> <o:p></o:p></span></p></div></div><div><div><p class=MsoNormal><span lang=EN-US> <o:p></o:p></span></p></div></div><div><div><p class=MsoNormal><span lang=EN-US> <o:p></o:p></span></p></div></div><div><div><p class=MsoNormal><span lang=EN-US>Both VPN and LBaaS will use SSL certificates and keys, and this makes it better to implement SSL entities as first class citizens in the OS world. So, three points need to be discussed here:<o:p></o:p></span></p></div></div><div><div><p class=MsoNormal><span lang=EN-US> <o:p></o:p></span></p></div></div><div><div><p class=MsoNormal><span lang=EN-US>1. The VPN SSL implementation above is putting the SSL cert content in a mapping table, instead of maintaining certs separately and referencing them using IDs. The LBaaS implementation stores certificates in a separate table, but implements the necessary extensions and logic under LBaaS. We propose that both these implementations move away from this and refer to SSL entities using IDs, and that the SSL entities themselves are implemented as their own resources, serviced either by a core plugin or a new SSL plugin (assuming neutron; please also see point 3 below).<o:p></o:p></span></p></div></div><div><div><p class=MsoNormal><span lang=EN-US> <o:p></o:p></span></p></div></div><div><div><p class=MsoNormal><span lang=EN-US>2. The actual data store where the certs and keys are stored should be configurable at least globally, such that the SSL plugin code will singularly refer to that store alone when working with the SSL entities. The data store candidates currently are Barbican and a sql db. Each should have a separate backend driver, along with the required config values. If further evaluation of Barbican shows that it fits all SSL needs, we should make it a priority over a sqldb driver.<o:p></o:p></span></p></div></div><div><div><p class=MsoNormal><span lang=EN-US> <o:p></o:p></span></p></div></div><div><div><p class=MsoNormal><span lang=EN-US>3. Where should the primary entries for the SSL entities be stored? While the actual certs themselves will reside on Barbican or SQLdb, the entities themselves are currently being implemented in Neutron since they are being used/referenced there. However, we feel that implementing them in keystone would be most appropriate. We could also follow a federated model where a subset of keys can reside on another service such as Neutron. We are fine with starting an initial implementation in neutron, in a modular manner, and move it later to keystone.<o:p></o:p></span></p></div></div><div><div><p class=MsoNormal><span lang=EN-US> <o:p></o:p></span></p></div></div><div><div><p class=MsoNormal><span lang=EN-US> <o:p></o:p></span></p></div></div><div><div><p class=MsoNormal><span lang=EN-US>Please provide your inputs on this.<o:p></o:p></span></p></div></div><div><div><p class=MsoNormal><span lang=EN-US> <o:p></o:p></span></p></div></div><div><div><p class=MsoNormal><span lang=EN-US> <o:p></o:p></span></p></div></div><div><div><p class=MsoNormal><span lang=EN-US>Thanks,<o:p></o:p></span></p></div></div><div><div><p class=MsoNormal><span lang=EN-US>Regards,<o:p></o:p></span></p></div></div><div><div><p class=MsoNormal><span lang=EN-US>Vijay<o:p></o:p></span></p></div></div></div></div></div></div></div><p class=MsoNormal><span lang=EN-US style='font-size:13.5pt;font-family:"Helvetica","sans-serif"'>_______________________________________________<br>OpenStack-dev mailing list<br></span><a href="mailto:OpenStack-dev@lists.openstack.org"><span lang=EN-US style='font-size:13.5pt;font-family:"Helvetica","sans-serif"'>OpenStack-dev@lists.openstack.org</span></a><span lang=EN-US style='font-size:13.5pt;font-family:"Helvetica","sans-serif"'><br></span><a href="http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev"><span lang=EN-US style='font-size:13.5pt;font-family:"Helvetica","sans-serif"'>http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev</span></a><span lang=EN-US style='font-size:13.5pt;font-family:"Helvetica","sans-serif"'><o:p></o:p></span></p></div></blockquote></div><p class=MsoNormal><o:p> </o:p></p></div></div></body></html>