On Fri, 2021-08-27 at 13:03 +0530, Hrishikesh Karanjikar wrote:
Hi Slawek,
Thanks for your reply. Can you guide Which SDN controller is best and supported in Netron via ML2 plugin/driver.
in general the design of openstack/neutron is such that it owns the ovs bridges and flow rules and you as a openstack operator shoudl not need to manage anything. neutron itself is an sdn contoler that allows self service network configureation vai its rest api and an abstraction layer between the end user and underlying implemantion. it can delegate the swich configuration to external sdn contoler but even in that case you are not intned to modify flows on the integration bridge via the sdn contoler manually. the sdn contoler can be used to manage your top of rack swithc and other infrasturue not managed by neutron but there is ment to be a seperation of concerns. all networking on comptue nodes shoudl be manageged via the neutron api and only your datacenter infrastucrue should be manageve by you via the sdn contoelr.
Thanks, Hrishikesh
On Fri, Aug 27, 2021 at 12:18 PM Slawek Kaplonski <skaplons@redhat.com> wrote:
Hi,
On piątek, 27 sierpnia 2021 07:18:10 CEST Hrishikesh Karanjikar wrote:
Hi Sean,
I am new to this domain. My use case is simple,
I have a node that runs OvS and I want to manage the flows remotely using an SDN controller. Initially I tried with ODL but it does not have a Web UI like ONOS has. So I was using ONOS. I am not sure if Neutron would do the same. If it is possible then I will not need any other SDN controller.
Neutron is generally providing connectivity for Your VMs/routers/etc and it may use different backend. If You will use e.g. ML2 plugin with OVN backend, Neutron will configure OVN and OVN will then configure flows in OVS on the nodes to achieve that. But if You are looking for a tool which will allow You to see OpenFlow rules on each node, and manipulate them with some GUI, then Neutron is not for You. It don't have such functionality.
I am not doing any deployment yet.
Thanks, Hrishikesh
On Thu, Aug 26, 2021 at 5:00 PM Sean Mooney <smooney@redhat.com> wrote:
On Thu, 2021-08-26 at 16:41 +0530, Hrishikesh Karanjikar wrote:
Hi Sean,
Thanks for your reply. I was expecting the same answer as I also read the github link you
sent.
I may need to try older versions of openstack in that case.
do you specificaly need onos for some reason.
if not i would not suggest building a production deployment with something that realiticlly is very unlikely to ever be supported again. you basically will be stuck on train with no upgrade path.
Hrishikesh
On Thu, Aug 26, 2021 at 4:27 PM Sean Mooney <smooney@redhat.com> wrote:
On Thu, 2021-08-26 at 15:31 +0530, Hrishikesh Karanjikar wrote: > Hi, > > Does Openstack latest release support ONOS?
the short answer is no technially upstream has never supported it because it was a big tent projec that was never an offical deliverable of the netwroking team. https://github.com/openstack-archive/networking-onos has been retired as has https://opendev.org/openstack/networking-onos. the last release seams to have been from train but even then im not sure that it was still active. it looks like the onos projecct move the openstack install info under
teh
obsolete paages
https://wiki.onosproject.org/display/ONOS/networking-onos+install+guides+per
+each+OpenStack+version>
so it does not look like the intend to support openstack anymore.
-- Slawek Kaplonski Principal Software Engineer Red Hat