<div dir="ltr"><div dir="ltr"><br></div><br><div class="gmail_quote"><div dir="ltr" class="gmail_attr">On Mon, Nov 16, 2020 at 3:31 PM Alfredo Moralejo Alonso <<a href="mailto:amoralej@redhat.com">amoralej@redhat.com</a>> wrote:<br></div><blockquote class="gmail_quote" style="margin:0px 0px 0px 0.8ex;border-left:1px solid rgb(204,204,204);padding-left:1ex"><div dir="ltr"><div dir="ltr"><br></div><br><div class="gmail_quote"><div dir="ltr" class="gmail_attr">On Mon, Nov 16, 2020 at 3:28 PM Satish Patel <<a href="mailto:satish.txt@gmail.com" target="_blank">satish.txt@gmail.com</a>> wrote:<br></div><blockquote class="gmail_quote" style="margin:0px 0px 0px 0.8ex;border-left:1px solid rgb(204,204,204);padding-left:1ex">Alfredo,<br>
<br>
Last followup question, Once victora release comes out in future in<br>
that case does openstackvswitch2.13 will be default part of<br>
rdo-victoria packages right? OR do i need to install<br>
centos-release-nfv-openvswitch extra repo to get that package to<br>
install?<br>
<br></blockquote><div><br></div><div>No, it will be installed and enabled by default when installing centos-release-openstack-victoria package or downloading [1] if you plan to use RDO Trunk repo.</div><div><br></div><div>[1] <a href="https://trunk.rdoproject.org/centos8-victoria/delorean-deps.repo" target="_blank">https://trunk.rdoproject.org/centos8-victoria/delorean-deps.repo</a></div></div></div></blockquote><div><br></div><div><br></div><div>BTW, victoria is ready to be used <a href="https://lists.centos.org/pipermail/centos-devel/2020-November/056179.html">https://lists.centos.org/pipermail/centos-devel/2020-November/056179.html</a></div><div><br> </div><blockquote class="gmail_quote" style="margin:0px 0px 0px 0.8ex;border-left:1px solid rgb(204,204,204);padding-left:1ex"><div dir="ltr"><div class="gmail_quote"><div><br></div><div> </div><blockquote class="gmail_quote" style="margin:0px 0px 0px 0.8ex;border-left:1px solid rgb(204,204,204);padding-left:1ex">
~S<br>
<br>
On Tue, Nov 10, 2020 at 4:41 AM Alfredo Moralejo Alonso<br>
<<a href="mailto:amoralej@redhat.com" target="_blank">amoralej@redhat.com</a>> wrote:<br>
><br>
><br>
><br>
> On Mon, Nov 9, 2020 at 4:42 PM Satish Patel <<a href="mailto:satish.txt@gmail.com" target="_blank">satish.txt@gmail.com</a>> wrote:<br>
>><br>
>> Just to follow up,<br>
>><br>
>> I have successfully deployed ovs+dpdk on centOS-8 on ussuri using the<br>
>> following repo. (openvswitch2.13)<br>
>><br>
>> dnf install -y centos-release-nfv-openvswitch<br>
>><br>
>> Just curious why RPM package name is openvswitch2.13 instead of<br>
>> openvswitch-2-13 (Let me guess because of centOS RDO provides that<br>
>> same naming style right?)<br>
><br>
><br>
> Actually not. Those packages are rebuilt from Red Hat Fast Datapath repositories [1] which use those names. The actual reason is that those names allow to have openvswitch 2.11 and 2.13 in the same repositories and let user choose the version that each project wants to use from it.<br>
><br>
> [1] <a href="ftp://ftp.redhat.com/pub/redhat/linux/enterprise/8Base/en/Fast-Datapath/SRPMS/" rel="noreferrer" target="_blank">ftp://ftp.redhat.com/pub/redhat/linux/enterprise/8Base/en/Fast-Datapath/SRPMS/</a><br>
><br>
>><br>
>> On Wed, Nov 4, 2020 at 9:34 AM Satish Patel <<a href="mailto:satish.txt@gmail.com" target="_blank">satish.txt@gmail.com</a>> wrote:<br>
>> ><br>
>> > That is great news, it's coming back in victoria. Thanks for the update.<br>
>> ><br>
>> > For fun this is what i did, I downloaded openvswitch-2.12.x.x.x.srpm<br>
>> > and re-compile RPM with --with-dpdk support against dpdk-18.11 and i<br>
>> > was successfully able to produce RPM.<br>
>> ><br>
>> > I have installed RPM on my computer node and it looks good so far, i<br>
>> > am successfully able to add my nic to OVS using DPDK interface. I have<br>
>> > noticed CPU usage of ovs-vswitchd showing 100% but it looks like that<br>
>> > is expected behavior.<br>
>> ><br>
>> > [root@compute-2 ~]# ovs-vswitchd --version<br>
>> > ovs-vswitchd (Open vSwitch) 2.12.0<br>
>> > DPDK 18.11.2<br>
>> ><br>
>> ><br>
>> > [root@compute-2 ~]# ovs-vsctl show<br>
>> > Bridge br-provider<br>
>> > Controller "tcp:<a href="http://127.0.0.1:6633" rel="noreferrer" target="_blank">127.0.0.1:6633</a>"<br>
>> > is_connected: true<br>
>> > fail_mode: secure<br>
>> > datapath_type: netdev<br>
>> > Port phy-br-provider<br>
>> > Interface phy-br-provider<br>
>> > type: patch<br>
>> > options: {peer=int-br-provider}<br>
>> > Port br-provider<br>
>> > Interface br-provider<br>
>> > type: internal<br>
>> > Port "dpdk-0"<br>
>> > Interface "dpdk-0"<br>
>> > type: dpdk<br>
>> > options: {dpdk-devargs="0000:06:00.0"}<br>
>> > ovs_version: "2.12.0"<br>
>> ><br>
>> ><br>
>> > I didn't see any issue so very curious when you said openvswitch-2.12<br>
>> > is broken. I would like to know more if i am doing wrong.<br>
>> ><br>
>> > I am running a fairly large openstack cloud using LinuxBridge/SR-IOV<br>
>> > and am very happy with simplicity. First time I am trying to deploy<br>
>> > OpenvSwitch in the lab to see how everything looks, a little nervous<br>
>> > because I heard lots of nightmare stories from various folks, but it<br>
>> > looks like the future is OVS.<br>
>> ><br>
>> > I will try NFV repo and see how it goes :)<br>
>> ><br>
>> > On Wed, Nov 4, 2020 at 4:59 AM Alfredo Moralejo Alonso<br>
>> > <<a href="mailto:amoralej@redhat.com" target="_blank">amoralej@redhat.com</a>> wrote:<br>
>> > ><br>
>> > ><br>
>> > ><br>
>> > > On Tue, Nov 3, 2020 at 6:04 PM Satish Patel <<a href="mailto:satish.txt@gmail.com" target="_blank">satish.txt@gmail.com</a>> wrote:<br>
>> > >><br>
>> > >> Thanks for reply,<br>
>> > >><br>
>> > >> I am using Openstack-Ansible deployment tool to run Openstack. I am<br>
>> > >> running a stable/ussuri release at the moment. current OVS package<br>
>> > >> coming from rdo-dep repository of Ussuri release. It would be great if<br>
>> > >> we have openvswitch+DPDK supported RPM for that repo, otherwise i am<br>
>> > >> stuck here and i have to re-compile RPM myself and need to pushout<br>
>> > >> with a custom repo. (Does victoria going to support the DPDK version<br>
>> > >> of openvswitch?)<br>
>> > ><br>
>> > ><br>
>> > > yes, Victoria has openvsiwtch 2.13 with dpdk enabled.<br>
>> > ><br>
>> > > if you can move to victoria, it would be the easiest way and my recommendation.<br>
>> > ><br>
>> > >><br>
>> > >><br>
>> > >> [root@compute-1 SPECS]# ovs-vswitchd --version<br>
>> > >> ovs-vswitchd (Open vSwitch) 2.12.0<br>
>> > >> [root@compute-1 SPECS]#<br>
>> > >><br>
>> > >> [root@compute-1 SPECS]# repoquery -i openvswitch<br>
>> > >> Last metadata expiration check: 2:57:01 ago on Tue 03 Nov 2020 06:02:46 AM PST.<br>
>> > >> Name : openvswitch<br>
>> > >> Version : 2.12.0<br>
>> > >> Release : 1.1.el8<br>
>> > >> Architecture : aarch64<br>
>> > >> Size : 1.9 M<br>
>> > >> Source : openvswitch-2.12.0-1.1.el8.src.rpm<br>
>> > >> Repository : rdo-deps<br>
>> > >><br>
>> > >> [root@compute-1 SPECS]# cat /etc/yum.repos.d/rdo-deps.repo<br>
>> > >> [rdo-deps]<br>
>> > >> module_hotfixes=1<br>
>> > >> baseurl = <a href="https://trunk.rdoproject.org/centos8-ussuri/deps/latest/" rel="noreferrer" target="_blank">https://trunk.rdoproject.org/centos8-ussuri/deps/latest/</a><br>
>> > >><br>
>> > ><br>
>> > > AFAIK, Ussuri should work also with 2.13 but you need to do some steps:<br>
>> > ><br>
>> > > 1. Add NFV SIG repository:<br>
>> > ><br>
>> > > dnf install -y centos-release-nfv-openvswitch<br>
>> > ><br>
>> > > 2. Package name change in NFS SIG from openvswitch to openvswitch2.13 so you need some wrapper packages for compatibility. You can download those wrappers from <a href="https://cbs.centos.org/koji/buildinfo?buildID=31051" rel="noreferrer" target="_blank">https://cbs.centos.org/koji/buildinfo?buildID=31051</a> (you need all RPMs in noarch list), create a local repository with them and add it to all nodes in the cluster.<br>
>> > ><br>
>> > > Update all nodes and you should get openvswitch updated to new packages openvswitch2.13 (and ovn2.13 if you are using ovn). Note that you may need to re-enable and restart openvswitch services manually after the update.<br>
>> > ><br>
>> > >> On Tue, Nov 3, 2020 at 10:47 AM Alfredo Moralejo Alonso<br>
>> > >> <<a href="mailto:amoralej@redhat.com" target="_blank">amoralej@redhat.com</a>> wrote:<br>
>> > >> ><br>
>> > >> > Hi,<br>
>> > >> ><br>
>> > >> > On Tue, Nov 3, 2020 at 3:48 PM Satish Patel <<a href="mailto:satish.txt@gmail.com" target="_blank">satish.txt@gmail.com</a>> wrote:<br>
>> > >> >><br>
>> > >> >> Folks,<br>
>> > >> >><br>
>> > >> >> Recently i started playing with openvswitch on centOS for openstack<br>
>> > >> >> SDN, and found centos8 doesn't have openvswitch with dpdk support, I<br>
>> > >> >> was looking around RPM but didn't find any RPM also, do i need to<br>
>> > >> >> compile openviswtch+dpdk support or rpm is available but i am not<br>
>> > >> >> aware of it.<br>
>> > >> >><br>
>> > >> ><br>
>> > >> > The build of openvswitch included in Train and Ussuri, openvswitch-2.12-1.el8 has dpdk support disabled as it doesn't work with the version of dpdk included in CentOS 8.2.<br>
>> > >> ><br>
>> > >> > Since Victoria we have openvswitch 2.13 with dpdk enabled coming from NFV SIG builds. We may backport this to Ussuri although we need to validate if it breaks updates somehow, so it's still work in progress.<br>
>> > >> ><br>
>> > >> > RDO Victoria will be announced very soon (we are in the process of pushing latest required builds to CentOS official mirrors today).<br>
>> > >> ><br>
>> > >> > What version of RDO are you using and how are you deploying it? are you using TripleO?, depending on it, we may be able to provide some workaround to update OpenvSwitch to the latest openvswitch manually.<br>
>> > >> ><br>
>> > >> > Regards,<br>
>> > >> ><br>
>> > >> > Alfredo<br>
>> > >> ><br>
>> > >> >> ~S<br>
>> > >> >> _______________________________________________<br>
>> > >> >> CentOS-devel mailing list<br>
>> > >> >> <a href="mailto:CentOS-devel@centos.org" target="_blank">CentOS-devel@centos.org</a><br>
>> > >> >> <a href="https://lists.centos.org/mailman/listinfo/centos-devel" rel="noreferrer" target="_blank">https://lists.centos.org/mailman/listinfo/centos-devel</a><br>
>> > >> >><br>
>> > >> > _______________________________________________<br>
>> > >> > CentOS-devel mailing list<br>
>> > >> > <a href="mailto:CentOS-devel@centos.org" target="_blank">CentOS-devel@centos.org</a><br>
>> > >> > <a href="https://lists.centos.org/mailman/listinfo/centos-devel" rel="noreferrer" target="_blank">https://lists.centos.org/mailman/listinfo/centos-devel</a><br>
>> > >> _______________________________________________<br>
>> > >> CentOS-devel mailing list<br>
>> > >> <a href="mailto:CentOS-devel@centos.org" target="_blank">CentOS-devel@centos.org</a><br>
>> > >> <a href="https://lists.centos.org/mailman/listinfo/centos-devel" rel="noreferrer" target="_blank">https://lists.centos.org/mailman/listinfo/centos-devel</a><br>
>> > >><br>
>> > > _______________________________________________<br>
>> > > CentOS-devel mailing list<br>
>> > > <a href="mailto:CentOS-devel@centos.org" target="_blank">CentOS-devel@centos.org</a><br>
>> > > <a href="https://lists.centos.org/mailman/listinfo/centos-devel" rel="noreferrer" target="_blank">https://lists.centos.org/mailman/listinfo/centos-devel</a><br>
>><br>
<br>
</blockquote></div></div>
</blockquote></div></div>