ceph
/
ceph-ansible
mirror of https://github.com/ceph/ceph-ansible.git
1
0
Fork 0
Code Issues Packages Projects Releases Wiki Activity
ceph-ansible/tests/functional/ubuntu/16.04/cluster/group_vars/all

27 lines
548 B
Plaintext
Raw Normal View History

tests: adds a scenario to test a xenial 1mon 1osd 1mds 1rgw cluster This scenario duplicates what we are currently doing with our ceph-ansible testing using OVH and a single node, except now we are using 4 separate nodes. Signed-off-by: Andrew Schoen <aschoen@redhat.com> Resolves: vagrant#boxes
2016-11-10 04:14:10 +08:00
---
common: refactor installation method The installation process is now described as follow: * you still have to choose a 'ceph_origin' installation method. The origin can be a 'repository' (add a new repository), distro (it will use the packages provided by the native repo source of your distribution), local (only available on redhat system, it installs locally built packages). This option is not well tested, so use it carefully * if ceph_origin == 'repository' you will have to decide what kind of repository you want to enable: - community: corresponds to the stable upstream/community version - enterprise: corresponds to the stable enterprise/downstream version (basically you are a red hat customer) - dev: it will install ceph from packages built out of the github development branches Signed-off-by: Sébastien Han <seb@redhat.com> Co-Authored-by: Guillaume Abrioux <gabrioux@redhat.com> Signed-off-by: Guillaume Abrioux <gabrioux@redhat.com>
2017-08-03 21:30:25 +08:00
ceph_origin: repository
ceph_repository: community
test: add cluster name support test scenario We need to test the cluster name support in this CI as well. This commit might be prone to debate because it tests 2 things in a single scenario. We first test our ability to deploy a cluster AND the cluster name support. However it's easier to do it this way and will reduce the amount of time for testingg. If we don't do this we will have a duplicate those 2 existing tests into new ones 'only' to test the cluster name support. Signed-off-by: Sébastien Han <seb@redhat.com>
2016-12-06 18:20:23 +08:00
cluster: test
testing: use the same sequence in the group_vars for every test scenario Signed-off-by: Alfredo Deza <adeza@redhat.com>
2016-11-19 00:47:38 +08:00
public_network: "192.168.5.0/24"
cluster_network: "192.168.6.0/24"
Tests: update tests according to ipv6 support Since ceph.conf.j2 has been updated to add ipv6 support, the different variables in many scenarios need to be updated. Signed-off-by: Guillaume Abrioux <gabrioux@redhat.com>
2017-06-21 20:14:35 +08:00
monitor_interface: eth1
Common: changed civetweb line in rgw section(conf) Resolves issue: Multiple RGW Ceph.conf Issue #1258 In multi-RGW setup, in ceph.conf the RGW sections contain identical bind IP in civetweb line. So this modification fixes that issue and puts the right IP for each RGW. Signed-off-by: SirishaGuduru SGuduru@walmartlabs.com Modified ceph-defaults and ran generate_group_vars_sample.sh group_vars/osds.yml.sample and group_vars/rhcs.yml.sample are not part of the changes. But they got modified when generate_group_vars_sample.sh is ran to generate group_vars/ all.yml.sample. Uncommented added variables in ceph-defaults Updated tests by adding value for radosgw_interface Added radosgw_interface to centos cluster tests Modified ceph-rgw role,rebased and ran generate_group_vars_sample.sh In ceph-rgw role removed check_mandatory_vars.yml. Rebased on master. Ran generate_group_vars_sample.sh and then the below files got modified.
2017-08-07 17:23:32 +08:00
radosgw_interface: eth1
tests: adds a scenario to test a xenial 1mon 1osd 1mds 1rgw cluster This scenario duplicates what we are currently doing with our ceph-ansible testing using OVH and a single node, except now we are using 4 separate nodes. Signed-off-by: Andrew Schoen <aschoen@redhat.com> Resolves: vagrant#boxes
2016-11-10 04:14:10 +08:00
journal_size: 100
devices:
- '/dev/sdb'
osd: simplify scenarios There is only two main scenarios now: * collocated: everything remains on the same device: - data, db, wal for bluestore - data and journal for filestore * non-collocated: dedicated device for some of the component Signed-off-by: Sébastien Han <seb@redhat.com>
2017-07-27 23:05:59 +08:00
dedicated_devices:
tests: adds a scenario to test a xenial 1mon 1osd 1mds 1rgw cluster This scenario duplicates what we are currently doing with our ceph-ansible testing using OVH and a single node, except now we are using 4 separate nodes. Signed-off-by: Andrew Schoen <aschoen@redhat.com> Resolves: vagrant#boxes
2016-11-10 04:14:10 +08:00
- '/dev/sdc'
osd: simplify scenarios There is only two main scenarios now: * collocated: everything remains on the same device: - data, db, wal for bluestore - data and journal for filestore * non-collocated: dedicated device for some of the component Signed-off-by: Sébastien Han <seb@redhat.com>
2017-07-27 23:05:59 +08:00
osd_scenario: non-collocated
tests: adds a scenario to test a xenial 1mon 1osd 1mds 1rgw cluster This scenario duplicates what we are currently doing with our ceph-ansible testing using OVH and a single node, except now we are using 4 separate nodes. Signed-off-by: Andrew Schoen <aschoen@redhat.com> Resolves: vagrant#boxes
2016-11-10 04:14:10 +08:00
os_tuning_params:
- { name: kernel.pid_max, value: 4194303 }
- { name: fs.file-max, value: 26234859 }
ci: set replica count to 1 since we have a single osd Signed-off-by: Sébastien Han <seb@redhat.com>
2017-01-31 22:29:35 +08:00
ceph_conf_overrides:
global:
osd_pool_default_pg_num: 8
osd_pool_default_size: 1
common: bump ceph version to kraken Kraken has been out for a couple of weeks now and the CI can test both Kraken and Jewel. Signed-off-by: Sébastien Han <seb@redhat.com>
2017-04-10 22:20:49 +08:00
debian_ceph_packages:
- ceph
- ceph-common
- ceph-fuse