I merged the SFC patch [0], but just realized I should have first resolved an SFC model issue with the new yangtools.
Im going to submit a patch now to fix the issue so that the SFC version bump patch will merge successfully. [0] https://git.opendaylight.org/gerrit/#/c/66513/ Regards, *Brady Johnson* [email protected] <https://twitter.com/inocybetech> <http://www.inocybe.com/> <https://www.linkedin.com/company/2661537?trk=tyah&trkInfo=clickedVertical%3Acompany%2CclickedEntityId%3A2661537%2Cidx%3A1-1-1%2CtarId%3A1441300264767%2Ctas%3Ainocybe> [image: Screenshot 2017-02-14 at 10.43.55 AM.png] <https://www.youtube.com/channel/UC9uUWABdPR0Je9Du_15FCkw> On Tue, Jan 16, 2018 at 1:51 PM, Jamo Luhrsen <[email protected]> wrote: > Sam built a local distro with the remaining unmerged patches > and I am trying some netvirt CSIT with that: > > https://jenkins.opendaylight.org/releng/user/jluhrsen/my- > views/view/netvirt%20csit/job/netvirt-csit-1node-openstack- > ocata-gate-stateful-oxygen/637 > > https://jenkins.opendaylight.org/releng/user/jluhrsen/my- > views/view/netvirt%20csit/job/netvirt-csit-1node-openstack- > ocata-gate-stateful-snat-conntrack-oxygen/38 > > > JamO > > > > On 01/16/2018 11:07 AM, Michael Vorburger wrote: > > On Tue, Jan 16, 2018 at 7:29 PM, Brady Johnson <[email protected] > <mailto:[email protected]>> wrote: > > > > We have indeed made good progress and it looks like we're close. > Should we at least give it until the end of the day today? > > > > Related to this, since the merges started I havent been able to > build SFC since Friday when I sent this email [0] and I > > still cant today. So this is something we need to resolve soon to > avoid schedule slips. > > > > [0] https://lists.opendaylight.org/pipermail/release/2018- > January/013337.html > > <https://lists.opendaylight.org/pipermail/release/2018- > January/013337.html> > > > > > > Regards, > > > > *Brady Johnson* > > [email protected] <mailto:[email protected]> > > > > <https://twitter.com/inocybetech><http://www.inocybe.com/>< > https://www.linkedin.com/company/2661537?trk=tyah&trkInfo= > clickedVertical%3Acompany%2CclickedEntityId%3A2661537% > 2Cidx%3A1-1-1%2CtarId%3A1441300264767%2Ctas%3Ainocybe>Screenshot > > 2017-02-14 at 10.43.55 AM.png <https://www.youtube.com/ > channel/UC9uUWABdPR0Je9Du_15FCkw> > > > > > > > > On Tue, Jan 16, 2018 at 8:31 AM, Stephen Kitt <[email protected] > <mailto:[email protected]>> wrote: > > > > Hi, > > > > In last week’s TSC call we agreed to move forward with merging > the > > odlparent 3 / yangtools 2 migration patches, with a timebox — we > were > > supposed to be able to run NetVirt CSIT yesterday. Obviously that > > deadline has gone whizzing past and we’re still some way away > from > > running NetVirt CSIT; I’m not sure how far away... Strictly > speaking, > > all the NetVirt dependencies now pass verify (thanks to lots of > work by > > Tom, Robert and Michael on Neutron in particular), so we could > give it > > a shot once the patches are merged, but I also knows that OVSDB > fails > > its IT so I expect NetVirt CSIT won’t pass. > > > > So the question now is what do we do. Following the agreed plan, > we > > should start reverting the patches (hopefully without messing up > the > > follow-up fixes). We could formulate alternative plans, but I’m > not > > sure what the community feels about that! > > > > Anyway, I’m not trying to suggest a concrete solution with this > email, > > I want to start the discussion. > > > > > > my personal view is that the sane thing to do would be to revert and > finish this up on a branch in parallel, to unblock > > folks, because the timeline proposed in https://lists.opendaylight. > org/pipermail/release/2018-January/013336.html was missed, > > and IMHO it's likely at least several more days until things fully > stabilize. Through all the various 3rd party upgrades and > > yangtools changes etc. that went into this big bump, as of right there > still has never been a full netvirt CSIT successfully > > run proving non-regression, yet; that's going to happen in the coming > days. > > > > But I believe this view is not widely shared... ;-) Part of the reasons > for that seem to include issues such as that the > > multipatch job apparently doesn't work, so it is hard to test change > accross projects easily. I'm not sure that "let's just > > merge and figure it out as we go along" is the best answer to that > problem.. but if others don't have a problem with the > > "broken world" for a number of days, then so be it! > > > > > > Regards, > > > > -- > > Stephen Kitt > > Principal Software Engineer, Office of the CTO > > Red Hat > > > > _______________________________________________ > > release mailing list > > [email protected] <mailto:release@lists. > opendaylight.org> > > https://lists.opendaylight.org/mailman/listinfo/release < > https://lists.opendaylight.org/mailman/listinfo/release> > > > > > > > > _______________________________________________ > > TSC mailing list > > [email protected] <mailto:[email protected]> > > https://lists.opendaylight.org/mailman/listinfo/tsc < > https://lists.opendaylight.org/mailman/listinfo/tsc> > > > > > > > > > > _______________________________________________ > > release mailing list > > [email protected] > > https://lists.opendaylight.org/mailman/listinfo/release > > >
_______________________________________________ Discuss mailing list [email protected] https://lists.opendaylight.org/mailman/listinfo/discuss
