Open Stack

On Fri, Jun 24, 2016 at 2:36 PM, Jonathan Proulx <jon at csail.mit.edu> wrote:

> On Fri, Jun 24, 2016 at 02:19:33PM -0400, Russell Bryant wrote:
> :I had some feedback regarding the Neutron driver section of the user
> :survey.  If there is a better place to send this feedback, please let me
> :know.
> :
> :1) I think it's very confusing to include ML2 as an option here.  ML2 is a
> :framework, not a specific technology.  It's not really comparable with
> :anything else on the list.  I think it would make the most sense to just
> :remove it from the list as an option on its own.
>
> I agree here ML2 isn't really a driver you need to be ML2+<something>.
>
> :
> :2) "Open vSwitch" is a bit confusing as an option, as it could mean
> :multiple things.  To most people, it means using Neutron with the OVS ML2
> :plugin and the Neutron OVS agent.  However, there are several other
> :solutions that involve Open vSwitch itself.  OpenDaylight may be used with
> :Open vSwitch.  I believe Midonet uses the kernel portion of Open vSwitch,
> :but not userspace.  VMware NSX uses Open vSwitch.
> :
> :"Neutron ML2 OVS plugin + Neutron OVS agent" is more clear, but perhaps
> :long.  "Neutron ML2 OVS plugin+agent" is a bit shorter?
>
> I hadn't considered that as confusing, though with OVN it may be
> becoming more so.
>
> "Neutron ML2 OVS plugin+agent" is still a bit of a mouthful, do you
> think "Neutron OVS plugin" leaves out too much?
>

​"Neutron OVS plugin" is probably good enough.  Technically it's the ML2
plugin with the OVS ML2 mechanism driver + some set of ML2 type drivers,
but that's even worse.  :-)  I don't think "Neutron OVS plugin" would be
interpreted any other way than what is intended, and that's what's
important.

>
>
> :3) I'd like to add "OVN (Open Virtual Network)" as an option.  It's a new
> :option for Neutron being built within the Open vSwitch community (and is
> :another option that includes Open vSwitch as part of the picture).
> :
> :4) There are more options that could be added.  Maybe they are options and
> :just got grouped into "other" in the results I'm looking at.
> :
> :
> http://docs.openstack.org/developer/neutron/stadium/sub_projects.html#official-sub-project-list
> :
> :Additions could include, at least:
> :
> : - Calico
> : - ONOS
> : - Dragonflow
>
> The general case for long lists of optional components is we break out
> the most popular ones as specific choices and if something lumped in
> 'other' starts to break out of the noise we list it on its own in the
> next survey.
>
> This isn't written in stone.  If OVN (or soemthing else) is new and you
> think it has
> gathered significant adoption already we could certainly consider
> directly adding it to the list rather than having it skew 'other'.
>

​It's new, but is already seeing some early adoption.  We expect the first
non-experimental release just ahead of the OpenStack Newton release.​

​Given that the "Neutron OVS plugin" ;-) is the most popular result on the
survey, and OVN is being pushed by the Open vSwitch community, it seems
quite likely that adoption could pick up and it would be good to capture
exactly what that looks like in the survey.

Thanks for considering my feedback,​

-- 
Russell Bryant
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.openstack.org/pipermail/user-committee/attachments/20160624/0e319548/attachment.html>