Madhu, I don't think this is the right way to handle this -- IMO Neutron
shouldn't need to be aware of details of the virtualization
implementation. In keeping with the notion of Neutron being focused on
providing an abstraction layer, and details and complexity of network
configuration being pushed to the SDN controller, it makes more sense to
me to activate one (or more in the future) virtual network implementations
in OpenDaylight.

thanks.

-- Anees

opendove-dev-bounces@... wrote on 12/02/2013 10:43:31
AM:

From: Madhu Venguopal <vmadhu@...>
To: opendove-dev@..., "vtn-
dev@..." <vtn-dev@...>,
"ovsdb-dev@..." <ovsdb-
dev@...>, "Kyle Mestery (kmestery)"

<kmestery@...>,

Date: 12/02/2013 10:45 AM
Subject: [opendove-dev] ODL - Neutron API enhancement to include the
southbound driver info
Sent by: opendove-dev-bounces@...

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 :

[[post-config|/etc/neutron/plugins/ml2/ml2_conf.ini]]
[ml2_odl]
url=http://192.168.56.1:8080/controller/nb/v2/neutron
username=admin
password=admin
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.

Thanks,
Madhu_______________________________________________
opendove-dev mailing list
opendove-dev@...
https://lists.opendaylight.org/mailman/listinfo/opendove-dev