Hello Aditya:

If you don't have any specific requirement, I would choose one of the Neutron in-tree ML2 plugins: ML2/OVS or ML2/OVN (and ML2/SR-IOV, that can run with the other two).

About which one you can choose, I won't point you to any of them. I would prefer you to review the different architectures:
* OVS: https://docs.openstack.org/liberty/networking-guide/scenario-classic-ovs.html (this is an old but still valid document to see the different ML2/OVS deployments)
* OVN: https://www.openstack.org/videos/summits/austin-2016/practical-ovn-architecture-deployment-and-scale-of-openstack-networking

Regards.


On Wed, Oct 5, 2022 at 10:37 PM Aditya Sathish <saditya@vt.edu> wrote:
Hi Lajos and Rodolfo,

First of all thank you for your previous replies. After discussing it with my team over here, we have decided to look at other alternatives beyond ONOS for implementing an SDN controller with OpenStack.

Lajos, as you mentioned about OVN, we can perform SDN control on the VM instances using this. One extension we would like to do is to use OVN to control an openflow hardware switch. The idea is to allow different users over a network to access the VM instances. Any idea if I can get this done through OVN?

I also tried to check out OpenDayLight but even this has not been updated in some time.

Any replies would be greatly appreciated!

Regards,
Aditya

On Thu, Sep 22, 2022 at 12:22 PM Lajos Katona <katonalala@gmail.com> wrote:
Seems gmail lost some chars from Rodolfo's address, resending.

Lajos Katona <katonalala@gmail.com> ezt írta (időpont: 2022. szept. 22., Cs, 17:55):
Hi,
Thanks for considering this question. I do not add this topic now to the agenda, of course it can be discussed any time :-)
In openstack OVN as an SDN controller is tested, and more and more companies are using it, so for long term I would check it.
OVN is now in-tree in Neutron code base, meaning that you don't need any extra code, you can just use Neutron.
OVN uses OVS as soft switch and the OVN code is written in C, and originally started by the same team who develops OVS.

If you need any advice, or would like to discuss any topics with the team just ping us on #openstack-neutron channel.

Best wishes
Lajos Katona (lajoskatona)


Aditya Sathish <saditya@vt.edu> ezt írta (időpont: 2022. szept. 22., Cs, 17:00):
Hi Lajos,

Thank you for the email. Unfortunately, I'm not sure if I can dedicate time to maintain this release-on-release. However, I forked the networking-onos repository and currently verified it with DevStack Zed along with tempest. (https://github.com/adityasathis/networking-onos). Considering the changes so far involved only replacing some code to account for changes in the ML2 callback interface, I think the support should not be too time consuming if we assume that the ML2 plugin interface remains the same.

If we cannot find a way to support networking-onos for long-term support, do you know a better way to understand the industry implementation of using SDN controllers with OpenStack?

Regards,
Aditya.

On Thu, Sep 22, 2022 at 10:46 AM Lajos Katona <katonalala@gmail.com> wrote:
Hi,
Do you think that you can maintain networking-onos, if you think yes, we can discuss this topic on next drivers meeting (as Rodolfo wrote previously).
Just ping me on IRC (#openstack-neutron lajoskatona) and I add this topic for you to the agenda:

Best Wishes
Lajos Katona (lajoskatona)

Aditya Sathish <saditya@vt.edu> ezt írta (időpont: 2022. szept. 20., K, 17:48):
Hello!

I am trying to integrate an SDN controller with our lab's OpenStack network. Currently, we have already deployed a version of ONOS to serve our needs and I have been following the SONA project which uses the networking-onos ML2 plugin with OpenStack. However, it seems that the networking-onos project has been retired since the Train release.

Is there any way I can get ONOS to work with OpenStack Yoga? If not, what is the go-to way to integrate an SDN controller with OpenFlow support with Neutron??

Any help will be much appreciated.

Regards,
Aditya.