[openstack-dev] [neutron][networking-ovn] OVN vs. OpenDayLight

Kyle Mestery mestery at mestery.com
Thu Jun 9 21:28:50 UTC 2016


On Thu, Jun 9, 2016 at 4:19 PM, Assaf Muller <assaf at redhat.com> wrote:
> On Thu, Jun 9, 2016 at 5:06 PM, Kyle Mestery <mestery at mestery.com> wrote:
>> On Thu, Jun 9, 2016 at 2:11 PM, Assaf Muller <assaf at redhat.com> wrote:
>>> On Thu, Jun 9, 2016 at 1:48 PM, Ben Pfaff <blp at ovn.org> wrote:
>>>> On Thu, Jun 09, 2016 at 10:28:31AM -0700, rezroo wrote:
>>>>> I'm trying to reconcile differences and similarities between OVN and
>>>>> OpenDayLight in my head. Can someone help me compare these two technologies
>>>>> and explain if they solve the same problem, or if there are fundamental
>>>>> differences between them?
>>>>
>>>> OVN implements network virtualization for clouds of VMs or containers or
>>>> a mix.  Open Daylight is a platform for managing networks that can do
>>>> anything you want.
>>>
>>> That is true, but when considering a Neutron backend for OpenStack
>>> deployments, people choose a subset of OpenDaylight projects and the
>>> end result is a solution that is comparable in scope and feature set.
>>> There are objective differences in where the projects are in their
>>> lifetime, the HA architecture, the project's consistency model between
>>> the neutron-server process and the backend, the development velocity,
>>> the community size and the release model.
>>>
>> Fundamentally, the main difference is that OVN does one thing: It does
>> network virtualization. OpenDaylight _MAY_ do network virtualization,
>> among other things, and it likely does network virtualization in many
>> different ways. Like Ben said:
>>
>> "Open Daylight is a platform for managing networks that can do
>> anything you want."
>
> I agree, but I don't think that was what was asked or makes for an
> interesting discussion. I think the obvious comparison is OVN to
> ML2/ODL using the ovsdb ODL project.
>
OK, I'll bite. :)

Fundamentally, a project's focus is absolutely important, especially
when a comparison is asked. When you ask the question: "How can OVN or
ODL solve being a backend layer for Neutron?", for example, the answer
with OVN is simple: You do it this way, and it works. For ODL, the
question is much more nuanced, as it depends on *what* components in
ODL you are using.

Also, yes, the comparison between "ML2+python agents" vs. "ML2+OVN" is
much more relevant IMHO.

Thanks!
Kyle

>>
>> Thanks,
>> Kyle
>>
>>>>
>>>> __________________________________________________________________________
>>>> 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
>
> __________________________________________________________________________
> 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



More information about the OpenStack-dev mailing list