On Mon, Nov 16, 2020 at 3:31 PM Alfredo Moralejo Alonso <amoralej at redhat.com> wrote: > > > On Mon, Nov 16, 2020 at 3:28 PM Satish Patel <satish.txt at gmail.com> wrote: > >> Alfredo, >> >> Last followup question, Once victora release comes out in future in >> that case does openstackvswitch2.13 will be default part of >> rdo-victoria packages right? OR do i need to install >> centos-release-nfv-openvswitch extra repo to get that package to >> install? >> >> > 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. > > [1] https://trunk.rdoproject.org/centos8-victoria/delorean-deps.repo > BTW, victoria is ready to be used https://lists.centos.org/pipermail/centos-devel/2020-November/056179.html > > >> ~S >> >> On Tue, Nov 10, 2020 at 4:41 AM Alfredo Moralejo Alonso >> <amoralej at redhat.com> wrote: >> > >> > >> > >> > On Mon, Nov 9, 2020 at 4:42 PM Satish Patel <satish.txt at gmail.com> >> wrote: >> >> >> >> Just to follow up, >> >> >> >> I have successfully deployed ovs+dpdk on centOS-8 on ussuri using the >> >> following repo. (openvswitch2.13) >> >> >> >> dnf install -y centos-release-nfv-openvswitch >> >> >> >> Just curious why RPM package name is openvswitch2.13 instead of >> >> openvswitch-2-13 (Let me guess because of centOS RDO provides that >> >> same naming style right?) >> > >> > >> > 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. >> > >> > [1] >> ftp://ftp.redhat.com/pub/redhat/linux/enterprise/8Base/en/Fast-Datapath/SRPMS/ >> > >> >> >> >> On Wed, Nov 4, 2020 at 9:34 AM Satish Patel <satish.txt at gmail.com> >> wrote: >> >> > >> >> > That is great news, it's coming back in victoria. Thanks for the >> update. >> >> > >> >> > For fun this is what i did, I downloaded openvswitch-2.12.x.x.x.srpm >> >> > and re-compile RPM with --with-dpdk support against dpdk-18.11 and i >> >> > was successfully able to produce RPM. >> >> > >> >> > I have installed RPM on my computer node and it looks good so far, i >> >> > am successfully able to add my nic to OVS using DPDK interface. I >> have >> >> > noticed CPU usage of ovs-vswitchd showing 100% but it looks like that >> >> > is expected behavior. >> >> > >> >> > [root at compute-2 ~]# ovs-vswitchd --version >> >> > ovs-vswitchd (Open vSwitch) 2.12.0 >> >> > DPDK 18.11.2 >> >> > >> >> > >> >> > [root at compute-2 ~]# ovs-vsctl show >> >> > Bridge br-provider >> >> > Controller "tcp:127.0.0.1:6633" >> >> > is_connected: true >> >> > fail_mode: secure >> >> > datapath_type: netdev >> >> > Port phy-br-provider >> >> > Interface phy-br-provider >> >> > type: patch >> >> > options: {peer=int-br-provider} >> >> > Port br-provider >> >> > Interface br-provider >> >> > type: internal >> >> > Port "dpdk-0" >> >> > Interface "dpdk-0" >> >> > type: dpdk >> >> > options: {dpdk-devargs="0000:06:00.0"} >> >> > ovs_version: "2.12.0" >> >> > >> >> > >> >> > I didn't see any issue so very curious when you said openvswitch-2.12 >> >> > is broken. I would like to know more if i am doing wrong. >> >> > >> >> > I am running a fairly large openstack cloud using LinuxBridge/SR-IOV >> >> > and am very happy with simplicity. First time I am trying to deploy >> >> > OpenvSwitch in the lab to see how everything looks, a little nervous >> >> > because I heard lots of nightmare stories from various folks, but it >> >> > looks like the future is OVS. >> >> > >> >> > I will try NFV repo and see how it goes :) >> >> > >> >> > On Wed, Nov 4, 2020 at 4:59 AM Alfredo Moralejo Alonso >> >> > <amoralej at redhat.com> wrote: >> >> > > >> >> > > >> >> > > >> >> > > On Tue, Nov 3, 2020 at 6:04 PM Satish Patel <satish.txt at gmail.com> >> wrote: >> >> > >> >> >> > >> Thanks for reply, >> >> > >> >> >> > >> I am using Openstack-Ansible deployment tool to run Openstack. I >> am >> >> > >> running a stable/ussuri release at the moment. current OVS package >> >> > >> coming from rdo-dep repository of Ussuri release. It would be >> great if >> >> > >> we have openvswitch+DPDK supported RPM for that repo, otherwise i >> am >> >> > >> stuck here and i have to re-compile RPM myself and need to pushout >> >> > >> with a custom repo. (Does victoria going to support the DPDK >> version >> >> > >> of openvswitch?) >> >> > > >> >> > > >> >> > > yes, Victoria has openvsiwtch 2.13 with dpdk enabled. >> >> > > >> >> > > if you can move to victoria, it would be the easiest way and my >> recommendation. >> >> > > >> >> > >> >> >> > >> >> >> > >> [root at compute-1 SPECS]# ovs-vswitchd --version >> >> > >> ovs-vswitchd (Open vSwitch) 2.12.0 >> >> > >> [root at compute-1 SPECS]# >> >> > >> >> >> > >> [root at compute-1 SPECS]# repoquery -i openvswitch >> >> > >> Last metadata expiration check: 2:57:01 ago on Tue 03 Nov 2020 >> 06:02:46 AM PST. >> >> > >> Name : openvswitch >> >> > >> Version : 2.12.0 >> >> > >> Release : 1.1.el8 >> >> > >> Architecture : aarch64 >> >> > >> Size : 1.9 M >> >> > >> Source : openvswitch-2.12.0-1.1.el8.src.rpm >> >> > >> Repository : rdo-deps >> >> > >> >> >> > >> [root at compute-1 SPECS]# cat /etc/yum.repos.d/rdo-deps.repo >> >> > >> [rdo-deps] >> >> > >> module_hotfixes=1 >> >> > >> baseurl = >> https://trunk.rdoproject.org/centos8-ussuri/deps/latest/ >> >> > >> >> >> > > >> >> > > AFAIK, Ussuri should work also with 2.13 but you need to do some >> steps: >> >> > > >> >> > > 1. Add NFV SIG repository: >> >> > > >> >> > > dnf install -y centos-release-nfv-openvswitch >> >> > > >> >> > > 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 >> https://cbs.centos.org/koji/buildinfo?buildID=31051 (you need all RPMs >> in noarch list), create a local repository with them and add it to all >> nodes in the cluster. >> >> > > >> >> > > 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. >> >> > > >> >> > >> On Tue, Nov 3, 2020 at 10:47 AM Alfredo Moralejo Alonso >> >> > >> <amoralej at redhat.com> wrote: >> >> > >> > >> >> > >> > Hi, >> >> > >> > >> >> > >> > On Tue, Nov 3, 2020 at 3:48 PM Satish Patel < >> satish.txt at gmail.com> wrote: >> >> > >> >> >> >> > >> >> Folks, >> >> > >> >> >> >> > >> >> Recently i started playing with openvswitch on centOS for >> openstack >> >> > >> >> SDN, and found centos8 doesn't have openvswitch with dpdk >> support, I >> >> > >> >> was looking around RPM but didn't find any RPM also, do i need >> to >> >> > >> >> compile openviswtch+dpdk support or rpm is available but i am >> not >> >> > >> >> aware of it. >> >> > >> >> >> >> > >> > >> >> > >> > 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. >> >> > >> > >> >> > >> > 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. >> >> > >> > >> >> > >> > RDO Victoria will be announced very soon (we are in the process >> of pushing latest required builds to CentOS official mirrors today). >> >> > >> > >> >> > >> > 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. >> >> > >> > >> >> > >> > Regards, >> >> > >> > >> >> > >> > Alfredo >> >> > >> > >> >> > >> >> ~S >> >> > >> >> _______________________________________________ >> >> > >> >> CentOS-devel mailing list >> >> > >> >> CentOS-devel at centos.org >> >> > >> >> https://lists.centos.org/mailman/listinfo/centos-devel >> >> > >> >> >> >> > >> > _______________________________________________ >> >> > >> > CentOS-devel mailing list >> >> > >> > CentOS-devel at centos.org >> >> > >> > https://lists.centos.org/mailman/listinfo/centos-devel >> >> > >> _______________________________________________ >> >> > >> CentOS-devel mailing list >> >> > >> CentOS-devel at centos.org >> >> > >> https://lists.centos.org/mailman/listinfo/centos-devel >> >> > >> >> >> > > _______________________________________________ >> >> > > CentOS-devel mailing list >> >> > > CentOS-devel at centos.org >> >> > > https://lists.centos.org/mailman/listinfo/centos-devel >> >> >> >> -------------- next part -------------- An HTML attachment was scrubbed... URL: <http://lists.centos.org/pipermail/centos-devel/attachments/20201116/d8882341/attachment-0006.html>