Mailing List (not for usage questions)
Date: Thursday, March 5, 2015 at 1:52 AM
To: OpenStack Development Mailing List (not for usage questions)
Subject: Re: [openstack-dev] [neutron][vpnaas] VPNaaS Subteam meetings
Hi,
I'm fine with C) and 1600 UTC would be more adapted for EU time Zone
, March 5, 2015 at 1:52 AM
To: OpenStack Development Mailing List (not for usage questions)
Subject: Re: [openstack-dev] [neutron][vpnaas] VPNaaS Subteam meetings
Hi,
I'm fine with C) and 1600 UTC would be more adapted for EU time Zone :)
However, I Agree that neutron-vpnaas meetings
Hi,
I'm fine with C) and 1600 UTC would be more adapted for EU time Zone :)
However, I Agree that neutron-vpnaas meetings was mainly focus on
maintaining the current IPSec implementation, by managing the slip out,
adding StrongSwan support and adding functional tests.
Maybe we will get a broader
time zone.
Thanks,
—Hanif.
From: Mathieu Rohon
Reply-To: OpenStack Development Mailing List (not for usage questions)
Date: Thursday, March 5, 2015 at 1:52 AM
To: OpenStack Development Mailing List (not for usage questions)
Subject: Re: [openstack-dev] [neutron][vpnaas] VPNaaS Subteam
To: OpenStack Development Mailing List (not for usage questions)
Subject: Re: [openstack-dev] [neutron][vpnaas] VPNaaS Subteam meetings
Hi,
I'm fine with C) and 1600 UTC would be more adapted for EU time Zone :)
However, I Agree that neutron-vpnaas meetings was mainly focus on maintaining
the current
Hi Paul.
I'd vote for (C) and a slightly later time-slot on Tuesdays - 1630 UTC (or
later).
The meetings so far was indeed quite useful. I guess the current busy Kilo
cycle is also contributing to the low turnout. As we pick up things going
forward this forum will be quite useful to discuss
