[openstack-dev] [Neutron] Design Summit Session - Containers Orchestration platforms Integration with Neutron

Kyle Mestery mestery at mestery.com
Mon Oct 19 14:30:30 UTC 2015


On Sun, Oct 18, 2015 at 1:54 PM, Murali R <muralirdev at gmail.com> wrote:

> Will there be an irc opened for these sessions to join remotely?
>
> We will have people in the room who will be on IRC, yes, just use
#openstack-neutron. Even better, you can comment on the etherpad live while
the session is going on, which is a good way to attend remotely as well.


>
>
> On Sun, Oct 18, 2015 at 9:19 AM, Armando M. <armamig at gmail.com> wrote:
>
>> Perhaps adding a section for 'collecting ideas' right at the bottom of
>> the etherpad will help directing input.
>>
>> We should strive for keeping the session focussed, sessions are only 40
>> mins, and realistically we'll only have 30 mins to talk about the meaty
>> stuff. If we want to go through bullet by bullet, we'll need an entire
>> summit :)
>>
>> Cheers,
>> Armando
>>
>>
>> On 18 October 2015 at 09:14, Armando M. <armamig at gmail.com> wrote:
>>
>>> Gal,
>>>
>>> [2] is not meant to be edited by anyone just yet. This will lead to
>>> chaos and an unproductive session. Once the link is out is obvious that
>>> anyone can edit, but welcoming input is a recipe for disaster!
>>>
>>> I appreciate the initiative, but please consider running thoughts by me
>>> for advice.
>>>
>>> Cheers,
>>> Armando
>>>
>>> On 18 October 2015 at 04:09, Gal Sagie <gal.sagie at gmail.com> wrote:
>>>
>>>> Hello All,
>>>>
>>>> In OpenStack Tokyo summit we will have a design summit session for
>>>> containers networking
>>>> and containers orchestration engines integration with Neutron [1].
>>>>
>>>> Please feel free to edit the session etherpad [2] with relevant topics,
>>>> if you are working
>>>> and have any gaps or needs from Neutron in that area, please share.
>>>>
>>>> Even if we cant resolve everything in one session, i think it would be
>>>> great to at least understand
>>>> the problems and document them so we can address the needs and
>>>> priorities during the upcoming cycle.
>>>>
>>>> Thanks
>>>> Gal.
>>>>
>>>> [1]
>>>> http://mitakadesignsummit.sched.org/event/9be2ec1db45ea3267f811b8d35816e1c#.ViN7rLOY7CI
>>>> [2] https://etherpad.openstack.org/p/mitaka-neutron-labs-orchestration
>>>>
>>>>
>>>> __________________________________________________________________________
>>>> OpenStack Development Mailing List (not for usage questions)
>>>> Unsubscribe:
>>>> OpenStack-dev-request at 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-request at 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-request at lists.openstack.org?subject:unsubscribe
> 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/20151019/af1370e1/attachment.html>


More information about the OpenStack-dev mailing list