Feature #10240
Updated by Yuri Weinstein over 9 years ago
<pre> currently, upgrade suites have been optimized to run upgrades in parallel to a pile of mixed workloads[rados/rbd/rgw] thereby in most cases, upgrade gets over before some of the workloads actually run. so it appears like most workloads run post upgrade which is not much useful. there are 2 things we can do to expand the test coverage for upgrades here, 1. run multiple combinations of mixed workloads when upgrade is running in parallel and also cover different upgrade sequences. 2. run a few workloads in parallel by itself, while upgrade is happening.also, for different upgrade sequences. currently, the upgrade suite structure looks like, ceph-qa-suite/suites/upgrade/<release>/parallel/workload/[+,rbd,rados,rgw] for option 1, we need something like ceph-qa-suite/suites/upgrade/<release>/parallel/workload/test1/[+ , rbd, rados, rgw] ceph-qa-suite/suites/upgrade/<release>/parallel/workload/test2/[+, rbd,rados,rgw] where test1, test2 have different workloads for rados/rbd/rgw. for option2: ceph-qa-suite/suites/upgrade/<release>/parallel/workload/[+, rbd, rados, rgw] where all the rbd,rados, rgw tasks run in parallel with upgrades. </pre>