Ceph

description¶

The "upgrade/jewel-x" suite in the jewel branch should use a specific version of jewel as base. Currently, only "upgrade/jewel-x/point-to-point-x" does this (it uses v10.2.0 as base).

This ticket is to update the other tests in the jewel version of upgrade/jewel-x so they install the latest released version of jewel (currently v10.2.5) as base, and then upgrade from there.

This is a little clumsy because it means we will have to manually update the tests for every point release, before starting integration testing.

(11:04:28 AM) smithfarm: loicd: we agreed that, in jewel integration testing with "--ceph wip-jewel-backports", the only test that makes sense is point-to-point-x, correct?
(11:04:55 AM) loicd: yes
(11:04:56 AM) smithfarm: but we could add "tag: v10.2.5" to the other tests and then they would make sense too
(11:05:06 AM) smithfarm: additionally, we could run with "--ceph v11.2.0" 
(11:05:28 AM) smithfarm: which would cover upgrade from latest jewel to kraken, but would not cover upgrade from wip-jewel-backports to kraken
(11:05:30 AM) loicd: I was suggesting adding a run of --suite-branch jewel --ceph v11.2.0 to test the latest jewel before it is released ?
(11:06:26 AM) loicd: if we add a tag: v10.2.5 we can't do that, can we ?
(11:06:44 AM) smithfarm: loicd: would need to be "--suite-branch kraken --ceph v11.2.0" 
(11:06:48 AM) smithfarm: if we added v10.2.5
(11:07:31 AM) loicd: that would work too
(11:08:50 AM) loicd: ok

We'll just run upgrade/jewel-x/point-to-point on jewel for integration testing and QE will run the full upgrade/jewel-x (against kraken)