[openstack-dev] [Neutron] VLAN-aware VMs meeting

Kyle Mestery mestery at mestery.com
Mon Jun 15 13:52:24 UTC 2015


On Mon, Jun 15, 2015 at 7:40 AM, Ildikó Váncsa <ildiko.vancsa at ericsson.com>
wrote:

> Hi Kyle,
>
> > -----Original Message-----
> > From: Kyle Mestery [mailto:mestery at mestery.com]
> > Sent: June 15, 2015 04:26
> > To: OpenStack Development Mailing List (not for usage questions)
> > Subject: Re: [openstack-dev] [Neutron] VLAN-aware VMs meeting
> >
> > On Fri, Jun 12, 2015 at 8:51 AM, Ildikó Váncsa <
> ildiko.vancsa at ericsson.com>
> > wrote:
> >
> >
> >       Hi,
> >
> >
> >
> >       Since we reopened the review for this blueprint we’ve got a
> > large number of comments. It can be clearly seen that the original
> proposal
> > has to be changed, although it still requires some discussion to define a
> > reasonable design that provides the desired feature and is aligned with
> the
> > architecture and guidelines of Neutron. In order to speed up the process
> to
> > fit into the Liberty timeframe, we would like to have a discussion about
> this.
> > The goal is to discuss the alternatives we have, decide which to go on
> with
> > and sort out the possible issues. After this discussion the blueprint
> will be
> > updated with the desired solution.
> >
> >
> >
> >       I would like to propose a time slot for _next Tuesday (06. 16.),
> > 17:00UTC – 18:00UTC_. I would like to have the discussion on the
> > #openstack-neutron channel, that gives a chance to guys who might be
> > interested, but missed this mail to attend. I tried to check the slot,
> but please
> > let me know if it collides with any Neutron related meeting.
> >
> >
> >
> >
> > This looks to be fine. I would suggest that it may make more sense to
> have it
> > in an #openstack-meeting channel, though we can certainly do a free-form
> > chat in #openstack-neutron as well. I think the desired end-goal here
> should
> > be to figure out any remaining nits that are being discussed on the spec
> so
> > we can move forward in Liberty.
> >
>
> I wasn’t sure that it is a good idea to bring an unscheduled meeting to
> the meeting channels. Is it acceptable to hold an ad-hoc meeting there or
> does it have to be registered somewhere even if it's one occasion? As much
> as I saw the #openstack-meeting-4 channel is available although the list of
> meetings and the .ical file is not in sync, it's not taken in either.
> Should we try it there?
>
>
I think as long as there isn't a scheduled meeting in place, we can use the
channel for a one-off meeting. It has the added benefit of being logged in
the same way as other meetings, and we can focus the discussion.

I agree with the desired outcome, so that we can start the implementation
> as soon as possible. I will try to send out an agenda before the meeting
> with the points that we should discuss.
>
>
Perfect! I've added a note to the Neutron meeting for tomorrow [1] to
highlight this. If you get the agenda written, please add a pointer in the
Neutron meeting agenda in the same place.

[1]
https://wiki.openstack.org/wiki/Network/Meetings#Announcements_.2F_Reminders


> Thanks and Best Regards,
> Ildikó
>
> >
> > Thanks,
> >
> > Kyle
> >
> >
> >
> >
> >
> >
> >       Thanks and Best Regards,
> >
> >       Ildikó
> >
> >
> >       _______________________________________________
> > ___________________________
> >       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/20150615/a3b11bbf/attachment.html>


More information about the OpenStack-dev mailing list