Re: [openstack-dev] [neutron][lbaas][barbican] default certificate manager

2015-04-13 Thread Brandon Logan
, Brandon From: Ihar Hrachyshka ihrac...@redhat.com Sent: Monday, April 13, 2015 9:40 AM To: openstack-dev@lists.openstack.org Subject: Re: [openstack-dev] [neutron][lbaas][barbican] default certificate manager -BEGIN PGP SIGNED MESSAGE- Hash: SHA1

Re: [openstack-dev] [neutron][lbaas][barbican] default certificate manager

2015-04-13 Thread Doug Wiegley
To: openstack-dev@lists.openstack.org 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

Re: [openstack-dev] [neutron][lbaas][barbican] default certificate manager

2015-04-13 Thread Ihar Hrachyshka
-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

[openstack-dev] [neutron][lbaas][barbican] default certificate manager

2015-04-09 Thread Ihar Hrachyshka
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Hi lbaas folks, I've realized recently that the default certificate manager for lbaas advanced service is now barbican based. Does it mean that to make default configuration working as is, users will need to deploy barbican service? If that's really

Re: [openstack-dev] [neutron][lbaas][barbican] default certificate manager

2015-04-09 Thread Brandon Logan
incompatible. It's still a signal to users/operators that its experimental. Thanks, Brandon From: Ihar Hrachyshka ihrac...@redhat.com Sent: Thursday, April 9, 2015 10:29 AM To: openstack-dev Subject: [openstack-dev] [neutron][lbaas][barbican] default