Open Stack

On Tue, Nov 26, 2013 at 5:25 AM, Adam Young <ayoung at redhat.com> wrote:

> Back in the Day, Barbican was just one Service of Cloud Keep.  While I
> would say that KDS belongs in the Cloud Keep, it is not the same as, and
> should not be deployed with Barbican.  Is it possible to keep them as
> separate services?  I think that is the right way to go.  Barbican is for
> the  end users of Cloud, but KDS is not.  Does this make sense?
>

I think that make sense to say that Barbican is for public and KDS for
internal services and should be kept as different WSGI daemons. If we were
having it in two different projects when assuming barbican graduate it may
end-up more confusing for the end user.

Chmouel.
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.openstack.org/pipermail/openstack-dev/attachments/20131126/c5bd12aa/attachment.html>