On Wed, Sep 10, 2014 at 2:40 PM, Tomasz Napierala <tnapier...@mirantis.com> wrote:
> > Regarding > After careful consideration, I think that for 6.0 we will only be able to > implement  with limited functionality. In terms of certificate > management, we could offer uploading customer generated cert (and maybe > provide shot doc on how to spawn CA + sign certs) > After 6.0 we can concentrate on proper implementation of CA management, > and then allow Fuel master node part to use it. > >  https://blueprints.launchpad.net/fuel/+spec/ca-deployment >  https://blueprints.launchpad.net/fuel/+spec/fuel-ssl-endpoints >  https://blueprints.launchpad.net/fuel/+spec/ssl-endpoints So if I understand correctly the idea is that we implement basic functionality for  and  especially for the management of the certificate. I guess that even if  and  are managing a self-signed certificate by their own the code that does this could be share. And then concentrate on the CA management. Thus I removed the dependency to  and I consider that in  we should implement a limited functionality as described above for .
_______________________________________________ OpenStack-dev mailing list OpenStackfirstname.lastname@example.org http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev