/1
>>>
>>>
>>>
>>> -Original Message-
>>> From: Evgeny Fedoruk
>>> Sent: Wednesday, July 23, 2014 6:54 PM
>>> To: OpenStack Development Mailing List (not for usage questions)
>>> Subject: RE: [openstack-dev] [Neutron][LBaa
make sense?
>
> Thanks,
> Evg
>
> -Original Message-
> From: Carlos Garza [mailto:carlos.ga...@rackspace.com]
> Sent: Wednesday, July 23, 2014 6:15 PM
> To: OpenStack Development Mailing List (not for usage questions)
> Subject: Re: [openstack-dev] [Neutron][LBaaS] TLS c
Mailing List (not for usage questions)
Subject: Re: [openstack-dev] [Neutron][LBaaS] TLS capability - work division
Do you have any idea as to how we can split up the work?
On Jul 23, 2014, at 6:01 AM, Evgeny Fedoruk
wrote:
> Hi,
>
> I'm working on TLS integration with l
Sent: Wednesday, July 23, 2014 3:54 AM
> To: OpenStack Development Mailing List (not for usage questions)
> Subject: [openstack-dev] [Neutron][LBaaS] TLS capability - work division
>
> Since it looks like the TLS blueprint was approved I''m sure were all
> eager t
hanks,
Evg
-Original Message-
From: Carlos Garza [mailto:carlos.ga...@rackspace.com]
Sent: Wednesday, July 23, 2014 3:54 AM
To: OpenStack Development Mailing List (not for usage questions)
Subject: [openstack-dev] [Neutron][LBaaS] TLS capability - work division
Since it looks like the TLS
Since it looks like the TLS blueprint was approved I''m sure
were all eager to start coded so how should we divide up work on the
source code. I have Pull requests in pyopenssl
"https://github.com/pyca/pyopenssl/pull/143";. and a few one liners
in pica/cryptography to expose the needed low
