Hi Thomas, The time reserved for the weekly IRC is 1600 UTC on Tuesdays (http://eavesdrop.openstack.org/#Neutron_VPNaaS_Meeting). The IRC channel might not be available on any other time (1500 UTC is taken by the libvirt team meeting).
Thanks, —Hanif. On 5/29/15, 12:57 PM, "Vikram Choudhary" <viks...@gmail.com> wrote: >Hi Thomos/Mathieu, > >Thanks for starting this mail thread. Let's discuss over the IRC as >suggested by Paul. > >Thanks >Vikram > >On 5/29/15, Paul Michali <p...@michali.net> wrote: >> You can use the VPNaaS IRC channel/time... we don't have much on the agenda >> right now, other than discussion VPN flavors for Liberty, in which it would >> be good to discuss BGP VPN and Edge VPN. >> >> Regards, >> >> Paul Michali (pc_m) >> >> On Fri, May 29, 2015 at 11:08 AM <thomas.mo...@orange.com> wrote: >> >>> Hi everyone, >>> >>> As a follow-up to discussions last week on a BGP VPN interconnection API >>> and the work started with the people already involved, we are going to >>> hold IRC meetings to discuss how to progress the different pieces of >>> work, in particular on the API itself [1] and its implementation+drivers >>> [2]. >>> >>> The slot we propose is ** Tuesday 15:00 UTC ** with the first meeting >>> next Tuesday (June 2nd). >>> >>> Note that, based on last week feedback, we submitted the existing >>> stackforge project for inclusion in the Neutron "big tent" earlier this >>> week [3]. >>> >>> We will do a proper meeting registration (patch to openstack-infra >>> irc-meeting) and send meeting info with wiki and meeting room before >>> next Tuesday. >>> >>> Looking forward to discussing with everyone interested! >>> >>> -Thomas & Mathieu >>> >>> [1] currently being discussed at https://review.openstack.org/#/c/177740 >>> [2] https://github.com/stackforge/networking-bgpvpn >>> [3] https://review.openstack.org/#/c/186041 >>> >>> >>> >>> >>> _________________________________________________________________________________________________________________________ >>> >>> 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. >>> >>> >>> __________________________________________________________________________ >>> OpenStack Development Mailing List (not for usage questions) >>> Unsubscribe: >>> openstack-dev-requ...@lists.openstack.org?subject:unsubscribe >>> http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev >>> >> > >__________________________________________________________________________ >OpenStack Development Mailing List (not for usage questions) >Unsubscribe: openstack-dev-requ...@lists.openstack.org?subject:unsubscribe >http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev __________________________________________________________________________ OpenStack Development Mailing List (not for usage questions) Unsubscribe: openstack-dev-requ...@lists.openstack.org?subject:unsubscribe http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev