Re: [openstack-dev] [tripleo] [barbican] [tc] key store in base services (was: Encrypted swift volumes by default in the undercloud)

2018-05-16 Thread Jeremy Stanley
On 2018-05-16 17:42:09 + (+), Jeremy Stanley wrote: [...] > Unfortunately, I'm unable to find any follow-up summary on the > mailing list from the aforementioned session, but recollection from > those who were present (I had a schedule conflict at that time) was > that a

Re: [openstack-dev] [tripleo] [barbican] [tc] key store in base services (was: Encrypted swift volumes by default in the undercloud)

2018-05-16 Thread Doug Hellmann
Excerpts from Jeremy Stanley's message of 2018-05-16 17:42:09 +: > On 2018-05-16 13:16:09 +0200 (+0200), Dmitry Tantsur wrote: > > On 05/15/2018 09:19 PM, Juan Antonio Osorio wrote: > > > As part of the work from the Security Squad, we added the > > > ability for the containerized undercloud

[openstack-dev] [tripleo] [barbican] [tc] key store in base services (was: Encrypted swift volumes by default in the undercloud)

2018-05-16 Thread Jeremy Stanley
On 2018-05-16 13:16:09 +0200 (+0200), Dmitry Tantsur wrote: > On 05/15/2018 09:19 PM, Juan Antonio Osorio wrote: > > As part of the work from the Security Squad, we added the > > ability for the containerized undercloud to encrypt the > > overcloud plans. This is done by enabling Swift's encrypted