Oops, sorry about the blank email. Answers/Questions in-line.
On 26/08/15 07:46, Paul Michali wrote:
> Previous post only went to dev list. Ensuring both and adding a bit more...
>
>
>
> On Tue, Aug 25, 2015 at 8:37 AM Paul Michali wrote:
>
>> Xav,
>>
>> The discussion is very important, and
On 26/08/15 07:46, Paul Michali wrote:
> Previous post only went to dev list. Ensuring both and adding a bit more...
>
>
>
> On Tue, Aug 25, 2015 at 8:37 AM Paul Michali wrote:
>
>> Xav,
>>
>> The discussion is very important, and hence why both Kyle and I have been
>> posting these questions
Previous post only went to dev list. Ensuring both and adding a bit more...
On Tue, Aug 25, 2015 at 8:37 AM Paul Michali wrote:
> Xav,
>
> The discussion is very important, and hence why both Kyle and I have been
> posting these questions on the operator (and dev) lists. Unfortunately, I
> was
Xav,
The discussion is very important, and hence why both Kyle and I have been
posting these questions on the operator (and dev) lists. Unfortunately, I
wasn't subscribed to the operator's list and missed some responses to
Kyle's message, which were posted only to that list.
As a result, I had an
I'm sure I'm not the only one that finds the vast amount of traffic in the
dev list to be completely unmanageable to catch the important messages -
the ops list is much lower traffic, and as an operator I pay a bunch more
attention to it. The discussion of deprecating an API is something that
HAS
Also:
http://lists.openstack.org/pipermail/openstack-operators/2015-August/007928.html
http://lists.openstack.org/pipermail/openstack-operators/2015-August/007891.html
On 25 August 2015 at 09:09, Kevin Benton wrote:
> It sounds like you might have missed a couple responses:
>
>
> http://lists.
Thanks Kevin, I think I was only seeing messages that had also replied all
to openstack-dev mailing list (I wasn't on openstack-operators, until
today).
Regards,
Paul Michali (pc_m)
On Mon, Aug 24, 2015 at 5:11 PM Kevin Benton wrote:
> It sounds like you might have missed a couple responses:
It sounds like you might have missed a couple responses:
http://lists.openstack.org/pipermail/openstack-operators/2015-August/007903.html
http://lists.openstack.org/pipermail/openstack-operators/2015-August/007910.html
On Mon, Aug 24, 2015 at 1:53 PM, Paul Michali wrote:
> Xav,
>
> In the emai
Xav,
In the email, there were no responses of anyone using VPNaaS *in a
production environment*. Summary from responders:
Erik M - Tried in Juno with no success. Will retry.
Edgar M - said no reports from operators about VPNaaS code
Sam S - Using VPN in VMs and not VPNaaS
Kevin B - Not used. Use
On 25/08/15 06:32, Paul Michali wrote:
> As part of the effort to provide support for multiple local subnets
> for VPNaaS IPSec connections, there are three API changes planned [1].
>
> One is to add a new "endpoint groups" API that will describe what is
> being connected. This is the place were lo
As part of the effort to provide support for multiple local subnets for
VPNaaS IPSec connections, there are three API changes planned [1].
One is to add a new "endpoint groups" API that will describe what is being
connected. This is the place were local and peer subnets will be specified.
It will
11 matches
Mail list logo
