Hi Sean, In my last email I forgot to add the openstack discussion email so I sent it again. I am really great ful for the insight you have provided. I will check the links and ml2/ovs ml2/ovn support mentioned by you. Thanks, Hrishikesh On Fri, Aug 27, 2021, 7:41 PM Sean Mooney <smooney@redhat.com> wrote:
On Fri, 2021-08-27 at 19:09 +0530, Hrishikesh Karanjikar wrote:
Hi Sean,
Thanks a lot for the clarification. I am wondering how smart nics attached to a compute node (which runs ovs-dpdk) can be configured using sdn controllers so that the ovs/tunneling/ipsec functionality on the compute node is offloaded to smartnic and compute node cpu is free to do other stuffs?
i responed privatly too but what you are discribing is hardware offloaded ovs https://docs.openstack.org/neutron/latest/admin/config-ovs-offload.html which is supported by ml2/ovs and ml2/ovn although with most testign done with ml2/ovs
in general this feature is not compatible with sdn contolers today although as i noted in my other respocne contrail has limited support for hardwar offload with there vrouter solution but i generally do not recommend that solution since it has miniumal testing upstream.
there is some other work to move ovs entirely to run on the smart nics where those smatnics have embded arm cores. that work is very much not ready for production and still under design there are 3 competting approches to taht on via ironic one via cybrog and one in nova. they all work slightly differnetly and serve slightly differnt usecase and hardware.
if you want somethin you can use today or even in the next 12 months you want hardware offload ovs with ml2/ovs or possibel ml2/ovn although ovn support for hardware offload is much newer and less well tested although long term that is likely where more of the investment will go.
Thanks, Hrishikesh
On Fri, Aug 27, 2021 at 5:38 PM Sean Mooney <smooney@redhat.com> wrote:
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
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
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
will 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
via then I 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