Open Stack

I agree logging IRC is much better than using etherpad chat. There is a
rather low limit of characters for each sentence.

I have added some preliminary comments on the etherpad.


On 4 April 2013 10:54, Akihiro MOTOKI <amotoki at gmail.com> wrote:

> Hi,
>
> All logs of major OpenStack IRC channels are available at
> http://eavesdrop.openstack.org/irclogs/
> In addition, we can use OpenStack meeting bot on #openstack-meeting or
> #openstack-meeting-alt.
>
> Thanks,
> Akihiro
>
>
>
> 2013/4/4 Nachi Ueno <nachi at ntti3.com>
>
>> Hi Rohon
>>
>> Good point.
>> How about to use chat window on the etherpad?
>>
>> Best
>> Nachi
>>
>> 2013/4/4 Rohon Mathieu <mathieu.rohon at gmail.com>:
>> > Hi nachi,
>> >
>> > thanks for your investment and your proposal on the VPNaas. I hope I
>> > can join on IRC. However could you log the session and report the log
>> > on etherpad or elsewhere?
>> >
>> > thanks
>> >
>> >
>> > On Thu, Apr 4, 2013 at 9:27 AM, Nachi Ueno <nachi at ntti3.com> wrote:
>> >> Hi Sachin
>> >>
>> >> OK I would like to change it to 12PM
>> >> (Is that OK > for the other guys? )
>> >>
>> >> Time updated
>> >> https://etherpad.openstack.org/HavanaVPNaaS
>> >>
>> >>
>> >>
>> >>
>> >>
>> >> 2013/4/4 Sachin Thakkar <sthakkar at vmware.com>:
>> >>> I'd like to join as well. Can we do 12PM PST instead?
>> >>>
>> >>> I think the initial kickoff will need to distinguish the various
>> facets of
>> >>> VPN that we want to cover. Reading through the proposals it appears
>> that
>> >>> many of the use cases are across the board. I'd recommend we
>> consolidate
>> >>> where appropriate and prioritize accordingly.
>> >>>
>> >>> Cheers,
>> >>> Sachin
>> >>>
>> >>> ________________________________
>> >>> From: "Alan Kavanagh" <alan.kavanagh at ericsson.com>
>> >>> To: "OpenStack Development Mailing List" <
>> openstack-dev at lists.openstack.org>
>> >>> Sent: Wednesday, April 3, 2013 8:17:10 PM
>> >>>
>> >>> Subject: Re: [openstack-dev] [Quantum] Summit Sessions
>> >>>
>> >>> +1
>> >>>
>> >>> Would like to join too, 1PM PST sounds good. I guess Mark is also
>> hoping
>> >>> that we can structure the several contributions in a good flow and
>> where
>> >>> possible combine them etc, guess we can cover that also.
>> >>>
>> >>> BR
>> >>> Alan
>> >>>
>> >>> -----Original Message-----
>> >>> From: Nachi Ueno [mailto:nachi at ntti3.com]
>> >>> Sent: April-03-13 8:59 PM
>> >>> To: OpenStack Development Mailing List
>> >>> Subject: Re: [openstack-dev] [Quantum] Summit Sessions
>> >>>
>> >>> Hi  Vasudevan
>> >>>
>> >>> +1
>> >>> I would like to join
>> >>> How about 4/5  1pm (PST)  on the IRC?
>> >>>
>> >>> I created etherpad page for this discussion
>> >>> https://etherpad.openstack.org/HavanaVPNaaS
>> >>>
>> >>> Thanks
>> >>> Nachi
>> >>>
>> >>> 2013/4/3 Vasudevan, Swaminathan (PNB Roseville)
>> >>> <swaminathan.vasudevan at hp.com>:
>> >>>> Hi Mark McClain,
>> >>>>
>> >>>> I would like to have a discussion on the VPNaaS for the quantum prior
>> >>>> to the Havana summit.
>> >>>>
>> >>>> Is there a discussion group for the VPNaaS, if so could you please
>> >>>> forward me the details.
>> >>>>
>> >>>> If not can we start a discussion group to discuss the VPNaaS
>> blueprint
>> >>>> before the summit.
>> >>>>
>> >>>>
>> >>>>
>> >>>> Thanks.
>> >>>>
>> >>>>
>> >>>>
>> >>>> Swaminathan Vasudevan
>> >>>> Systems Software Engineer (TC)
>> >>>>
>> >>>>
>> >>>> HP ProCurve
>> >>>> Hewlett-Packard
>> >>>> 8000 Foothills Blvd
>> >>>> M/S 5541
>> >>>> Roseville, CA - 95747
>> >>>> tel: 916.785.0937
>> >>>> fax: 916.785.1815
>> >>>> email: swaminathan.vasudevan at hp.com
>> >>>>
>> >>>> From: Mark McClain [mailto:mark.mcclain at dreamhost.com]
>> >>>> Sent: Tuesday, March 26, 2013 9:37 AM
>> >>>>
>> >>>>
>> >>>> To: OpenStack Development Mailing List
>> >>>> Subject: [openstack-dev] [Quantum] Summit Sessions
>> >>>>
>> >>>>
>> >>>>
>> >>>> All-
>> >>>>
>> >>>> I know we're busy working on the final push to get the docs ready for
>> >>>> the Grizzly release.  I wanted to remind the team that summit session
>> >>>> proposals are due by the end of March.
>> >>>>
>> >>>> You can submit your proposals here:
>> >>>>
>> >>>> http://summit.openstack.org.
>> >>>>
>> >>>> A couple of reminders:
>> >>>> * It is not about who proposed first.  If we have multiple proposals
>> >>>> for the same topic, the sessions most likely will be merged.
>> >>>> * We want to have a good balance of community projects vs shiny
>> features.
>> >>>> Community projects are projects that benefit the community as a whole
>> >>>> (i.e.
>> >>>> metadata service, db migration, L3 multi host).
>> >>>> * Design sessions are a good way to discuss, build consensus and
>> >>>> recruit others to help with implementation.
>> >>>> * If you have a mini-topic make a note in your proposal.  Mini-topics
>> >>>> are something we'll spend around 15mins discussing.
>> >>>>
>> >>>> Here are a few of the topics that would be good candidates to discuss
>> >>>> in
>> >>>> Portland:
>> >>>>
>> >>>> * How can we make Quantum Simpler ((tm)) For deployers? For
>> developers?
>> >>>>             * How do we make it easier to deploy Quantum in common
>> cases?
>> >>>> * Improved Unit Testing
>> >>>> * Improved Tempest Testing
>> >>>> * Improved Quantum API Testing in Nova
>> >>>> * Improving Quantum Documentation
>> >>>> * L3
>> >>>>             * IPv6 Support
>> >>>>             * Pluggable IPAM
>> >>>>             * ACLs
>> >>>>             * richer NAT API (tcp/udp port forwarding)
>> >>>> * Modular L2 and L3
>> >>>> * Database Improvements (how to handle trunk chasers, model
>> >>>> extensions)
>> >>>> * Full Multi-Host L3
>> >>>> * Device management and scheduling for services
>> >>>> * DNS and Quantum
>> >>>> * Bare-metal
>> >>>> * Physical Switch Interactions
>> >>>> * SR-IOV
>> >>>> * VPNaaS (important to separate use cases: site-to-site, sslvpn,
>> >>>> mpls-vpn)
>> >>>> * LBaaS (how do we extend upon the foundation created in Grizzly)
>> >>>>
>> >>>> Have something that's not in the list?  This list does not cover
>> >>>> everything, so feel free to propose it on the summit website.
>> >>>>
>> >>>> I hope you're excited as I am for the Grizzly release, and I'm
>> looking
>> >>>> forward discussing Havana Portland,
>> >>>>
>> >>>> mark
>> >>>>
>> >>>>
>> >>>> _______________________________________________
>> >>>> OpenStack-dev mailing list
>> >>>> OpenStack-dev at lists.openstack.org
>> >>>> http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev
>> >>>>
>> >>>
>> >>> _______________________________________________
>> >>> OpenStack-dev mailing list
>> >>> OpenStack-dev at lists.openstack.org
>> >>> http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev
>> >>>
>> >>> _______________________________________________
>> >>> OpenStack-dev mailing list
>> >>> OpenStack-dev at lists.openstack.org
>> >>> http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev
>> >>>
>> >>>
>> >>> _______________________________________________
>> >>> OpenStack-dev mailing list
>> >>> OpenStack-dev at lists.openstack.org
>> >>> http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev
>> >>>
>> >>
>> >> _______________________________________________
>> >> OpenStack-dev mailing list
>> >> OpenStack-dev at lists.openstack.org
>> >> http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev
>> >
>> > _______________________________________________
>> > OpenStack-dev mailing list
>> > OpenStack-dev at lists.openstack.org
>> > http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev
>>
>> _______________________________________________
>> OpenStack-dev mailing list
>> OpenStack-dev at lists.openstack.org
>> http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev
>>
>
>
>
> --
> Akihiro MOTOKI <amotoki at gmail.com>
>
> _______________________________________________
> OpenStack-dev mailing list
> OpenStack-dev at lists.openstack.org
> http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev
>
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.openstack.org/pipermail/openstack-dev/attachments/20130404/df1be553/attachment.html>