Re: [OpenDaylight Discuss] [vtn-dev] ODL - Neutron API enhancement to include the southbound driver info

Anees A Shaikh <aashaikh@...>

As we've discussed at some length, Affinity is not in the same category of
function as the virtualization implementations, and also doesn't implement
the Neutron APIs, so I don't think the issue of multiple Neutron API
clients applies to Affinity.

Per Tai-san's note, we're addressing the issue of overlapping control of
the network by i) making the Affinity example flows default-off and
optional, and ii) providing configuration support so that the
virtualization edition runs a single implementation (i.e., one of
VTN/OpenDOVE/OVSDB). (unless something else was discussed in the TWS
call earlier today)


-- Anees

discuss-bounces@... wrote on 12/02/2013 07:55:37 PM:

From: Hideyuki Tai <h-tai@...>
To: "Ed Warnicke (eaw)" <eaw@...>,
Cc: "<discuss@...>"
<discuss@...>, "ovsdb-dev@..."
<ovsdb-dev@...>, "<affinity-
dev@...>" <affinity-dev@...>,
"opendove-dev@..." <opendove-
dev@...>, Madhu Venguopal <vmadhu@...>,
"vtn-dev@..." <vtn-dev@...>
Date: 12/02/2013 07:56 PM
Subject: Re: [OpenDaylight Discuss] [ovsdb-dev] [vtn-dev] ODL -
Neutron API enhancement to include the southbound driver info
Sent by: discuss-bounces@...

Hi Ed,

Madhu’s proposal focus on the co-existing problem between southbound
drivers for Neutron Interface.
I explained about this problem in the following mail.
To solve this problem, I think Madhu’s proposal is good.

The co-existing problem between Affinity, VTN Manager, and
simpleforwarding is a different problem.
In the Virtualization Edition, more than one application exist, and
they try to control the same network resources simultaneously.
Because different applications have different policies on how to
control network resources, it’s obvious that flow entries installed
by different applications are inconsistent.
To solve this problem, we need other solution.

Hideyuki Tai

From: Ed Warnicke (eaw) [mailto:eaw@...]
Sent: Tuesday, December 03, 2013 11:44 AM
To: Tai, Hideyuki
Cc: Madhu Venguopal; opendove-dev@...; vtn-
dev@...; ovsdb-dev@...; Kyle
Mestery (kmestery); <affinity-dev@...>;
Subject: Re: [ovsdb-dev] [vtn-dev] ODL - Neutron API enhancement to
include the southbound driver info

So I see the value of this... But what about Affinity?


Sent from my iPad

On Dec 2, 2013, at 7:57 PM, "Hideyuki Tai" <h-tai@...> wrote:
Hi Madhu,

I completely agree with your opinion.

Hideyuki Tai

From: vtn-dev-bounces@... [mailto:vtn-dev-
bounces@...] On Behalf Of Madhu Venguopal
Sent: Tuesday, December 03, 2013 3:44 AM
To: opendove-dev@...; vtn-dev@...;
ovsdb-dev@...; Kyle Mestery (kmestery)
Subject: [vtn-dev] ODL - Neutron API enhancement to include the
southbound driver info

Hi Kyle, OpenDove, VTN & OVSDB devs,

Since we all have integrations completed with the Neutron nb-apis
and these southbound drivers (ovsdb, open-dove, vtn)
cannot co-exist in the same virtualization edition, I was thinking
of extending the Neutron NB-API to include the information
on which Southbound driver to choose. By doing that, all of these
bundles can co-exist in the same virtualization edition and
based on the Openstack/Neutron deployment, the customer can choose
which ODL-southbound to use. This can be done along
with the existing configuration that is needed on the OpenStack to
point to the ODL-Northbound API & the authentication details.
something like :

southbound=[ovsdb | opendove | vtn]

We can ofcourse keep this configuration inside the OpenDaylight as
well. But, having it done as part of Neutron provides a single
point of configuration and let the Neutron administrator decide on
what is to be done, rather than depending on another administrator
who might handle the Opendaylight Controller.

Please share your opinion and I can get this thing done on the
Opendaylight side.

ovsdb-dev mailing list
Discuss mailing list

Join { to automatically receive all group messages.