Yea, Sage, that sounds reasonable. I added a ticket to capture this plan (http://tracker.ceph.com/issues/11413) and will add those tests soon. Please add your comments to the ticket above. I am assuming that it will look something like this for dumpling, firefly and hammer: dumpling(stable) -> client-x firefly(stable) -> client-x hammer(stable) -> client-x and reverse dumpling-client(stable) -> cluster-x firefly-cluster(stable) -> cluster-x hammer-cluster(stable) -> cluster-x Yes? Thx YuriW ----- Original Message ----- From: "Sage Weil" <sweil@xxxxxxxxxx> To: ceph-devel@xxxxxxxxxxxxxxx Sent: Thursday, April 16, 2015 9:42:29 AM Subject: client/cluster compatibility testing Now that there are several different vendors shipping and supporting Ceph in their products, we'll invariably have people running different versions of Ceph that are interested in interoperability. If we focus just on client <-> cluster compatability, I think the issues are (1) compatibility between upstream ceph versions (firefly vs hammer) and (2) ensuring that any downstream changes the vendor makes don't break that compatibility. I think the simplest way to address this is to talk about compatibility in terms of the upstream stable releases (firefly, hammer, etc.), and test that compatibility with teuthology tests from ceph-qa-suite.git. We have some basic inter-version client/cluster tests already in suites/upgrade/client-upgrade. Currently these test new (version "x") clients against a given release (dumpling, firefly). I think we just need to add hammer to that mix, and then add a second set of tests that do the reverse: test clients from a given release (dumpling, firefly, hammer) against an arbitrary cluster version ("x"). We'll obviously run these tests on upstream releases to ensure that we are not breaking compatibility (or are doing so in known, explicit ways). Downstream folks can run the same test suites against any changes they make as well to ensure that their product is "compatible with firefly clients," or whatever. Does that sound reasonable? sage -- To unsubscribe from this list: send the line "unsubscribe ceph-devel" in the body of a message to majordomo@xxxxxxxxxxxxxxx More majordomo info at http://vger.kernel.org/majordomo-info.html -- To unsubscribe from this list: send the line "unsubscribe ceph-devel" in the body of a message to majordomo@xxxxxxxxxxxxxxx More majordomo info at http://vger.kernel.org/majordomo-info.html
