[openstack-dev] [magnum][keystone][all] Using Keystone /v3/credentials to store TLS certificates
lbragstad at gmail.com
Wed Apr 13 15:21:59 UTC 2016
I think we need to ask who we are lowering the barrier of entry for. Are we
going down this path because we want developers to have less things to do
to stand up a development environment? Or do we want to make it easy for
people to realistically test? If you're going to realistically vet magnum,
why not make that PoC as realistic as possible, as in deploying with
barbican. As an operator, I think it would be better to have an honest
assessment of the work required to deploy magnum, even if it costs a little
extra time. I'd rather hit roadblocks with the realistic approach early
than reassure my team everything will work correctly when we didn't test
what we planned to offer to our customers. In my experience, having
roadblocks pop up later after commitment has been made is expensive and
On Wed, Apr 13, 2016 at 9:37 AM, Clayton O'Neill <clayton at oneill.net> wrote:
> On Wed, Apr 13, 2016 at 10:26 AM, rezroo <openstack at roodsari.us> wrote:
> > Hi Kevin,
> > I understand that this is how it is now. My question is how bad would it
> > to wrap the Barbican client library calls in another class and claim, for
> > all practical purposes, that Magnum has no direct dependency on Barbican?
> > What is the negative of doing that?
> > Anyone who wants to use another mechanism should be able to do that with
> > simple change to the Magnum conf file. Nothing more complicated. That's
> > essence of my question.
> For us, the main reason we’d want to be able to deploy without
> Barbican is mostly to lower the initial barrier of entry. We’re not
> running anything else that would require Barbican for a multi-node
> deployment, so for us to do a realistic evaluation of Magnum, we’d
> have to get two “new to us” services up and running in a development
> environment. Since we’re not running Barbican or Magnum, that’s a big
> time commitment for something we don’t really know if we’d end up
> using. From that perspective, something that’s less secure might be
> just fine in the short term. For example, I’d be completely fine with
> storing certificates in the Magnum database as part of an evaluation,
> knowing I had to switch from that before going to production.
> OpenStack Development Mailing List (not for usage questions)
> Unsubscribe: OpenStack-dev-request at lists.openstack.org?subject:unsubscribe
-------------- next part --------------
An HTML attachment was scrubbed...
More information about the OpenStack-dev