<html>
<head>
<meta content="text/html; charset=utf-8" http-equiv="Content-Type">
</head>
<body bgcolor="#FFFFFF" text="#000000">
<div class="moz-cite-prefix">Hi Paul, all,<br>
<br>
Yes, it's good to have a discussion on BGP VPN and edge VPN
proposals during the VPNaaS meeting.<br>
At least Mathieu and I will participate to see how we can help.<br>
<br>
To avoid confusion we think it's good to keep separate the
discussion on the details of the work around the networking-bgpvpn
stackforge project, so we'll use the 15:00 UTC slot on
#openstack-alt for this purpose (free AFAICT). And, we will
encourage all participants to attend the VPNaaS meeting right
after, on #openstack-meeting-3.<br>
<br>
Thank you,<br>
<br>
-Thomas<br>
<br>
<br>
Le 01/06/2015 13:06, Paul Michali a écrit :<br>
</div>
<blockquote
cite="mid:CA+ikoRMtH+0PNRPzm-AxdBh3N6gDmtpHHf0S=nEd5T_cMYxLYA@mail.gmail.com"
type="cite">
<meta http-equiv="Content-Type" content="text/html; charset=utf-8">
<div dir="ltr">FYI, the channel is openstack-meeting-3.<br>
</div>
<br>
<div class="gmail_quote">
<div dir="ltr">On Sun, May 31, 2015 at 10:41 PM Mohammad Hanif
<<a moz-do-not-send="true" href="mailto:mhanif@brocade.com">mhanif@brocade.com</a>>
wrote:<br>
</div>
<blockquote class="gmail_quote" style="margin:0 0 0
.8ex;border-left:1px #ccc solid;padding-left:1ex">Hi Thomas,<br>
<br>
The time reserved for the weekly IRC is 1600 UTC on Tuesdays (<a
moz-do-not-send="true"
href="http://eavesdrop.openstack.org/#Neutron_VPNaaS_Meeting"
target="_blank">http://eavesdrop.openstack.org/#Neutron_VPNaaS_Meeting</a>).
The IRC channel might not be available on any other time (1500
UTC is taken by the libvirt team meeting).<br>
<br>
Thanks,<br>
—Hanif.<br>
<br>
<br>
<br>
On 5/29/15, 12:57 PM, "Vikram Choudhary" <<a
moz-do-not-send="true" href="mailto:vikschw@gmail.com"
target="_blank">vikschw@gmail.com</a>> wrote:<br>
<br>
>Hi Thomas/Mathieu,<br>
><br>
>Thanks for starting this mail thread. Let's discuss over
the IRC as<br>
>suggested by Paul.<br>
><br>
>Thanks<br>
>Vikram<br>
><br>
>On 5/29/15, Paul Michali <<a moz-do-not-send="true"
href="mailto:pc@michali.net" target="_blank">pc@michali.net</a>>
wrote:<br>
>> You can use the VPNaaS IRC channel/time... we don't
have much on the agenda<br>
>> right now, other than discussion VPN flavors for
Liberty, in which it would<br>
>> be good to discuss BGP VPN and Edge VPN.<br>
>><br>
>> Regards,<br>
>><br>
>> Paul Michali (pc_m)<br>
>><br>
>> On Fri, May 29, 2015 at 11:08 AM <<a
moz-do-not-send="true" href="mailto:thomas.morin@orange.com"
target="_blank">thomas.morin@orange.com</a>> wrote:<br>
>><br>
>>> Hi everyone,<br>
>>><br>
>>> As a follow-up to discussions last week on a BGP
VPN interconnection API<br>
>>> and the work started with the people already
involved, we are going to<br>
>>> hold IRC meetings to discuss how to progress the
different pieces of<br>
>>> work, in particular on the API itself [1] and its
implementation+drivers<br>
>>> [2].<br>
>>><br>
>>> The slot we propose is ** Tuesday 15:00 UTC **
with the first meeting<br>
>>> next Tuesday (June 2nd).<br>
>>><br>
>>> Note that, based on last week feedback, we
submitted the existing<br>
>>> stackforge project for inclusion in the Neutron
"big tent" earlier this<br>
>>> week [3].<br>
>>><br>
>>> We will do a proper meeting registration (patch
to openstack-infra<br>
>>> irc-meeting) and send meeting info with wiki and
meeting room before<br>
>>> next Tuesday.<br>
>>><br>
>>> Looking forward to discussing with everyone
interested!<br>
>>><br>
>>> -Thomas & Mathieu<br>
>>><br>
>>> [1] currently being discussed at <a
moz-do-not-send="true"
href="https://review.openstack.org/#/c/177740"
target="_blank">https://review.openstack.org/#/c/177740</a><br>
>>> [2] <a moz-do-not-send="true"
href="https://github.com/stackforge/networking-bgpvpn"
target="_blank">https://github.com/stackforge/networking-bgpvpn</a><br>
>>> [3] <a moz-do-not-send="true"
href="https://review.openstack.org/#/c/186041"
target="_blank">https://review.openstack.org/#/c/186041</a><br>
>>><br>
>>><br>
>>><br>
>>><br>
>>>
_________________________________________________________________________________________________________________________<br>
>>><br>
>>> Ce message et ses pieces jointes peuvent contenir
des informations<br>
>>> confidentielles ou privilegiees et ne doivent
donc<br>
>>> pas etre diffuses, exploites ou copies sans
autorisation. Si vous avez<br>
>>> recu ce message par erreur, veuillez le signaler<br>
>>> a l'expediteur et le detruire ainsi que les
pieces jointes. Les messages<br>
>>> electroniques etant susceptibles d'alteration,<br>
>>> Orange decline toute responsabilite si ce message
a ete altere, deforme<br>
>>> ou<br>
>>> falsifie. Merci.<br>
>>><br>
>>> This message and its attachments may contain
confidential or privileged<br>
>>> information that may be protected by law;<br>
>>> they should not be distributed, used or copied
without authorisation.<br>
>>> If you have received this email in error, please
notify the sender and<br>
>>> delete this message and its attachments.<br>
>>> As emails may be altered, Orange is not liable
for messages that have<br>
>>> been<br>
>>> modified, changed or falsified.<br>
>>> Thank you.<br>
>>><br>
>>><br>
>>>
__________________________________________________________________________<br>
>>> OpenStack Development Mailing List (not for usage
questions)<br>
>>> Unsubscribe:<br>
>>> <a moz-do-not-send="true"
href="http://OpenStack-dev-request@lists.openstack.org?subject:unsubscribe"
target="_blank">OpenStack-dev-request@lists.openstack.org?subject:unsubscribe</a><br>
>>> <a moz-do-not-send="true"
href="http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev"
target="_blank">http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev</a><br>
>>><br>
>><br>
><br>
>__________________________________________________________________________<br>
>OpenStack Development Mailing List (not for usage
questions)<br>
>Unsubscribe: <a moz-do-not-send="true"
href="http://OpenStack-dev-request@lists.openstack.org?subject:unsubscribe"
target="_blank">OpenStack-dev-request@lists.openstack.org?subject:unsubscribe</a><br>
><a moz-do-not-send="true"
href="http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev"
target="_blank">http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev</a><br>
__________________________________________________________________________<br>
OpenStack Development Mailing List (not for usage questions)<br>
Unsubscribe: <a moz-do-not-send="true"
href="http://OpenStack-dev-request@lists.openstack.org?subject:unsubscribe"
target="_blank">OpenStack-dev-request@lists.openstack.org?subject:unsubscribe</a><br>
<a moz-do-not-send="true"
href="http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev"
target="_blank">http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev</a><br>
</blockquote>
</div>
<br>
<fieldset class="mimeAttachmentHeader"></fieldset>
<br>
<pre wrap="">__________________________________________________________________________
OpenStack Development Mailing List (not for usage questions)
Unsubscribe: <a class="moz-txt-link-abbreviated" href="mailto:OpenStack-dev-request@lists.openstack.org?subject:unsubscribe">OpenStack-dev-request@lists.openstack.org?subject:unsubscribe</a>
<a class="moz-txt-link-freetext" href="http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev">http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev</a>
</pre>
</blockquote>
<br>
<PRE>_________________________________________________________________________________________________________________________
Ce message et ses pieces jointes peuvent contenir des informations confidentielles ou privilegiees et ne doivent donc
pas etre diffuses, exploites ou copies sans autorisation. Si vous avez recu ce message par erreur, veuillez le signaler
a l'expediteur et le detruire ainsi que les pieces jointes. Les messages electroniques etant susceptibles d'alteration,
Orange decline toute responsabilite si ce message a ete altere, deforme ou falsifie. Merci.
This message and its attachments may contain confidential or privileged information that may be protected by law;
they should not be distributed, used or copied without authorisation.
If you have received this email in error, please notify the sender and delete this message and its attachments.
As emails may be altered, Orange is not liable for messages that have been modified, changed or falsified.
Thank you.
</PRE></body>
</html>