=======
This suite tests upgrades of a ceph cluster from dumpling (current
-branch) to firefly (current branch), and then to a later specified
+branch) to giant (current branch), and then to a later specified
version (version x, e.g. for example ‘next’ or ‘master’). It runs the
-last upgrade (steps in 3-firefly-upgrade) in parallel with firefly
+last upgrade (steps in 3-giant-upgrade) in parallel with firefly
client tests.
Generally the flow is:
- install dumpling
- test it
-- upgrade cluster and clients to firefly
-- test firefly while upgrading cluster to version x
+- upgrade cluster and clients to giant
+- test giant while upgrading cluster to version x
- upgrade clients
- test with version x clients
Defines the 'workload' section - correctness tests to run on dumpling
“+” is used to construct a single yaml load from all tests in this directory
-3-firefly-upgrade
+3-giant-upgrade
-----------------
-First upgrades everything to firefly. Then upgrades the cluster to
+First upgrades everything to giant. Then upgrades the cluster to
version x while running correctness tests (from the 'workload2'
-section) on firefly clients in parallel. This upgrade is done by the
+section) on giant clients in parallel. This upgrade is done by the
'upgrade-sequence' section, defined later. Once the cluster is
upgraded and these tests complete, upgrades the clients to version x
as well.
Clients are upgraded last to avoid running newer tests that don't work
-against firefly, and to verify that firefly clients can continue
+against giant, and to verify that giant clients can continue
working with a newer cluster.
4-workload
----------
Defines the 'workload2' section - correctness tests to run during the
-upgrade from firefly to version x.
+upgrade from giant to version x.
“+” is used to construct a single yaml load from all tests in this directory
5-upgrade-sequence
------------------
Defines the 'upgrade-sequence' section - the order in which the
-upgrade from firefly to version x is done. Note that leaving the
+upgrade from giant to version x is done. Note that leaving the
version unspecified here is what makes it upgrade to version x,
which is set as an override when this suite is scheduled.