rgw: increase the number of OSDs for erasure coded pools

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/9298 Fixes: #9298

Signed-off-by: Loic Dachary <loic-201408@dachary.org>
dumpling-giant-x: use giant version of workunits

The firefly version of test_librbd_python at least does
not work on giant.

Signed-off-by: Josh Durgin <josh.durgin@inktank.com>
Update giant.yaml
Create dumpling-giant-x stress-split upgrade suite

Fixes: 9357
Signed-off-by: Warren Usui <warren.usui@inktank.com>
Merge pull request #122 from ceph/wip-9357-wusui

Create dumpling-giant-x stress-split upgrade suite
Merge pull request #116 from dachary/wip-9298-rgw-ec-starvation

rgw: increase the number of OSDs for erasure coded pools
tasks: add watch_notify_same_primary

Reproduces: #9220
Signed-off-by: Samuel Just <sam.just@inktank.com>
Merge pull request #130 from ceph/wip-9220

tasks: add watch_notify_same_primary

Reviewed-by: Sage Weil <sage@redhat.com>
Use same upgrade-test as firefly.
The changes for firefly upgrade tests apply to giant as well.
Merge pull request #131 from ceph/wip-9357-wusui

Use same upgrade-test as firefly.
Revert "Use same upgrade-test as firefly."
Merge pull request #132 from ceph/revert-131-wip-9357-wusui

Revert "Use same upgrade-test as firefly."
Added RHEL7 to matrix.

Signed-off-by: Sandon Van Ness <sandon@inktank.com>
tasks: generalize config writing for Filesystem

Signed-off-by: John Spray <john.spray@redhat.com>
tasks: generalise CephFSTestCase

Some of this stuff could be even more general for embedding
unittest-style suites, but for the moment let's keep the cephfs
stuff in a walled garden.

Signed-off-by: John Spray <john.spray@redhat.com>
tasks: add mds_client_limits

New CephFS tests for the behaviour of the system while
enforcing its resource limits.

Signed-off-by: John Spray <john.spray@redhat.com>
tasks: typo in mds_client_recovery

Signed-off-by: John Spray <john.spray@redhat.com>
tasks: rename FuseMount.get_client_id to get_global_id

'client_id' was ambiguous because in other places it
meant the '0' in client.0, whereas here it means
the runtime-generated global ID of the client.

Signed-off-by: John Spray <john.spray@redhat.com>
tasks: wait for mds active before mounting clients

To make the logs clearer when trying to work out
if/when something went wrong, rather than always
having client logs start with some failures.

Signed-off-by: John Spray <john.spray@redhat.com>
suites: enable mds_client_limits test

Requires same cluster etc as 'recovery', though
we could now do with better name than that.

Signed-off-by: John Spray <john.spray@redhat.com>