So that there never is less than 4 osd which is the minimum when trying
erasure coded workloads that only work with 4 osd.
http://tracker.ceph.com/issues/9298Fixes: #9298
Signed-off-by: Loic Dachary <loic-201408@dachary.org>
And replace the ec-readwrite.yaml custom workloads with links to the
workloads found in the erasure-code directory.
Signed-off-by: Loic Dachary <loic-201408@dachary.org>
The erasure-code directory is populated with files describing rados
workloads suitable to test the default erasure code plugins. They are
linked to the rados suite. The pre-existing rados workloads from the
rados suite are replaced with those. Two workloads only differed by the
fact that one of them had less operations than the other. The more
complete set of operations is kept and used for all workloads to
maximize coverage.
Signed-off-by: Loic Dachary <loic-201408@dachary.org>
Sage found:
"... supposed to have half dumpling, half x osds. but the steps that upgrade and restart the mons upgrade the packages on the second host (which should remain dumpling w/ osd 3,4,5)"
Signed-off-by: Yuri Weinstein <yuri.weinstein@inktank.com>
"... supposed to have half dumpling, half x osds. but the steps that upgrade and restart the mons upgrade the packages on the second host (which should remain dumpling w/ osd 3,4,5)"
Signed-off-by: Yuri Weinstein <yuri.weinstein@inktank.com>
Because rgw.py iterates over it to run the rgw server. If it is removed
the rgw servers are not run and all fails.
Signed-off-by: Loic Dachary <loic@dachary.org>
Globally overriding the rgw idle_timeout is not possible because it it
needs to be done on a per client.0, client.1, etc. basis. Add the
default_idle_timeout key to the rgw config : it defaults to the
previously hardcoded default (30) and can be changed via the override.
The existing tasks that were previously overriding the idle_timeout on a
per client basis are changed to use the default_idle_timeout instead for
consistency and to allow a global override.
Signed-off-by: Loic Dachary <loic@dachary.org>
A place for any tests which should be run with
standbyreplay MDSs in play. Initially just
the mds_journal_migration task, to cover
the #8811 case.
Signed-off-by: John Spray <john.spray@redhat.com>
Hopefully this makes it easier to digest and maintain
than reading yaml fragments.
Signed-off-by: Josh Durgin <josh.durgin@inktank.com>
Signed-off-by: Yuri Weintstein <yuri.weinstein@inktank.com>
This has been timing out for weeks to months (hard to say since before that
we were consistently hitting an OSD crash on shutdown). The runs I've looked
at are making progress and seem fine ... just slow because of valgrind and
because of thrashing.
Backport: firefly
Signed-off-by: Sage Weil <sage@redhat.com>
Follow up to a24efaef, remove the mds from
the (mainly singleton) test configs that
explicitly list it.
Signed-off-by: John Spray <john.spray@redhat.com>
