On Wed, Aug 12, 2020 at 5:31 PM Gregory Farnum <gfarnum@xxxxxxxxxx> wrote: > > On Wed, Aug 12, 2020 at 7:34 AM Neha Ojha <nojha@xxxxxxxxxx> wrote: > > > > Hi everyone, > > > > We have merged [1] and [2] with the aim to help developers run upgrade > > tests on teuthology easily. One can now schedule an upgrade suite run > > in teuthology just like any other suite, by just passing "-s upgrade". > > This was not possible earlier due to the dependency of client-upgrades > > on versions other than the one the suite was being run from. Now > > upgrade-clients is a suite of its own, independent of other upgrades. > > Moving forward, upgrades suites in master/Pacific and beyond will also > > follow the same structure. > > Which client upgrade pieces have been pulled out now? This sounds like > we've lost the check that old clients can continue talking to new > servers in the normal upgrade suite? We are NOT losing any test coverage for client upgrades, they've just been moved to a suite of their own(See https://github.com/ceph/ceph/tree/octopus/qa/suites/upgrade-clients/client-upgrade-octopus-pacific). The PRs linked in my earlier email explain this. Neha > > > > > Let's try to make sure we care about backward compatibility and run > > upgrade tests wherever required. > > > > Thanks, > > Neha > > > > [1] https://github.com/ceph/ceph/pull/36435 - nautilus > > [2] https://github.com/ceph/ceph/pull/36436 - octopus > > _______________________________________________ > > Dev mailing list -- dev@xxxxxxx > > To unsubscribe send an email to dev-leave@xxxxxxx > > > _______________________________________________ Dev mailing list -- dev@xxxxxxx To unsubscribe send an email to dev-leave@xxxxxxx
