On Wed, May 3, 2017 at 11:30 AM, Alan Pevec <apevec(a)redhat.com&gt; wrote: > > On May 3, 2017 05:54, "Numan Siddique" <nusiddiq(a)redhat.com&gt; wrote: > > Hello Everyone, > > I wanted to know what is the plan for moving OpenvSwitch packages to > version 2.7. > > In order to deploy OVN in tripleo, we need OVS 2.7 > - for deploying all the ovn services successfully > - for having the floating ip/gateway functionality to work > > > Is it possible to consider moving to OVS 2.7 sooner ? > > > Ideally, OVS for all CentOS SIGs would be maintained within NFV SIG and > other SIGs would reuse it. For 2.6 I rebuilt it first from Fedora then > snapshots which included critical fixes. Now I see VirtSIG has built 2.7 on > their own but not sure what is the source: > http://cbs.centos.org/koji/buildinfo?buildID=16698 > > Can you test this build and report back if it is good to cross-tag it for > RDO Pike? > Thanks. Sure, I will test and report back.

> > Cheers, > Alan >

On Mon, May 15, 2017 at 10:33 AM, Numan Siddique <nusiddiq(a)redhat.com&gt; wrote: > I tested by deploying upstream tripleo on my local setup by making use of > these rpms and it works fine for me. Did you also try upgrade tests? That was the pain-point with the previous OVS updates.

> Is it possible to cross-tag for RDO pike ? I've tagged openvswitch-2.7.0-1.el7 for pike-candidate for now so we can ran full RDO CI on it. Alfredo, David, Emilien, can you please run pipeline jobs with http://cbs.centos.org/repos/cloud7-openstack-pike-candidate/x86_64/os/ repo added ? Alternatively, it is also tagged for http://cbs.centos.org/repos/cloud7-openstack-common-pending/x86_64/os/ but there we have more other updates under testing so result might be polluted. Cheers, Alan

On Tue, May 16, 2017 at 12:35 PM, Numan Siddique <nusiddiq(a)redhat.com&gt; wrote: > > > On Tue, May 16, 2017 at 2:31 AM, Alan Pevec <apevec(a)redhat.com&gt; wrote: > >> On Mon, May 15, 2017 at 10:33 AM, Numan Siddique <nusiddiq(a)redhat.com&gt; >> wrote: >> > I tested by deploying upstream tripleo on my local setup by making use >> of >> > these rpms and it works fine for me. >> >> Did you also try upgrade tests? That was the pain-point with the >> previous OVS updates. >> >> > No. I didn't try that. > > Hi Alan, On my local setup, I have a master of tripleo overcloud deployed. I will do a stack update (with the OVS 2.7 version) and come back with the results. Is this what you are expecting ? Or you are expecting an upgrade from Newton to Ocata or Ocata to Pike (or master) ? In the last conversation we had, you mentioned about setting up a CI job to test the OVS uprade ? Do you have any idea about it ? Is some one looking into it ? I can look into it if some one can point me to the right direction what needs to be done. (My apologies, I am not completely aware of the CI jobs run).

Thanks Numan > >> > Is it possible to cross-tag for RDO pike ? >> >> I've tagged openvswitch-2.7.0-1.el7 for pike-candidate for now so we >> can ran full RDO CI on it. >> >> Alfredo, David, Emilien, can you please run pipeline jobs with >> http://cbs.centos.org/repos/cloud7-openstack-pike-candidate/x86_64/os/ >> repo added ? >> Alternatively, it is also tagged for >> http://cbs.centos.org/repos/cloud7-openstack-common-pending/x86_64/os/ >> but there we have more other updates under testing so result might be >> polluted. >> >> Cheers, >> Alan >> > >

Hi Numan, thanks for testing! Few questions inline: >>>> > I tested by deploying upstream tripleo on my local setup by making use of these rpms and it works fine for me. >>>> Did you also try upgrade tests? That was the pain-point with the previous OVS updates. >>> No. I didn't try that. > I did some testing locally and these are my findings > - After deploying a overcloud (with 3 controllers and 1 compute ) using > tripleo-quickstart, I added the OVS 2.7 repo from here [1] manually on all Was [1] http://cbs.centos.org/repos/cloud7-openstack-pike- candidate/x86_64/os/ ?

Can you confirm which openvswitch NVR you got?

> the nodes and triggered "openstack overcloud update stack". > - For some reason update was always failing. Not sure what is going wrong > - So I manually ran "yum update" on the nodes > - OVS 2.7 was updated successfully, but the service was not restarted. Numan, please report update stack failure as tripleo upstream LP bug. Adding Sofer from the upgrades team: is there upstream tripleo update/upgrade CI job which is testing with OVS 2.7 ?

From the logs I could see that ovs was never updated (not sure why) and the

> - After the update everything was working fine. Working fine without ovs service restart?

> - Then I restarted all the nodes to have OVS 2.7 started up. > - After restart I was able to have my tenant networks working fine. So that sounds promising but I'd like to get details on update stack failure before we proceed promotion OVS 2.7 packages to the RDO Pike repo. Also note that 2.7.0-1 RPM from v2.7.0 tag is missing > 100 backports on branch-2.7, upstream should really consider releasing 2.7.1.

Cheers, Alan > Thanks > Numan >>>> > Is it possible to cross-tag for RDO pike ? >>>> I've tagged openvswitch-2.7.0-1.el7 for pike-candidate for now so we >>>> can ran full RDO CI on it. >>>> Alfredo, David, Emilien, can you please run pipeline jobs with >>>> http://cbs.centos.org/repos/cloud7-openstack-pike- candidate/x86_64/os/ >>>> repo added ?

On Tue, Jun 13, 2017 at 4:39 PM, Numan Siddique <nusiddiq(a)redhat.com&gt; wrote: > > > On Tue, Jun 13, 2017 at 4:18 PM, Alan Pevec <apevec(a)redhat.com&gt; wrote: > >> Hi Numan, >> >> thanks for testing! Few questions inline: >> >> >>>> > I tested by deploying upstream tripleo on my local setup by >> making use of these rpms and it works fine for me. >> >>>> Did you also try upgrade tests? That was the pain-point with the >> previous OVS updates. >> >>> No. I didn't try that. >> > I did some testing locally and these are my findings >> > - After deploying a overcloud (with 3 controllers and 1 compute ) >> using >> > tripleo-quickstart, I added the OVS 2.7 repo from here [1] manually on >> all >> >> Was [1] http://cbs.centos.org/repos/cloud7-openstack-pike-candidate/ >> x86_64/os/ ? >> > > No. It was http://cbs.centos.org/repos/cloud7-openstack-common-candidat > e/x86_64/os/ > > > >> Can you confirm which openvswitch NVR you got? >> > > I am not sure which one. I will get back to you on this. > > >> > the nodes and triggered "openstack overcloud update stack". >> > - For some reason update was always failing. Not sure what is going >> wrong >> > - So I manually ran "yum update" on the nodes >> > - OVS 2.7 was updated successfully, but the service was not >> restarted. >> >> Numan, please report update stack failure as tripleo upstream LP bug. >> Adding Sofer from the upgrades team: is there upstream tripleo >> update/upgrade CI job which is testing with OVS 2.7 ? >> > > I want to test once more before I submit a bug to be really sure if I > haven't done any mistake. > Hi Alan, I ran the stack update again, but now with 1 controller and 1 compute node and the stack update was successful. I have captured the terminal logs which you can find here - https://paste.fedoraproject.org/paste/FELBFKHNWiIwgNsd3o22~A Before starting the update, I created a VM with ip 10.0.0.9. I started a ping command in the controller node from the neutron dhcp namespace. The ping was running successfully without any issues. As expected, the OVS packages were updated to 2.7 and openvswitch service was not restarted. So essentially OVS 2.6 was running even after the update. Then I manually restarted openvswitch service first on the compute node and then on controller node. The ping was only interrupted during the service restarts and was back again. Below is the repo file I added to get the OVS 2.7 ****************************************************** cat /etc/yum.repos.d/cbs.centos.org_repos_cloud7-openstack- pike-candidate_x86_64_os.repo [cbs.centos.org_repos_cloud7-openstack-pike-candidate_x86_64_os] name=added from: http://cbs.centos.org/repos/cloud7-openstack-pike- candidate/x86_64/os baseurl=http://cbs.centos.org/repos/cloud7-openstack-pike- candidate/x86_64/os enabled=1 gpgcheck=0 includepkgs=openvswitch,openvswitch-ovn* *********************************************************

Numan > I don't think there is any CI job yet. I tried to be bold and submitted a > patch to test it here (please note it's only for testing) - > https://review.openstack.org/#/c/473191/ > > In the puppet/services/openvswitch_upgrade.yaml, I tried to install the > OVS 2.7 and restart it. > From the logs I could see that ovs was never updated (not sure why) and > the ansible task to restart the openvswitch (still with version 2.6) makes > the node loose the network completely. I will explore more on this job and > see how it goes. > > But from what I understand upgrading OVS (presently) has a down time > overhead. i.e We can update the ovs package. But restarting OVS with the > updated version would cause some down time or reboot. I may be wrong here. > But that's what I understand. If this is the case, not sure if we can test > this scenario in CI other than just updating the package without restart. > > > >> > - After the update everything was working fine. >> >> Working fine without ovs service restart? >> > > That's right. > > >> >> > - Then I restarted all the nodes to have OVS 2.7 started up. >> > - After restart I was able to have my tenant networks working fine. >> >> So that sounds promising but I'd like to get details on update stack >> failure before we proceed promotion OVS 2.7 packages to the RDO Pike >> repo. >> Also note that 2.7.0-1 RPM from v2.7.0 tag is missing > 100 backports >> on branch-2.7, upstream should really consider releasing 2.7.1. >> >> > I have requested for a new tag in the OVS mailing list. Hope it would be > done soon. > > Thanks > Numan > > >> Cheers, >> Alan >> >> > Thanks >> > Numan >> >> >>>> > Is it possible to cross-tag for RDO pike ? >> >>>> I've tagged openvswitch-2.7.0-1.el7 for pike-candidate for now so we >> >>>> can ran full RDO CI on it. >> >>>> Alfredo, David, Emilien, can you please run pipeline jobs with >> >>>> http://cbs.centos.org/repos/cloud7-openstack-pike-candidate/ >> x86_64/os/ >> >>>> repo added ? >> > >

Just an update. The test review [1] is passing for the CI job - gate-tripleo-ci-centos-7-multinode-upgrades-nv. This patch updates the OVS to OVS 2.7 from the repo - http://cbs.centos.org/repos/cloud7-openstack-pike-candidate/x86_64/os and restarts it at step0 of the upgrade.

[1] - https://review.openstack.org/#/c/473191/ http://logs.openstack.org/91/473191/9/check/gate-tripleo-

http://logs.openstack.org/91/473191/9/check/gate-tripleo-

On Fri, Jun 16, 2017 at 12:00 PM, Numan Siddique <nusiddiq(a)redhat.com&gt; wrote: > > > On Jun 16, 2017 11:41 AM, "Alan Pevec" <apevec(a)redhat.com&gt; wrote: > > On Fri, Jun 16, 2017 at 3:03 AM, Numan Siddique <nusiddiq(a)redhat.com&gt; > wrote: > > Just an update. The test review [1] is passing for the CI job - > > gate-tripleo-ci-centos-7-multinode-upgrades-nv. > > This patch updates the OVS to OVS 2.7 from the repo - > > http://cbs.centos.org/repos/cloud7-openstack-pike-candidate/x86_64/os > and > > restarts it at step0 of the upgrade. > > Thanks, double-checking, ovs in overcloud is 2.7: > http://logs.openstack.org/91/473191/9/check/gate-tripleo-ci- > centos-7-multinode-upgrades-nv/3307cf8/logs/subnode-2/rpm-qa.txt.gz > > In undercloud 2.6.1 is still installed but I'll assume testing in OC > is good enough. > I'm moving 2.7 to pike-testing, please watch for any issues in RDO and > TripleO CI on master/Pike and report here. > Hopefully we'll get 2.7.1 upstream release soon so we can update the > package. > > > Thanks Alan. Sure I will watch out for any CI issues. > ovs 2.7.1 would be released soon. I will update you once it's available. > Hi Alan, OVS 2.7.1 is available now. I am working on having a CI job for tripleo to enable OVN. I submitted this patch [1] for that. But it is failing in upgrade job from ML2OVS to OVN. So Emilien suggested to enable OVN first in ocata job [2] and after that in master, so that upgrade from Ocata to master would be successful since we would be using OVN here. This patch [2] is failing because ocata repos have OVS 2.6. Is it possible to have OVS 2.7 in ocata testing repo ? [1] - https://review.openstack.org/#/c/412831/ [2] - https://review.openstack.org/#/c/480355/ Thanks Numan > Thanks again > Numan > > > Cheers, > Alan > > > [1] - https://review.openstack.org/#/c/473191/ > > > > http://logs.openstack.org/91/473191/9/check/gate-tripleo-ci- > centos-7-multinode-upgrades-nv/3307cf8/logs/subnode-2/var/lo > g/ovs_debug.txt.gz > > > > http://logs.openstack.org/91/473191/9/check/gate-tripleo-ci- > centos-7-multinode-upgrades-nv/3307cf8/logs/subnode-2/var/lo > g/openvswitch/ovsdb-server.txt.gz > > >