> On Apr 13, 2015, at 3:38 PM, Brandon Logan <[email protected]> 
> wrote:
> 
> I'm of the opinion, which may not be the popular opinion, that barbican is 
> the secret store for openstack.  It is in openstack, it is meant to be used 
> by other openstack services.  v1 lives in the same code base as v2.  Version 
> transitions such as these are going to end up having requirements only for 
> one version.  I don't think think that is a bad thing as v1 will eventually 
> be deprecated.  I am not, however, a packager so I do not know the pains you 
> have nor the perspective.  Sounds like you are okay with leaving it in, which 
> is my preference, but I can obviously be swayed.

And by "eventually", I believe Brandon meant "Liberty".

Thanks,
doug

> 
> Thanks,
> Brandon
> ________________________________________
> From: Ihar Hrachyshka <[email protected]>
> Sent: Monday, April 13, 2015 9:40 AM
> To: [email protected]
> Subject: Re: [openstack-dev] [neutron][lbaas][barbican] default certificate 
> manager
> 
> -----BEGIN PGP SIGNED MESSAGE-----
> Hash: SHA1
> 
> On 04/10/2015 09:18 PM, Brandon Logan wrote:
>> Hi Ihar, I'm not against the lazy loading solution, just wondering
>> what the real issue is here.  Is your problem with this that
>> python-barbicanclient needs to be in the requirements.txt?  Or is
>> the problem that v1 will import it even though it isn't used?
>> 
> 
> I package neutron for RDO, so I use requirements.txt as a suggestion.
> My main problem was that python-barbicanclient was not packaged for
> RDO when I started looking into the issue, but now that it's packaged
> in Fedora [1], the issue is not that significant to me. Of course it's
> a wasted dependency installed for nothing (plus its own dependencies),
> but that's not a disaster, and if upstream team thinks it's the right
> thing to do, let it be so, and I'm happy to abandon the change.
> 
> [1]: https://bugzilla.redhat.com/show_bug.cgi?id=1208454
> 
> /Ihar
> -----BEGIN PGP SIGNATURE-----
> Version: GnuPG v2
> 
> iQEcBAEBAgAGBQJVK9VFAAoJEC5aWaUY1u57dCkH/R73ECDlHVl2ocBWfTk4BEqi
> R8j/wpCCSz3x9uffWR9F8mJoqEnvekIvTtoaHaleiVfZTAhGRDRoxT7nOuMBFBDp
> ynmeJEicualeiAFX1z6//KA4L6y5hqGaV71axCRmAT/c0P5fuK08WIMBOkzQRyuo
> JmJbej5pOOlDRos0+PJd2+7qxAVU2CAuVBrJIVsJoG4zuISNDalxeOIaYKHU0+Tu
> /r7bztTrjkbcs6jiHrvv8MugsivrV1hGEBDsIVgC/Fsgy19f0X2aEjbh7G6lioab
> Vm6G+fDCFJVVQ6Xbc9qQPs1geRrocVAb7ZGeuhT/RdoMFTxBR8EJnPqWHXkYWuA=
> =O4Ll
> -----END PGP SIGNATURE-----
> 
> __________________________________________________________________________
> OpenStack Development Mailing List (not for usage questions)
> Unsubscribe: [email protected]?subject:unsubscribe
> http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev
> 
> __________________________________________________________________________
> OpenStack Development Mailing List (not for usage questions)
> Unsubscribe: [email protected]?subject:unsubscribe
> http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev


__________________________________________________________________________
OpenStack Development Mailing List (not for usage questions)
Unsubscribe: [email protected]?subject:unsubscribe
http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev

Reply via email to