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/tox.ini

383 lines
21 KiB
INI
Raw Normal View History

tests: adds a tox.ini to run the functional tests This currently tests the initial-members scenario for both ansible 2.1 and ansible 2.2. It assumes a hosts file and vagrant_ssh_config exists in the scenario directory. Signed-off-by: Andrew Schoen <aschoen@redhat.com> Resolves: pytest#harness
2016-11-05 01:25:06 +08:00
[tox]
tests: add purge_lvm_osds_container scenario This commits adds the purge_lvm_osds_container scenario. Signed-off-by: Guillaume Abrioux <gabrioux@redhat.com>
2018-11-30 18:25:25 +08:00
envlist = {dev,luminous,mimic,rhcs}-{xenial_cluster,centos7_cluster,cluster,docker_cluster,update_cluster,update_docker_cluster,switch_to_containers,ooo_collocation,bluestore_lvm_osds,bluestore_lvm_osds_container,lvm_osds,purge_lvm_osds,purge_lvm_osds_container,shrink_mon,shrink_osd,shrink_mon_container,shrink_osd_container,docker_cluster_collocation,lvm_batch,lvm_osds_container,lvm_batch_container,infra_lv_create,add_osds,add_osds_container,rgw_multisite,rgw_multisite_container,container_podman}
tox: change container image to use master We have a latest-master image which contains builds from upstream ceph so let's use it to verify build. Signed-off-by: Sébastien Han <seb@redhat.com>
2018-10-25 22:15:36 +08:00
infra_lv_create
Tests: Add bluestore scenarios Since we started testing against Luminous, we need to add more scenarios testing. Signed-off-by: Guillaume Abrioux <gabrioux@redhat.com>
2017-07-12 21:02:32 +08:00
tests: adds a tox.ini to run the functional tests This currently tests the initial-members scenario for both ansible 2.1 and ansible 2.2. It assumes a hosts file and vagrant_ssh_config exists in the scenario directory. Signed-off-by: Andrew Schoen <aschoen@redhat.com> Resolves: pytest#harness
2016-11-05 01:25:06 +08:00
skipsdist = True
tests: adds a testing scenario for lv-create and lv-teardown Using an explicitly named testing environment name allows us to have a specific [testenv] block for this test. This greatly simplifies how it will work as it doesn't really anything from the ceph cluster tests. Signed-off-by: Andrew Schoen <aschoen@redhat.com>
2018-08-09 06:12:30 +08:00
# a test scenario for the lv-create.yml and lv-teardown playbooks
[testenv:infra_lv_create]
whitelist_externals =
vagrant
bash
cp
mkdir
tests: cat the contents of lv-create.log in infra_lv_create Signed-off-by: Andrew Schoen <aschoen@redhat.com>
2018-08-09 20:26:58 +08:00
cat
tests: adds a testing scenario for lv-create and lv-teardown Using an explicitly named testing environment name allows us to have a specific [testenv] block for this test. This greatly simplifies how it will work as it doesn't really anything from the ceph cluster tests. Signed-off-by: Andrew Schoen <aschoen@redhat.com>
2018-08-09 06:12:30 +08:00
passenv=*
setenv=
ANSIBLE_SSH_ARGS = -F {changedir}/vagrant_ssh_config
ANSIBLE_CONFIG = -F {toxinidir}/ansible.cfg
ANSIBLE_ACTION_PLUGINS = {toxinidir}/plugins/actions
ANSIBLE_CALLBACK_PLUGINS = {toxinidir}/plugins/callback
ANSIBLE_CALLBACK_WHITELIST = profile_tasks
# only available for ansible >= 2.2
ANSIBLE_STDOUT_CALLBACK = debug
deps= -r{toxinidir}/tests/requirements.txt
changedir={toxinidir}/tests/functional/centos/7/infra_lv_create
commands=
vagrant up --no-provision {posargs:--provider=virtualbox}
bash {toxinidir}/tests/scripts/generate_ssh_config.sh {changedir}
cp {toxinidir}/infrastructure-playbooks/lv-create.yml {toxinidir}/lv-create.yml
ansible-playbook -vv -i {changedir}/hosts {toxinidir}/lv-create.yml
cp {toxinidir}/infrastructure-playbooks/lv-teardown.yml {toxinidir}/lv-teardown.yml
ansible-playbook -vv -i {changedir}/hosts {toxinidir}/lv-teardown.yml --extra-vars "ireallymeanit=yes"
tests: cat the contents of lv-create.log in infra_lv_create Signed-off-by: Andrew Schoen <aschoen@redhat.com>
2018-08-09 20:26:58 +08:00
cat {toxinidir}/lv-create.log
tests: adds a testing scenario for lv-create and lv-teardown Using an explicitly named testing environment name allows us to have a specific [testenv] block for this test. This greatly simplifies how it will work as it doesn't really anything from the ceph cluster tests. Signed-off-by: Andrew Schoen <aschoen@redhat.com>
2018-08-09 06:12:30 +08:00
vagrant destroy --force
tests: adds purge_cluster and purge_dmcrypt scenarios This also removes the purge_cluster_collocated scenario as it's not needed now because of purge_cluster. Moving all the purge commands into its own section allows for ease of reuse when creating new purge scenarios. Signed-off-by: Andrew Schoen <aschoen@redhat.com>
2017-01-27 00:38:10 +08:00
# extra commands for purging clusters
# that purge the cluster and then set it up again to
# ensure that a purge can clear nodes well enough that they
# can be redployed to.
[purge]
commands=
tests: adds a scenario for purging containerized clusters Signed-off-by: Andrew Schoen <aschoen@redhat.com>
2017-05-25 20:50:37 +08:00
cp {toxinidir}/infrastructure-playbooks/{env:PURGE_PLAYBOOK:purge-cluster.yml} {toxinidir}/{env:PURGE_PLAYBOOK:purge-cluster.yml}
ansible-playbook -vv -i {changedir}/hosts {toxinidir}/{env:PURGE_PLAYBOOK:purge-cluster.yml} --extra-vars "\
tests: switch to using key/value extra-vars instead of json I continue to have issues with extra-vars as json. The latest issue being that the ceph_docker_image_tag config option included in the json was being ignored. I can't find the root cause, by using the key/value format seems to work. I've also removed several options here to simply the interface. We can add those back if they become necessary. Signed-off-by: Andrew Schoen <aschoen@redhat.com>
2017-05-03 00:15:23 +08:00
ireallymeanit=yes \
tests: adds a scenario for purging containerized clusters Signed-off-by: Andrew Schoen <aschoen@redhat.com>
2017-05-25 20:50:37 +08:00
remove_packages=yes \
ci: test luminous Luminous is out so let's test it instead of Kraken. Signed-off-by: Sébastien Han <seb@redhat.com>
2017-09-02 01:52:54 +08:00
ceph_stable_release={env:CEPH_STABLE_RELEASE:luminous} \
tests: switch to using key/value extra-vars instead of json I continue to have issues with extra-vars as json. The latest issue being that the ceph_docker_image_tag config option included in the json was being ignored. I can't find the root cause, by using the key/value format seems to work. I've also removed several options here to simply the interface. We can add those back if they become necessary. Signed-off-by: Andrew Schoen <aschoen@redhat.com>
2017-05-03 00:15:23 +08:00
fetch_directory={env:FETCH_DIRECTORY:{changedir}/fetch} \
tests: adds a scenario for purging containerized clusters Signed-off-by: Andrew Schoen <aschoen@redhat.com>
2017-05-25 20:50:37 +08:00
ceph_docker_registry={env:CEPH_DOCKER_REGISTRY:docker.io} \
ceph_docker_image={env:CEPH_DOCKER_IMAGE:ceph/daemon} \
tox: change container image to use master We have a latest-master image which contains builds from upstream ceph so let's use it to verify build. Signed-off-by: Sébastien Han <seb@redhat.com>
2018-10-25 22:15:36 +08:00
ceph_docker_image_tag={env:CEPH_DOCKER_IMAGE_TAG:latest-master} \
tests: switch to using key/value extra-vars instead of json I continue to have issues with extra-vars as json. The latest issue being that the ceph_docker_image_tag config option included in the json was being ignored. I can't find the root cause, by using the key/value format seems to work. I've also removed several options here to simply the interface. We can add those back if they become necessary. Signed-off-by: Andrew Schoen <aschoen@redhat.com>
2017-05-03 00:15:23 +08:00
"
purge-cluster: adds support for purging lvm osds This also adds a new testing scenario for purging lvm osds Signed-off-by: Andrew Schoen <aschoen@redhat.com>
2017-08-23 22:12:40 +08:00
purge: tox add lvm-setup Since we deploy > purge > deploy the LVs are gone so we much recreate them. Signed-off-by: Sébastien Han <seb@redhat.com>
2018-12-04 16:21:51 +08:00
# re-setup lvm
ansible-playbook -vv -i {changedir}/hosts {toxinidir}/tests/functional/lvm_setup.yml
purge-cluster: adds support for purging lvm osds This also adds a new testing scenario for purging lvm osds Signed-off-by: Andrew Schoen <aschoen@redhat.com>
2017-08-23 22:12:40 +08:00
# set up the cluster again
ansible-playbook -vv -i {changedir}/hosts {toxinidir}/{env:PLAYBOOK:site.yml.sample} --extra-vars "\
ci: test luminous Luminous is out so let's test it instead of Kraken. Signed-off-by: Sébastien Han <seb@redhat.com>
2017-09-02 01:52:54 +08:00
ceph_stable_release={env:CEPH_STABLE_RELEASE:luminous} \
purge-cluster: adds support for purging lvm osds This also adds a new testing scenario for purging lvm osds Signed-off-by: Andrew Schoen <aschoen@redhat.com>
2017-08-23 22:12:40 +08:00
fetch_directory={env:FETCH_DIRECTORY:{changedir}/fetch} \
ceph_docker_registry={env:CEPH_DOCKER_REGISTRY:docker.io} \
ceph_docker_image={env:CEPH_DOCKER_IMAGE:ceph/daemon} \
tox: change container image to use master We have a latest-master image which contains builds from upstream ceph so let's use it to verify build. Signed-off-by: Sébastien Han <seb@redhat.com>
2018-10-25 22:15:36 +08:00
ceph_docker_image_tag={env:CEPH_DOCKER_IMAGE_TAG:latest-master} \
purge-cluster: adds support for purging lvm osds This also adds a new testing scenario for purging lvm osds Signed-off-by: Andrew Schoen <aschoen@redhat.com>
2017-08-23 22:12:40 +08:00
ceph_dev_branch={env:CEPH_DEV_BRANCH:master} \
ceph_dev_sha1={env:CEPH_DEV_SHA1:latest} \
"
# test that the cluster can be redeployed in a healthy state
Revert "tests: add more verbosity in testinfra" This reverts commit 68eb850b27cd65571b9654fe7c1fd9c1f8435fdd. Signed-off-by: Guillaume Abrioux <gabrioux@redhat.com>
2018-06-20 22:52:38 +08:00
testinfra -n 4 --sudo -v --connection=ansible --ansible-inventory={changedir}/hosts {toxinidir}/tests/functional/tests
purge-cluster: adds support for purging lvm osds This also adds a new testing scenario for purging lvm osds Signed-off-by: Andrew Schoen <aschoen@redhat.com>
2017-08-23 22:12:40 +08:00
[purge-lvm]
commands=
cp {toxinidir}/infrastructure-playbooks/{env:PURGE_PLAYBOOK:purge-cluster.yml} {toxinidir}/{env:PURGE_PLAYBOOK:purge-cluster.yml}
ansible-playbook -vv -i {changedir}/hosts {toxinidir}/{env:PURGE_PLAYBOOK:purge-cluster.yml} --extra-vars "\
ireallymeanit=yes \
remove_packages=yes \
ci: test luminous Luminous is out so let's test it instead of Kraken. Signed-off-by: Sébastien Han <seb@redhat.com>
2017-09-02 01:52:54 +08:00
ceph_stable_release={env:CEPH_STABLE_RELEASE:luminous} \
purge-cluster: adds support for purging lvm osds This also adds a new testing scenario for purging lvm osds Signed-off-by: Andrew Schoen <aschoen@redhat.com>
2017-08-23 22:12:40 +08:00
fetch_directory={env:FETCH_DIRECTORY:{changedir}/fetch} \
ceph_docker_registry={env:CEPH_DOCKER_REGISTRY:docker.io} \
ceph_docker_image={env:CEPH_DOCKER_IMAGE:ceph/daemon} \
tox: change container image to use master We have a latest-master image which contains builds from upstream ceph so let's use it to verify build. Signed-off-by: Sébastien Han <seb@redhat.com>
2018-10-25 22:15:36 +08:00
ceph_docker_image_tag={env:CEPH_DOCKER_IMAGE_TAG:latest-master} \
purge-cluster: adds support for purging lvm osds This also adds a new testing scenario for purging lvm osds Signed-off-by: Andrew Schoen <aschoen@redhat.com>
2017-08-23 22:12:40 +08:00
"
ansible-playbook -vv -i {changedir}/hosts {toxinidir}/tests/functional/lvm_setup.yml
tests: adds purge_cluster and purge_dmcrypt scenarios This also removes the purge_cluster_collocated scenario as it's not needed now because of purge_cluster. Moving all the purge commands into its own section allows for ease of reuse when creating new purge scenarios. Signed-off-by: Andrew Schoen <aschoen@redhat.com>
2017-01-27 00:38:10 +08:00
# set up the cluster again
tests: use docker playbook when redeploying a purged cluster When we purge a containerized cluster we need to use the correct playbook when redploying the cluster. Signed-off-by: Andrew Schoen <aschoen@redhat.com>
2017-06-01 00:53:37 +08:00
ansible-playbook -vv -i {changedir}/hosts {toxinidir}/{env:PLAYBOOK:site.yml.sample} --extra-vars "\
ci: test luminous Luminous is out so let's test it instead of Kraken. Signed-off-by: Sébastien Han <seb@redhat.com>
2017-09-02 01:52:54 +08:00
ceph_stable_release={env:CEPH_STABLE_RELEASE:luminous} \
tests: switch to using key/value extra-vars instead of json I continue to have issues with extra-vars as json. The latest issue being that the ceph_docker_image_tag config option included in the json was being ignored. I can't find the root cause, by using the key/value format seems to work. I've also removed several options here to simply the interface. We can add those back if they become necessary. Signed-off-by: Andrew Schoen <aschoen@redhat.com>
2017-05-03 00:15:23 +08:00
fetch_directory={env:FETCH_DIRECTORY:{changedir}/fetch} \
tests: adds a scenario for purging containerized clusters Signed-off-by: Andrew Schoen <aschoen@redhat.com>
2017-05-25 20:50:37 +08:00
ceph_docker_registry={env:CEPH_DOCKER_REGISTRY:docker.io} \
ceph_docker_image={env:CEPH_DOCKER_IMAGE:ceph/daemon} \
tox: change container image to use master We have a latest-master image which contains builds from upstream ceph so let's use it to verify build. Signed-off-by: Sébastien Han <seb@redhat.com>
2018-10-25 22:15:36 +08:00
ceph_docker_image_tag={env:CEPH_DOCKER_IMAGE_TAG:latest-master} \
tests: run all existing tests with shaman repos If you use the 'dev' factor, the testing scenario will use repos from shaman.ceph.com. You can define CEPH_DEV_BRANCH and CEPH_DEV_SHA1 to specify which repo you'd like to test. Signed-off-by: Andrew Schoen <aschoen@redhat.com>
2017-07-17 23:26:48 +08:00
ceph_dev_branch={env:CEPH_DEV_BRANCH:master} \
ceph_dev_sha1={env:CEPH_DEV_SHA1:latest} \
tests: switch to using key/value extra-vars instead of json I continue to have issues with extra-vars as json. The latest issue being that the ceph_docker_image_tag config option included in the json was being ignored. I can't find the root cause, by using the key/value format seems to work. I've also removed several options here to simply the interface. We can add those back if they become necessary. Signed-off-by: Andrew Schoen <aschoen@redhat.com>
2017-05-03 00:15:23 +08:00
"
tests: adds purge_cluster and purge_dmcrypt scenarios This also removes the purge_cluster_collocated scenario as it's not needed now because of purge_cluster. Moving all the purge commands into its own section allows for ease of reuse when creating new purge scenarios. Signed-off-by: Andrew Schoen <aschoen@redhat.com>
2017-01-27 00:38:10 +08:00
# test that the cluster can be redeployed in a healthy state
Revert "tests: add more verbosity in testinfra" This reverts commit 68eb850b27cd65571b9654fe7c1fd9c1f8435fdd. Signed-off-by: Guillaume Abrioux <gabrioux@redhat.com>
2018-06-20 22:52:38 +08:00
testinfra -n 4 --sudo -v --connection=ansible --ansible-inventory={changedir}/hosts {toxinidir}/tests/functional/tests
tests: adds purge_cluster and purge_dmcrypt scenarios This also removes the purge_cluster_collocated scenario as it's not needed now because of purge_cluster. Moving all the purge commands into its own section allows for ease of reuse when creating new purge scenarios. Signed-off-by: Andrew Schoen <aschoen@redhat.com>
2017-01-27 00:38:10 +08:00
tests: adds a new ansible2.2-update_dmcrypt scenario This performs a rolling update on a cluster using dmcrypt dedicated journals. Signed-off-by: Andrew Schoen <aschoen@redhat.com>
2017-02-18 04:33:30 +08:00
# extra commands for performing a rolling update
# currently this hardcodes the release to kraken
# as we're still installing jewel by default
[update]
commands=
cp {toxinidir}/infrastructure-playbooks/rolling_update.yml {toxinidir}/rolling_update.yml
tests: switch to using key/value extra-vars instead of json I continue to have issues with extra-vars as json. The latest issue being that the ceph_docker_image_tag config option included in the json was being ignored. I can't find the root cause, by using the key/value format seems to work. I've also removed several options here to simply the interface. We can add those back if they become necessary. Signed-off-by: Andrew Schoen <aschoen@redhat.com>
2017-05-03 00:15:23 +08:00
ansible-playbook -vv -i {changedir}/hosts {toxinidir}/rolling_update.yml --extra-vars "\
ireallymeanit=yes \
ceph_stable_release={env:UPDATE_CEPH_STABLE_RELEASE:kraken} \
fetch_directory={env:FETCH_DIRECTORY:{changedir}/fetch} \
tests: adds *-update_docker_cluster testing scenarios Signed-off-by: Andrew Schoen <aschoen@redhat.com>
2017-06-06 22:43:14 +08:00
ceph_docker_registry={env:CEPH_DOCKER_REGISTRY:docker.io} \
ceph_docker_image={env:UPDATE_CEPH_DOCKER_IMAGE:ceph/daemon} \
tox: change container image to use master We have a latest-master image which contains builds from upstream ceph so let's use it to verify build. Signed-off-by: Sébastien Han <seb@redhat.com>
2018-10-25 22:15:36 +08:00
ceph_docker_image_tag={env:UPDATE_CEPH_DOCKER_IMAGE_TAG:latest-master} \
tests: run all existing tests with shaman repos If you use the 'dev' factor, the testing scenario will use repos from shaman.ceph.com. You can define CEPH_DEV_BRANCH and CEPH_DEV_SHA1 to specify which repo you'd like to test. Signed-off-by: Andrew Schoen <aschoen@redhat.com>
2017-07-17 23:26:48 +08:00
ceph_dev_branch={env:UPDATE_CEPH_DEV_BRANCH:master} \
ceph_dev_sha1={env:UPDATE_CEPH_DEV_SHA1:latest} \
tests: switch to using key/value extra-vars instead of json I continue to have issues with extra-vars as json. The latest issue being that the ceph_docker_image_tag config option included in the json was being ignored. I can't find the root cause, by using the key/value format seems to work. I've also removed several options here to simply the interface. We can add those back if they become necessary. Signed-off-by: Andrew Schoen <aschoen@redhat.com>
2017-05-03 00:15:23 +08:00
"
tests: adds a new ansible2.2-update_dmcrypt scenario This performs a rolling update on a cluster using dmcrypt dedicated journals. Signed-off-by: Andrew Schoen <aschoen@redhat.com>
2017-02-18 04:33:30 +08:00
tests: add missing test for rbd Add a missing test `test_rbd_mirror_service_is_running_from_luminous()`. Also using bash -c "<cmd>" to make testinfra aware that later in the upgrade process we are now running `luminous` ceph release so we must skip the rbd tests related to `jewel` ceph release. Signed-off-by: Guillaume Abrioux <gabrioux@redhat.com>
2017-10-31 02:44:56 +08:00
bash -c "CEPH_STABLE_RELEASE={env:UPDATE_CEPH_STABLE_RELEASE:luminous} testinfra -n 4 --sudo -v --connection=ansible --ansible-inventory={changedir}/hosts {toxinidir}/tests/functional/tests"
tests: adds a new ansible2.2-update_dmcrypt scenario This performs a rolling update on a cluster using dmcrypt dedicated journals. Signed-off-by: Andrew Schoen <aschoen@redhat.com>
2017-02-18 04:33:30 +08:00
shrink mon and osd Rework shrinking a monitor and an OSD playbook. Also adding test scenario. Closes: https://bugzilla.redhat.com/show_bug.cgi?id=1366807 Signed-off-by: Sébastien Han <seb@redhat.com>
2017-08-31 06:07:28 +08:00
[shrink-mon]
commands=
cp {toxinidir}/infrastructure-playbooks/shrink-mon.yml {toxinidir}/shrink-mon.yml
ansible-playbook -vv -i {changedir}/hosts {toxinidir}/shrink-mon.yml --extra-vars "\
ireallymeanit=yes \
shrink: support for container We can now shrink mon and osds on containerized deployment. Closes: https://bugzilla.redhat.com/show_bug.cgi?id=1492115 Signed-off-by: Sébastien Han <seb@redhat.com>
2017-09-18 23:45:08 +08:00
mon_to_kill={env:MON_TO_KILL:ceph-mon2} \
tox: add missing ceph_docker_image_tag in shrink When calling shrink on containerized deployment, we were first doing the setup with `latest-master` and then when calling the playbook we were using the default value for `ceph_docker_image_tag` that comes from ceph-defaults. Now we pass `ceph_docker_image_tag={env:CEPH_DOCKER_IMAGE_TAG:latest-master}` so the play will run the right container image. Signed-off-by: Sébastien Han <seb@redhat.com>
2018-12-05 01:41:36 +08:00
ceph_docker_image_tag={env:CEPH_DOCKER_IMAGE_TAG:latest-master} \
shrink mon and osd Rework shrinking a monitor and an OSD playbook. Also adding test scenario. Closes: https://bugzilla.redhat.com/show_bug.cgi?id=1366807 Signed-off-by: Sébastien Han <seb@redhat.com>
2017-08-31 06:07:28 +08:00
"
[shrink-osd]
commands=
cp {toxinidir}/infrastructure-playbooks/shrink-osd.yml {toxinidir}/shrink-osd.yml
ansible-playbook -vv -i {changedir}/hosts {toxinidir}/shrink-osd.yml --extra-vars "\
ireallymeanit=yes \
osd_to_kill=0 \
tox: add missing ceph_docker_image_tag in shrink When calling shrink on containerized deployment, we were first doing the setup with `latest-master` and then when calling the playbook we were using the default value for `ceph_docker_image_tag` that comes from ceph-defaults. Now we pass `ceph_docker_image_tag={env:CEPH_DOCKER_IMAGE_TAG:latest-master}` so the play will run the right container image. Signed-off-by: Sébastien Han <seb@redhat.com>
2018-12-05 01:41:36 +08:00
ceph_docker_image_tag={env:CEPH_DOCKER_IMAGE_TAG:latest-master} \
shrink mon and osd Rework shrinking a monitor and an OSD playbook. Also adding test scenario. Closes: https://bugzilla.redhat.com/show_bug.cgi?id=1366807 Signed-off-by: Sébastien Han <seb@redhat.com>
2017-08-31 06:07:28 +08:00
"
switch-from-non-containerized-to-containerized: mask unit files We must mask the image so we are sure that even if the system reboots then the OSDs won't start. Also remove Ceph udev rules if found on the system prior to deploy containers. If we don't do this we are exposed to conflicts between udev rules and sytemd unit files. Also add the CI will now test the migration from a non-containerized cluster to a containerized cluster. Signed-off-by: Sébastien Han <seb@redhat.com>
2017-08-25 20:36:07 +08:00
[switch-to-containers]
commands=
cp {toxinidir}/infrastructure-playbooks/switch-from-non-containerized-to-containerized-ceph-daemons.yml {toxinidir}/switch-from-non-containerized-to-containerized-ceph-daemons.yml
ansible-playbook -vv -i {changedir}/hosts {toxinidir}/switch-from-non-containerized-to-containerized-ceph-daemons.yml --extra-vars "\
ireallymeanit=yes \
fetch_directory={env:FETCH_DIRECTORY:{changedir}/fetch} \
ceph_docker_registry={env:CEPH_DOCKER_REGISTRY:docker.io} \
tests: do not upgrade ceph release for switch_to_containers scenario Using `UPDATE_*` environment variables here will make an upgrade of the ceph release when running switch_to_containers scenario which is not correct. Eg: If ceph luminous was first deployed, then we should switch to ceph luminous containers, not to mimic. Signed-off-by: Guillaume Abrioux <gabrioux@redhat.com>
2018-09-08 01:38:41 +08:00
ceph_docker_image={env:CEPH_DOCKER_IMAGE:ceph/daemon} \
tox: change container image to use master We have a latest-master image which contains builds from upstream ceph so let's use it to verify build. Signed-off-by: Sébastien Han <seb@redhat.com>
2018-10-25 22:15:36 +08:00
ceph_docker_image_tag={env:CEPH_DOCKER_IMAGE_TAG:latest-master} \
tests: do not upgrade ceph release for switch_to_containers scenario Using `UPDATE_*` environment variables here will make an upgrade of the ceph release when running switch_to_containers scenario which is not correct. Eg: If ceph luminous was first deployed, then we should switch to ceph luminous containers, not to mimic. Signed-off-by: Guillaume Abrioux <gabrioux@redhat.com>
2018-09-08 01:38:41 +08:00
ceph_dev_branch={env:CEPH_DEV_BRANCH:master} \
ceph_dev_sha1={env:CEPH_DEV_SHA1:latest} \
switch-from-non-containerized-to-containerized: mask unit files We must mask the image so we are sure that even if the system reboots then the OSDs won't start. Also remove Ceph udev rules if found on the system prior to deploy containers. If we don't do this we are exposed to conflicts between udev rules and sytemd unit files. Also add the CI will now test the migration from a non-containerized cluster to a containerized cluster. Signed-off-by: Sébastien Han <seb@redhat.com>
2017-08-25 20:36:07 +08:00
"
Revert "tests: add more verbosity in testinfra" This reverts commit 68eb850b27cd65571b9654fe7c1fd9c1f8435fdd. Signed-off-by: Guillaume Abrioux <gabrioux@redhat.com>
2018-06-20 22:52:38 +08:00
testinfra -n 4 --sudo -v --connection=ansible --ansible-inventory={changedir}/hosts-switch-to-containers {toxinidir}/tests/functional/tests
switch-from-non-containerized-to-containerized: mask unit files We must mask the image so we are sure that even if the system reboots then the OSDs won't start. Also remove Ceph udev rules if found on the system prior to deploy containers. If we don't do this we are exposed to conflicts between udev rules and sytemd unit files. Also add the CI will now test the migration from a non-containerized cluster to a containerized cluster. Signed-off-by: Sébastien Han <seb@redhat.com>
2017-08-25 20:36:07 +08:00
tests: add tests for day-2-operation playbook Adding testing scenarios for day-2-operation playbook. Steps: - deploys a cluster, - run testinfra, - test idempotency, - add a new osd node, - run testinfra Signed-off-by: Guillaume Abrioux <gabrioux@redhat.com>
2018-10-16 23:05:10 +08:00
[add-osds]
commands=
ansible-playbook -vv -i {changedir}/hosts-2 --limit osd1 {toxinidir}/tests/functional/setup.yml
cp {toxinidir}/infrastructure-playbooks/add-osd.yml {toxinidir}/add-osd.yml
ansible-playbook -vv -i {changedir}/hosts-2 --limit osd1 {toxinidir}/add-osd.yml --extra-vars "\
ireallymeanit=yes \
fetch_directory={env:FETCH_DIRECTORY:{changedir}/fetch} \
ceph_stable_release={env:CEPH_STABLE_RELEASE:mimic} \
ceph_docker_registry={env:CEPH_DOCKER_REGISTRY:docker.io} \
ceph_docker_image={env:CEPH_DOCKER_IMAGE:ceph/daemon} \
tox: change container image to use master We have a latest-master image which contains builds from upstream ceph so let's use it to verify build. Signed-off-by: Sébastien Han <seb@redhat.com>
2018-10-25 22:15:36 +08:00
ceph_docker_image_tag={env:CEPH_DOCKER_IMAGE_TAG:latest-master} \
tests: add tests for day-2-operation playbook Adding testing scenarios for day-2-operation playbook. Steps: - deploys a cluster, - run testinfra, - test idempotency, - add a new osd node, - run testinfra Signed-off-by: Guillaume Abrioux <gabrioux@redhat.com>
2018-10-16 23:05:10 +08:00
ceph_dev_branch={env:CEPH_DEV_BRANCH:master} \
ceph_dev_sha1={env:CEPH_DEV_SHA1:latest} \
"
testinfra -n 4 --sudo -v --connection=ansible --ansible-inventory={changedir}/hosts-2 {toxinidir}/tests/functional/tests
rgw: add testing scenario for rgw multisite This will setup 2 cluster with rgw multisite enabled. First cluster will act as the 'master', the 2nd will be the secondary one. Signed-off-by: Guillaume Abrioux <gabrioux@redhat.com>
2018-10-25 04:27:28 +08:00
[rgw-multisite]
commands=
bash -c "cd {changedir}/secondary && vagrant up --no-provision {posargs:--provider=virtualbox}"
bash -c "cd {changedir}/secondary && bash {toxinidir}/tests/scripts/generate_ssh_config.sh {changedir}/secondary"
ansible-playbook --ssh-extra-args='-F {changedir}/secondary/vagrant_ssh_config' -vv -i {changedir}/secondary/hosts {toxinidir}/tests/functional/setup.yml
tests: apply dev_setup on the secondary cluster for rgw_multisite we must apply this playbook before deploying the secondary cluster. Otherwise, there will be a mismatch between the two deployed cluster. Signed-off-by: Guillaume Abrioux <gabrioux@redhat.com>
2018-11-27 17:26:41 +08:00
ansible-playbook -vv -i "localhost," -c local {toxinidir}/tests/functional/dev_setup.yml --extra-vars "change_dir={changedir}/secondary ceph_dev_branch={env:CEPH_DEV_BRANCH:master} ceph_dev_sha1={env:CEPH_DEV_SHA1:latest}" --tags "vagrant_setup"
tests: rgw_multisite allow clusters to talk to each other Adding this rule on the hypervisor will allow cluster to talk to each other. Signed-off-by: Guillaume Abrioux <gabrioux@redhat.com>
2018-11-29 01:46:45 +08:00
ansible -i localhost, all -c local -b -m iptables -a 'chain=FORWARD protocol=tcp source=192.168.0.0/16 destination=192.168.0.0/16 jump=ACCEPT action=insert rule_num=1'
rgw: add testing scenario for rgw multisite This will setup 2 cluster with rgw multisite enabled. First cluster will act as the 'master', the 2nd will be the secondary one. Signed-off-by: Guillaume Abrioux <gabrioux@redhat.com>
2018-10-25 04:27:28 +08:00
ansible-playbook --ssh-extra-args='-F {changedir}/secondary/vagrant_ssh_config' -vv -i {changedir}/secondary/hosts {toxinidir}/{env:PLAYBOOK:site.yml.sample} --extra-vars "\
ireallymeanit=yes \
fetch_directory={env:FETCH_DIRECTORY:{changedir}/secondary/fetch} \
ceph_stable_release={env:CEPH_STABLE_RELEASE:mimic} \
ceph_docker_registry={env:CEPH_DOCKER_REGISTRY:docker.io} \
ceph_docker_image={env:CEPH_DOCKER_IMAGE:ceph/daemon} \
tests: fix image tag for secondary rgw cluster (rgw_multisite) the first cluster is using `latest-master` while the second is using `latest` which is not the right version to be used here. Signed-off-by: Guillaume Abrioux <gabrioux@redhat.com>
2018-11-27 21:50:18 +08:00
ceph_docker_image_tag={env:CEPH_DOCKER_IMAGE_TAG:latest-master} \
rgw: add testing scenario for rgw multisite This will setup 2 cluster with rgw multisite enabled. First cluster will act as the 'master', the 2nd will be the secondary one. Signed-off-by: Guillaume Abrioux <gabrioux@redhat.com>
2018-10-25 04:27:28 +08:00
ceph_dev_branch={env:CEPH_DEV_BRANCH:master} \
ceph_dev_sha1={env:CEPH_DEV_SHA1:latest} \
"
tests: add rgw_multisite functional test Add a playbook that will upload a file on the master then try to get info from the secondary node, this way we can check if the replication is ok. Signed-off-by: Guillaume Abrioux <gabrioux@redhat.com>
2018-10-29 20:30:59 +08:00
ansible-playbook -vv -i {changedir}/hosts {toxinidir}/tests/functional/rgw_multisite.yml --extra-vars "ceph_docker_registry={env:CEPH_DOCKER_REGISTRY:docker.io} ceph_docker_image={env:CEPH_DOCKER_IMAGE:ceph/daemon} ceph_docker_image_tag={env:CEPH_DOCKER_IMAGE_TAG:latest}"
ansible-playbook -vv --ssh-extra-args='-F {changedir}/secondary/vagrant_ssh_config' -i {changedir}/secondary/hosts {toxinidir}/tests/functional/rgw_multisite.yml --extra-vars "ceph_docker_registry={env:CEPH_DOCKER_REGISTRY:docker.io} ceph_docker_image={env:CEPH_DOCKER_IMAGE:ceph/daemon} ceph_docker_image_tag={env:CEPH_DOCKER_IMAGE_TAG:latest}"
bash -c "cd {changedir}/secondary && vagrant destroy --force"
tests: rgw_multisite allow clusters to talk to each other Adding this rule on the hypervisor will allow cluster to talk to each other. Signed-off-by: Guillaume Abrioux <gabrioux@redhat.com>
2018-11-29 01:46:45 +08:00
ansible -i localhost, all -c local -b -m iptables -a 'chain=FORWARD protocol=tcp source=192.168.0.0/16 destination=192.168.0.0/16 jump=ACCEPT action=insert rule_num=1 state=absent'
rgw: add testing scenario for rgw multisite This will setup 2 cluster with rgw multisite enabled. First cluster will act as the 'master', the 2nd will be the secondary one. Signed-off-by: Guillaume Abrioux <gabrioux@redhat.com>
2018-10-25 04:27:28 +08:00
tests: adds a tox.ini to run the functional tests This currently tests the initial-members scenario for both ansible 2.1 and ansible 2.2. It assumes a hosts file and vagrant_ssh_config exists in the scenario directory. Signed-off-by: Andrew Schoen <aschoen@redhat.com> Resolves: pytest#harness
2016-11-05 01:25:06 +08:00
[testenv]
tests: make the tox.ini config call the ssh config helper script Signed-off-by: Alfredo Deza <adeza@redhat.com> Resolves: pytest#harness
2016-11-05 02:01:28 +08:00
whitelist_externals =
vagrant
bash
tests: test with the latest ansible stable-2.2 branch from github Signed-off-by: Andrew Schoen <aschoen@redhat.com>
2017-01-10 20:53:17 +08:00
pip
tests: copy purge-cluster.yml to root of ceph-ansible There is an Ansible bug which makes the playbook fail when we are running a playbook from the non-git root directory. The real problem is that the ansible.cfg is not honoured and we are including variable from roles/<role>/defaults/main.yml The fix is too copy the purge cluster playbook on the git root directory and execute it. Signed-off-by: Andrew Schoen <aschoen@redhat.com>
2017-01-11 06:56:07 +08:00
cp
tests: implement reboot after a deployment We don't test server reboot, a lot of things can happen after that. So now, we deploy, reboot then we run testinfra. Signed-off-by: Sébastien Han <seb@redhat.com>
2017-09-22 05:47:36 +08:00
sleep
tests: add tests for day-2-operation playbook Adding testing scenarios for day-2-operation playbook. Steps: - deploys a cluster, - run testinfra, - test idempotency, - add a new osd node, - run testinfra Signed-off-by: Guillaume Abrioux <gabrioux@redhat.com>
2018-10-16 23:05:10 +08:00
rm
tests: adds a tox.ini to run the functional tests This currently tests the initial-members scenario for both ansible 2.1 and ansible 2.2. It assumes a hosts file and vagrant_ssh_config exists in the scenario directory. Signed-off-by: Andrew Schoen <aschoen@redhat.com> Resolves: pytest#harness
2016-11-05 01:25:06 +08:00
passenv=*
tests: always use sitepackages=True This is mostly important in rhcs testing so that our tests can use packages installed on the distro. Signed-off-by: Andrew Schoen <aschoen@redhat.com>
2017-08-28 22:59:28 +08:00
sitepackages=True
tests: adds a tox.ini to run the functional tests This currently tests the initial-members scenario for both ansible 2.1 and ansible 2.2. It assumes a hosts file and vagrant_ssh_config exists in the scenario directory. Signed-off-by: Andrew Schoen <aschoen@redhat.com> Resolves: pytest#harness
2016-11-05 01:25:06 +08:00
setenv=
tests: remove the need for a setenv entry per scenario in tox.ini Signed-off-by: Andrew Schoen <aschoen@redhat.com> Resolves: pytest#harness
2016-11-05 01:49:18 +08:00
ANSIBLE_SSH_ARGS = -F {changedir}/vagrant_ssh_config
tox: fix a typo the line setting `ANSIBLE_CONFIG` obviously contains a typo introduced by 1e283bf69be8b9efbc1a7a873d91212ad57c7351 `ANSIBLE_CONFIG` has to point to a path only (path to an ansible.cfg) Signed-off-by: Guillaume Abrioux <gabrioux@redhat.com>
2018-10-25 20:42:54 +08:00
ANSIBLE_CONFIG = {toxinidir}/ansible.cfg
tests: adds a tox.ini to run the functional tests This currently tests the initial-members scenario for both ansible 2.1 and ansible 2.2. It assumes a hosts file and vagrant_ssh_config exists in the scenario directory. Signed-off-by: Andrew Schoen <aschoen@redhat.com> Resolves: pytest#harness
2016-11-05 01:25:06 +08:00
ANSIBLE_ACTION_PLUGINS = {toxinidir}/plugins/actions
Cleanup plugins directories and references Having callback_plugins, and action plugins in random locations causes a lot of disparity. We should centralize this into one place in the plugins directory and fix up the ansible.cfg to reflect this. Additionally, since the ansible.cfg already reflects action_plugins, we don't need a link to action_plugins in the base of the repository.
2018-03-13 19:30:09 +08:00
ANSIBLE_CALLBACK_PLUGINS = {toxinidir}/plugins/callback
Enable profile_tasks callback plugin This patch adds the `profile_tasks` callback plugin to the whitelist so that we can identify the tasks which are taking the longest amount of time to run.
2017-10-13 00:43:29 +08:00
ANSIBLE_CALLBACK_WHITELIST = profile_tasks
tests: preserve newlines in ansible output when testing Signed-off-by: Andrew Schoen <aschoen@redhat.com>
2016-12-16 02:23:17 +08:00
# only available for ansible >= 2.2
ANSIBLE_STDOUT_CALLBACK = debug
common: make the delegate_facts feature optional Since we encountered issue with this on ansible2.2, this commit provide the ability to enable or disable it regarding which ansible we are running. Signed-off-by: Guillaume Abrioux <gabrioux@redhat.com>
2017-10-31 21:39:29 +08:00
ansible2.2: DELEGATE_FACTS_HOST = False
tests: docker_cluster should use the site-docker.yml playbook This commits allows for scenarios to pick their own playbook while defaulting to use site.yml.sample. Signed-off-by: Andrew Schoen <aschoen@redhat.com>
2016-12-02 00:19:19 +08:00
docker_cluster: PLAYBOOK = site-docker.yml.sample
tests: re-add missing param in tox this line has been removed by mistake in a53aa9e. Signed-off-by: Guillaume Abrioux <gabrioux@redhat.com>
2017-10-19 21:24:02 +08:00
docker_cluster_collocation: PLAYBOOK = site-docker.yml.sample
ci: add tripleo scenario testing This should help to see earlier any failure in a tripleo deployment scenario. Signed-off-by: Guillaume Abrioux <gabrioux@redhat.com>
2018-02-16 20:53:52 +08:00
ooo_collocation: PLAYBOOK = site-docker.yml.sample
tests: adds *-update_docker_cluster testing scenarios Signed-off-by: Andrew Schoen <aschoen@redhat.com>
2017-06-06 22:43:14 +08:00
update_docker_cluster: PLAYBOOK = site-docker.yml.sample
tests: split purge_cluster, followup on a53aa9e - split purge_cluster because we need to test filestore and bluestore scenarios. - clean some leftover. Signed-off-by: Guillaume Abrioux <gabrioux@redhat.com>
2017-10-20 23:18:39 +08:00
purge_cluster_container: PLAYBOOK = site-docker.yml.sample
purge_cluster_container: PURGE_PLAYBOOK = purge-docker-cluster.yml
tests: add purge_lvm_osds_container scenario This commits adds the purge_lvm_osds_container scenario. Signed-off-by: Guillaume Abrioux <gabrioux@redhat.com>
2018-11-30 18:25:25 +08:00
purge_lvm_osds_container: PLAYBOOK = site-docker.yml.sample
purge_lvm_osds_container: PURGE_PLAYBOOK = purge-docker-cluster.yml
tests: add tests for day-2-operation playbook Adding testing scenarios for day-2-operation playbook. Steps: - deploys a cluster, - run testinfra, - test idempotency, - add a new osd node, - run testinfra Signed-off-by: Guillaume Abrioux <gabrioux@redhat.com>
2018-10-16 23:05:10 +08:00
add_osds: PLAYBOOK = site.yml.sample
add_osds_container: PLAYBOOK = site-docker.yml.sample
rgw: add testing scenario for rgw multisite This will setup 2 cluster with rgw multisite enabled. First cluster will act as the 'master', the 2nd will be the secondary one. Signed-off-by: Guillaume Abrioux <gabrioux@redhat.com>
2018-10-25 04:27:28 +08:00
rgw_multisite: PLAYBOOK = site.yml.sample
rgw_multisite_container: PLAYBOOK = site-docker.yml.sample
shrink: support for container We can now shrink mon and osds on containerized deployment. Closes: https://bugzilla.redhat.com/show_bug.cgi?id=1492115 Signed-off-by: Sébastien Han <seb@redhat.com>
2017-09-18 23:45:08 +08:00
shrink_mon_container: PLAYBOOK = site-docker.yml.sample
shrink_mon_container: MON_TO_KILL = mon2
shrink_osd_container: PLAYBOOK = site-docker.yml.sample
test: do not always copy admin key The admin key must be copied on the osd nodes only when we test the shrink scenario. Shrink relies on ceph-disk commands that require the admin key on the node where it's being executed. Now we only copy the key when running on the shrink-osd scenario. Signed-off-by: Sébastien Han <seb@redhat.com>
2018-06-05 11:56:55 +08:00
shrink_osd_container: COPY_ADMIN_KEY = True
shrink_osd: COPY_ADMIN_KEY = True
Add new container scenario Test with podman instead of docker and also support for python 3 only. Signed-off-by: Sébastien Han <seb@redhat.com>
2018-11-08 17:02:37 +08:00
container_podman: PLAYBOOK = site-docker.yml.sample
Tests: Add bluestore scenarios Since we started testing against Luminous, we need to add more scenarios testing. Signed-off-by: Guillaume Abrioux <gabrioux@redhat.com>
2017-07-12 21:02:32 +08:00
tests: set ceph_stable_release to luminous for rhcs Signed-off-by: Andrew Schoen <aschoen@redhat.com>
2017-09-07 22:45:56 +08:00
rhcs: CEPH_STABLE_RELEASE = luminous
Revert "tests: set CEPH_STABLE_RELEASE in ceph-build" This reverts commit 7a1d7d92ff4d6f38be9f11f4c26909b361b58f99.
2017-12-06 22:18:42 +08:00
luminous: CEPH_STABLE_RELEASE = luminous
tests: set CEPH_DOCKER_IMAGE_TAG when ceph release is luminous Since latest points to mimic for the ceph container images, we need to set `CEPH_DOCKER_IMAGE_TAG` to `latest-luminous` when ceph release is luminous Signed-off-by: Guillaume Abrioux <gabrioux@redhat.com>
2018-06-11 21:40:54 +08:00
luminous: CEPH_DOCKER_IMAGE_TAG = latest-luminous
tests: keep same ceph release during handlers/idempotency test since `latest` points to `mimic`, we need to force the test to keep the same ceph release when testing anything else than `mimic`. Signed-off-by: Guillaume Abrioux <gabrioux@redhat.com>
2018-06-15 16:44:25 +08:00
luminous: CEPH_DOCKER_IMAGE_TAG_BIS = latest-bis-luminous
testing: add luminous factor for testing Signed-off-by: Alfredo Deza <adeza@redhat.com> Co-Authored-by: Guillaume Abrioux <gabrioux@redhat.com>
2017-05-16 00:46:49 +08:00
luminous: UPDATE_CEPH_STABLE_RELEASE = luminous
tests: set CEPH_DOCKER_IMAGE_TAG when ceph release is luminous Since latest points to mimic for the ceph container images, we need to set `CEPH_DOCKER_IMAGE_TAG` to `latest-luminous` when ceph release is luminous Signed-off-by: Guillaume Abrioux <gabrioux@redhat.com>
2018-06-11 21:40:54 +08:00
luminous: UPDATE_CEPH_DOCKER_IMAGE_TAG = latest
tox: test mimic deployment Let's try to deploy mimic. Signed-off-by: Guillaume Abrioux <gabrioux@redhat.com> (cherry picked from commit d2cdfd830c339738b43e6a4417ca5d41fe416f86)
2018-07-06 16:57:32 +08:00
mimic: CEPH_STABLE_RELEASE = mimic
mimic: CEPH_DOCKER_IMAGE_TAG = latest-mimic
mimic: CEPH_DOCKER_IMAGE_TAG_BIS = latest-bis
mimic: UPDATE_CEPH_STABLE_RELEASE = mimic
mimic: UPDATE_CEPH_DOCKER_IMAGE_TAG = latest
tests: adds an lvm_osds testing scenario Signed-off-by: Andrew Schoen <aschoen@redhat.com>
2017-07-26 02:46:22 +08:00
lvm_osds: CEPH_STABLE_RELEASE = luminous
ci: test lvm in containerized Signed-off-by: Sébastien Han <seb@redhat.com>
2018-07-13 02:30:59 +08:00
lvm_osds: PLAYBOOK = site.yml.sample
lvm_osds_container: CEPH_STABLE_RELEASE = luminous
lvm_osds_container: PLAYBOOK = site-docker.yml.sample
tests add the bluestore scenario in tox.ini Signed-off-by: Alfredo Deza <adeza@redhat.com>
2017-10-25 01:02:42 +08:00
bluestore_lvm_osds: CEPH_STABLE_RELEASE = luminous
ci: test lvm in containerized Signed-off-by: Sébastien Han <seb@redhat.com>
2018-07-13 02:30:59 +08:00
bluestore_lvm_osds_container: CEPH_STABLE_RELEASE = luminous
ceph_volume: refactor This commit does a couple of things: * Avoid code duplication * Clarify the code * add more unit tests * add myself to the author of the module Signed-off-by: Sébastien Han <seb@redhat.com>
2018-10-04 01:52:42 +08:00
bluestore_lvm_osds_container: PLAYBOOK = site-docker.yml.sample
lvm_batch_container: PLAYBOOK = site-docker.yml.sample
lvm_batch_container: CEPH_STABLE_RELEASE = luminous
tests: support update scenarios in test_rbd_mirror_is_up() `test_rbd_mirror_is_up()` is failing on update scenarios because it assumes the `ceph_stable_release` is still set to the value of the original ceph release, it means it won't enter in the right part of the condition and fails. Signed-off-by: Guillaume Abrioux <gabrioux@redhat.com>
2018-07-18 17:07:49 +08:00
update_cluster: ROLLING_UPDATE = True
update_docker_cluster: ROLLING_UPDATE = True
tests: add tests for day-2-operation playbook Adding testing scenarios for day-2-operation playbook. Steps: - deploys a cluster, - run testinfra, - test idempotency, - add a new osd node, - run testinfra Signed-off-by: Guillaume Abrioux <gabrioux@redhat.com>
2018-10-16 23:05:10 +08:00
add_osds: CEPH_STABLE_RELEASE = luminous
add_osds_container: CEPH_STABLE_RELEASE = luminous
rgw: add testing scenario for rgw multisite This will setup 2 cluster with rgw multisite enabled. First cluster will act as the 'master', the 2nd will be the secondary one. Signed-off-by: Guillaume Abrioux <gabrioux@redhat.com>
2018-10-25 04:27:28 +08:00
rgw_multisite: CEPH_STABLE_RELEASE = luminous
rgw_multisite_container: CEPH_STABLE_RELEASE = luminous
tests: test ooo_collocation agasint v3.0.3 ceph-container image Signed-off-by: Guillaume Abrioux <gabrioux@redhat.com>
2018-11-06 16:17:29 +08:00
ooo_collocation: CEPH_DOCKER_IMAGE_TAG = v3.0.3-stable-3.0-luminous-centos-7-x86_64
tests: refact ci testing master We should test ceph-ansible against the latest ansible stable version on master. This commit also remove the pinning to 1.7.1 version of testinfra because ansible 2.5 requires a newer version. Signed-off-by: Guillaume Abrioux <gabrioux@redhat.com>
2018-05-31 18:02:26 +08:00
deps= -r{toxinidir}/tests/requirements.txt
tests: adds a tox.ini to run the functional tests This currently tests the initial-members scenario for both ansible 2.1 and ansible 2.2. It assumes a hosts file and vagrant_ssh_config exists in the scenario directory. Signed-off-by: Andrew Schoen <aschoen@redhat.com> Resolves: pytest#harness
2016-11-05 01:25:06 +08:00
changedir=
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
# tests a 1 mon, 1 osd, 1 mds and 1 rgw xenial cluster using non-collocated OSD scenario
tests: rename the directory for xenial_cluster Signed-off-by: Andrew Schoen <aschoen@redhat.com>
2016-12-02 06:48:06 +08:00
xenial_cluster: {toxinidir}/tests/functional/ubuntu/16.04/cluster
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
# tests a 1 mon, 1 osd, 1 mds and 1 rgw centos7 cluster using non-collocated OSD scenario
tests: rename the directory for centos7_cluster Signed-off-by: Andrew Schoen <aschoen@redhat.com>
2016-12-02 06:59:27 +08:00
centos7_cluster: {toxinidir}/tests/functional/centos/7/cluster
shrink mon and osd Rework shrinking a monitor and an OSD playbook. Also adding test scenario. Closes: https://bugzilla.redhat.com/show_bug.cgi?id=1366807 Signed-off-by: Sébastien Han <seb@redhat.com>
2017-08-31 06:07:28 +08:00
shrink_mon: {toxinidir}/tests/functional/centos/7/cluster
shrink: support for container We can now shrink mon and osds on containerized deployment. Closes: https://bugzilla.redhat.com/show_bug.cgi?id=1492115 Signed-off-by: Sébastien Han <seb@redhat.com>
2017-09-18 23:45:08 +08:00
shrink_mon_container: {toxinidir}/tests/functional/centos/7/docker
tests: do not deploy all daemons for shrink osds scenarios Let's create a dedicated environment for these scenarios, there is no need to deploy everything. By the way, doing so will save some times. Signed-off-by: Guillaume Abrioux <gabrioux@redhat.com>
2018-07-23 22:40:49 +08:00
shrink_osd: {toxinidir}/tests/functional/centos/7/shrink_osd
shrink_osd_container: {toxinidir}/tests/functional/centos/7/shrink_osd_container
tests: add an alias of cluster for the centos7_cluster scenario When testing this downstream it makes more sense for this scenario to be named just 'cluster' because have 'centos7' in the name is misleading. Signed-off-by: Andrew Schoen <aschoen@redhat.com>
2017-04-06 02:36:51 +08:00
# an alias for centos7_cluster, this makes the name better suited for rhcs testing
cluster: {toxinidir}/tests/functional/centos/7/cluster
tests: adds a docker_cluster scenario Signed-off-by: Andrew Schoen <aschoen@redhat.com>
2016-12-01 02:20:07 +08:00
# tests a 1 mon, 1 osd, 1 mds and 1 rgw centos7 cluster using docker
Tests: rename tests directories Since we are hitting this bug : https://bugzilla.redhat.com/show_bug.cgi?id=1324587 eg: `failed: internal error: Monitor path /var/lib/libvirt/qemu/domain-bs-docker-cl uster-dmcrypt-journal-collocation_mon0_1499294943_ba9faf7bf296533177f6/monitor. sock too big for destination` and we can't upgrade libvirt in our CI for some reason we need to get the directories name shorter in order to workaround this issue Signed-off-by: Guillaume Abrioux <gabrioux@redhat.com>
2017-07-08 00:30:06 +08:00
docker_cluster: {toxinidir}/tests/functional/centos/7/docker
ci: add collocation scenario Signed-off-by: Sébastien Han <seb@redhat.com>
2017-09-28 00:22:15 +08:00
docker_cluster_collocation: {toxinidir}/tests/functional/centos/7/docker-collocation
Tests: rename tests directories Since we are hitting this bug : https://bugzilla.redhat.com/show_bug.cgi?id=1324587 eg: `failed: internal error: Monitor path /var/lib/libvirt/qemu/domain-bs-docker-cl uster-dmcrypt-journal-collocation_mon0_1499294943_ba9faf7bf296533177f6/monitor. sock too big for destination` and we can't upgrade libvirt in our CI for some reason we need to get the directories name shorter in order to workaround this issue Signed-off-by: Guillaume Abrioux <gabrioux@redhat.com>
2017-07-08 00:30:06 +08:00
update_docker_cluster: {toxinidir}/tests/functional/centos/7/docker
tests: split purge_cluster, followup on a53aa9e - split purge_cluster because we need to test filestore and bluestore scenarios. - clean some leftover. Signed-off-by: Guillaume Abrioux <gabrioux@redhat.com>
2017-10-20 23:18:39 +08:00
purge_cluster_non_container: {toxinidir}/tests/functional/centos/7/cluster
purge_cluster_container: {toxinidir}/tests/functional/centos/7/docker
tests: adds an update_cluster testing scenario This updates the centos 7 cluster scenario from jewel to kraken using the rolling_update playbook. Signed-off-by: Andrew Schoen <aschoen@redhat.com>
2017-03-08 04:05:03 +08:00
update_cluster: {toxinidir}/tests/functional/centos/7/cluster
switch-from-non-containerized-to-containerized: mask unit files We must mask the image so we are sure that even if the system reboots then the OSDs won't start. Also remove Ceph udev rules if found on the system prior to deploy containers. If we don't do this we are exposed to conflicts between udev rules and sytemd unit files. Also add the CI will now test the migration from a non-containerized cluster to a containerized cluster. Signed-off-by: Sébastien Han <seb@redhat.com>
2017-08-25 20:36:07 +08:00
switch_to_containers: {toxinidir}/tests/functional/centos/7/cluster
tests: adds an lvm_osds testing scenario Signed-off-by: Andrew Schoen <aschoen@redhat.com>
2017-07-26 02:46:22 +08:00
lvm_osds: {toxinidir}/tests/functional/centos/7/lvm-osds
ci: test lvm in containerized Signed-off-by: Sébastien Han <seb@redhat.com>
2018-07-13 02:30:59 +08:00
lvm_osds_container: {toxinidir}/tests/functional/centos/7/lvm-osds-container
ceph-volume: implement the 'lvm batch' subcommand This adds the action 'batch' to the ceph-volume module so that we can run the new 'ceph-volume lvm batch' subcommand. A functional test is also included. If devices is defind and osd_scenario is lvm then the 'ceph-volume lvm batch' command will be used to create the OSDs. Signed-off-by: Andrew Schoen <aschoen@redhat.com>
2018-08-04 00:15:58 +08:00
lvm_batch: {toxinidir}/tests/functional/centos/7/lvm-batch
ci: test lvm in containerized Signed-off-by: Sébastien Han <seb@redhat.com>
2018-07-13 02:30:59 +08:00
lvm_batch_container: {toxinidir}/tests/functional/centos/7/lvm-batch-container
tests add the bluestore scenario in tox.ini Signed-off-by: Alfredo Deza <adeza@redhat.com>
2017-10-25 01:02:42 +08:00
bluestore_lvm_osds: {toxinidir}/tests/functional/centos/7/bs-lvm-osds
ci: test lvm in containerized Signed-off-by: Sébastien Han <seb@redhat.com>
2018-07-13 02:30:59 +08:00
bluestore_lvm_osds_container: {toxinidir}/tests/functional/centos/7/bs-lvm-osds-container
purge-cluster: adds support for purging lvm osds This also adds a new testing scenario for purging lvm osds Signed-off-by: Andrew Schoen <aschoen@redhat.com>
2017-08-23 22:12:40 +08:00
purge_lvm_osds: {toxinidir}/tests/functional/centos/7/lvm-osds
tests: add purge_lvm_osds_container scenario This commits adds the purge_lvm_osds_container scenario. Signed-off-by: Guillaume Abrioux <gabrioux@redhat.com>
2018-11-30 18:25:25 +08:00
purge_lvm_osds_container: {toxinidir}/tests/functional/centos/7/lvm-osds-container
ci: add tripleo scenario testing This should help to see earlier any failure in a tripleo deployment scenario. Signed-off-by: Guillaume Abrioux <gabrioux@redhat.com>
2018-02-16 20:53:52 +08:00
ooo_collocation: {toxinidir}/tests/functional/centos/7/ooo-collocation
tests: add tests for day-2-operation playbook Adding testing scenarios for day-2-operation playbook. Steps: - deploys a cluster, - run testinfra, - test idempotency, - add a new osd node, - run testinfra Signed-off-by: Guillaume Abrioux <gabrioux@redhat.com>
2018-10-16 23:05:10 +08:00
add_osds: {toxinidir}/tests/functional/centos/7/add-osds
add_osds_container: {toxinidir}/tests/functional/centos/7/add-osds-container
rgw: add testing scenario for rgw multisite This will setup 2 cluster with rgw multisite enabled. First cluster will act as the 'master', the 2nd will be the secondary one. Signed-off-by: Guillaume Abrioux <gabrioux@redhat.com>
2018-10-25 04:27:28 +08:00
rgw_multisite: {toxinidir}/tests/functional/centos/7/rgw-multisite
rgw_multisite_container: {toxinidir}/tests/functional/centos/7/rgw-multisite-container
Add new container scenario Test with podman instead of docker and also support for python 3 only. Signed-off-by: Sébastien Han <seb@redhat.com>
2018-11-08 17:02:37 +08:00
container_podman: {toxinidir}/tests/functional/fedora/29/container-podman
Tests: Add bluestore tests Add two scenarios bluestore_journal_collocation and bluestore_cluster. Signed-off-by: Sébastien Han <seb@redhat.com>
2017-07-04 23:12:32 +08:00
tests: adds a tox.ini to run the functional tests This currently tests the initial-members scenario for both ansible 2.1 and ansible 2.2. It assumes a hosts file and vagrant_ssh_config exists in the scenario directory. Signed-off-by: Andrew Schoen <aschoen@redhat.com> Resolves: pytest#harness
2016-11-05 01:25:06 +08:00
commands=
tests: fix task in rhcs_setup that changes vagrant box to rhel7 Signed-off-by: Andrew Schoen <aschoen@redhat.com>
2017-03-23 01:38:12 +08:00
rhcs: ansible-playbook -vv -i "localhost," -c local {toxinidir}/tests/functional/rhcs_setup.yml --extra-vars "change_dir={changedir}" --tags "vagrant_setup"
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
dev: ansible-playbook -vv -i "localhost," -c local {toxinidir}/tests/functional/dev_setup.yml --extra-vars "change_dir={changedir} ceph_dev_branch={env:CEPH_DEV_BRANCH:master} ceph_dev_sha1={env:CEPH_DEV_SHA1:latest}" --tags "vagrant_setup"
tests: use the rhcs_setup.yml playbook in tox.ini Signed-off-by: Andrew Schoen <aschoen@redhat.com>
2017-03-22 23:14:41 +08:00
tests: provide a way use libvirt with vagrant and tox This allows for: tox -- --provider=libvirt Signed-off-by: Andrew Schoen <aschoen@redhat.com> Resolves: vagrant#boxes
2016-11-09 07:00:09 +08:00
vagrant up --no-provision {posargs:--provider=virtualbox}
tests: make the tox.ini config call the ssh config helper script Signed-off-by: Alfredo Deza <adeza@redhat.com> Resolves: pytest#harness
2016-11-05 02:01:28 +08:00
bash {toxinidir}/tests/scripts/generate_ssh_config.sh {changedir}
tests: adds a tox.ini to run the functional tests This currently tests the initial-members scenario for both ansible 2.1 and ansible 2.2. It assumes a hosts file and vagrant_ssh_config exists in the scenario directory. Signed-off-by: Andrew Schoen <aschoen@redhat.com> Resolves: pytest#harness
2016-11-05 01:25:06 +08:00
tox: change container image to use master We have a latest-master image which contains builds from upstream ceph so let's use it to verify build. Signed-off-by: Sébastien Han <seb@redhat.com>
2018-10-25 22:15:36 +08:00
# configure lvm
centos7_cluster: ansible-playbook -vv -i {changedir}/hosts {toxinidir}/tests/functional/lvm_setup.yml
docker_cluster: ansible-playbook -vv -i {changedir}/hosts {toxinidir}/tests/functional/lvm_setup.yml
docker_cluster_collocation: ansible-playbook -vv -i {changedir}/hosts {toxinidir}/tests/functional/lvm_setup.yml
tests: adds an lvm_osds testing scenario Signed-off-by: Andrew Schoen <aschoen@redhat.com>
2017-07-26 02:46:22 +08:00
lvm_osds: ansible-playbook -vv -i {changedir}/hosts {toxinidir}/tests/functional/lvm_setup.yml
ci: test lvm in containerized Signed-off-by: Sébastien Han <seb@redhat.com>
2018-07-13 02:30:59 +08:00
lvm_osds_container: ansible-playbook -vv -i {changedir}/hosts {toxinidir}/tests/functional/lvm_setup.yml
tests add the bluestore scenario in tox.ini Signed-off-by: Alfredo Deza <adeza@redhat.com>
2017-10-25 01:02:42 +08:00
bluestore_lvm_osds: ansible-playbook -vv -i {changedir}/hosts {toxinidir}/tests/functional/lvm_setup.yml
ceph_volume: refactor This commit does a couple of things: * Avoid code duplication * Clarify the code * add more unit tests * add myself to the author of the module Signed-off-by: Sébastien Han <seb@redhat.com>
2018-10-04 01:52:42 +08:00
bluestore_lvm_osds_container: ansible-playbook -vv -i {changedir}/hosts {toxinidir}/tests/functional/lvm_setup.yml
tox: change container image to use master We have a latest-master image which contains builds from upstream ceph so let's use it to verify build. Signed-off-by: Sébastien Han <seb@redhat.com>
2018-10-25 22:15:36 +08:00
shrink_osd: ansible-playbook -vv -i {changedir}/hosts {toxinidir}/tests/functional/lvm_setup.yml
shrink_osd_container: ansible-playbook -vv -i {changedir}/hosts {toxinidir}/tests/functional/lvm_setup.yml
tox: add lvm setup to shrink mon Fix shrink mon scenario by setting lvm so we can configure ceph-volume lvm osds. Signed-off-by: Sébastien Han <seb@redhat.com>
2018-11-14 00:54:14 +08:00
shrink_mon: ansible-playbook -vv -i {changedir}/hosts {toxinidir}/tests/functional/lvm_setup.yml
shrink_mon_container: ansible-playbook -vv -i {changedir}/hosts {toxinidir}/tests/functional/lvm_setup.yml
purge-cluster: adds support for purging lvm osds This also adds a new testing scenario for purging lvm osds Signed-off-by: Andrew Schoen <aschoen@redhat.com>
2017-08-23 22:12:40 +08:00
purge_lvm_osds: ansible-playbook -vv -i {changedir}/hosts {toxinidir}/tests/functional/lvm_setup.yml
tests: add purge_lvm_osds_container scenario This commits adds the purge_lvm_osds_container scenario. Signed-off-by: Guillaume Abrioux <gabrioux@redhat.com>
2018-11-30 18:25:25 +08:00
purge_lvm_osds_container: ansible-playbook -vv -i {changedir}/hosts {toxinidir}/tests/functional/lvm_setup.yml
tox: change container image to use master We have a latest-master image which contains builds from upstream ceph so let's use it to verify build. Signed-off-by: Sébastien Han <seb@redhat.com>
2018-10-25 22:15:36 +08:00
update_docker_cluster: ansible-playbook -vv -i {changedir}/hosts {toxinidir}/tests/functional/lvm_setup.yml
update_cluster: ansible-playbook -vv -i {changedir}/hosts {toxinidir}/tests/functional/lvm_setup.yml
purge_cluster_non_container: ansible-playbook -vv -i {changedir}/hosts {toxinidir}/tests/functional/lvm_setup.yml
purge_cluster_container: ansible-playbook -vv -i {changedir}/hosts {toxinidir}/tests/functional/lvm_setup.yml
switch_to_containers: ansible-playbook -vv -i {changedir}/hosts {toxinidir}/tests/functional/lvm_setup.yml
Add new container scenario Test with podman instead of docker and also support for python 3 only. Signed-off-by: Sébastien Han <seb@redhat.com>
2018-11-08 17:02:37 +08:00
container_podman: ansible-playbook -vv -i {changedir}/hosts {toxinidir}/tests/functional/lvm_setup.yml
container_podman: ansible-playbook -vv -i {changedir}/hosts {toxinidir}/tests/functional/simulate_rhel8.yml
tests: adds an lvm_osds testing scenario Signed-off-by: Andrew Schoen <aschoen@redhat.com>
2017-07-26 02:46:22 +08:00
tests: allow for insecure docker registries when testing rhcs Signed-off-by: Andrew Schoen <aschoen@redhat.com>
2017-05-03 04:49:50 +08:00
rhcs: ansible-playbook -vv -i {changedir}/hosts {toxinidir}/tests/functional/rhcs_setup.yml --extra-vars "ceph_docker_registry={env:CEPH_DOCKER_REGISTRY:docker.io} repo_url={env:REPO_URL:} rhel7_repo_url={env:RHEL7_REPO_URL:}" --skip-tags "vagrant_setup"
tests: use the rhcs_setup.yml playbook in tox.ini Signed-off-by: Andrew Schoen <aschoen@redhat.com>
2017-03-22 23:14:41 +08:00
tests: avoid yum failures In the CI we can see at many times failures like following: `Failure talking to yum: Cannot find a valid baseurl for repo: base/7/x86_64` It seems the fastest mirror detection is sometimes counterproductive and leads yum to fail. This fix has been added in the `setup.yml`. This playbook was used until now only just before playing `testinfra` and could be used before running ceph-ansible so we can add some provisionning tasks. Signed-off-by: Guillaume Abrioux <gabrioux@redhat.com> Co-authored-by: Erwan Velu <evelu@redhat.com>
2018-05-28 18:02:49 +08:00
ansible-playbook -vv -i {changedir}/hosts {toxinidir}/tests/functional/setup.yml
tests: switch to using key/value extra-vars instead of json I continue to have issues with extra-vars as json. The latest issue being that the ceph_docker_image_tag config option included in the json was being ignored. I can't find the root cause, by using the key/value format seems to work. I've also removed several options here to simply the interface. We can add those back if they become necessary. Signed-off-by: Andrew Schoen <aschoen@redhat.com>
2017-05-03 00:15:23 +08:00
ansible-playbook -vv -i {changedir}/hosts {toxinidir}/{env:PLAYBOOK:site.yml.sample} --extra-vars "\
common: make the delegate_facts feature optional Since we encountered issue with this on ansible2.2, this commit provide the ability to enable or disable it regarding which ansible we are running. Signed-off-by: Guillaume Abrioux <gabrioux@redhat.com>
2017-10-31 21:39:29 +08:00
delegate_facts_host={env:DELEGATE_FACTS_HOST:True} \
tests: switch to using key/value extra-vars instead of json I continue to have issues with extra-vars as json. The latest issue being that the ceph_docker_image_tag config option included in the json was being ignored. I can't find the root cause, by using the key/value format seems to work. I've also removed several options here to simply the interface. We can add those back if they become necessary. Signed-off-by: Andrew Schoen <aschoen@redhat.com>
2017-05-03 00:15:23 +08:00
fetch_directory={env:FETCH_DIRECTORY:{changedir}/fetch} \
tox: test mimic deployment Let's try to deploy mimic. Signed-off-by: Guillaume Abrioux <gabrioux@redhat.com> (cherry picked from commit d2cdfd830c339738b43e6a4417ca5d41fe416f86)
2018-07-06 16:57:32 +08:00
ceph_stable_release={env:CEPH_STABLE_RELEASE:mimic} \
tests: switch to using key/value extra-vars instead of json I continue to have issues with extra-vars as json. The latest issue being that the ceph_docker_image_tag config option included in the json was being ignored. I can't find the root cause, by using the key/value format seems to work. I've also removed several options here to simply the interface. We can add those back if they become necessary. Signed-off-by: Andrew Schoen <aschoen@redhat.com>
2017-05-03 00:15:23 +08:00
ceph_docker_registry={env:CEPH_DOCKER_REGISTRY:docker.io} \
ceph_docker_image={env:CEPH_DOCKER_IMAGE:ceph/daemon} \
tox: change container image to use master We have a latest-master image which contains builds from upstream ceph so let's use it to verify build. Signed-off-by: Sébastien Han <seb@redhat.com>
2018-10-25 22:15:36 +08:00
ceph_docker_image_tag={env:CEPH_DOCKER_IMAGE_TAG:latest-master} \
tests: run all existing tests with shaman repos If you use the 'dev' factor, the testing scenario will use repos from shaman.ceph.com. You can define CEPH_DEV_BRANCH and CEPH_DEV_SHA1 to specify which repo you'd like to test. Signed-off-by: Andrew Schoen <aschoen@redhat.com>
2017-07-17 23:26:48 +08:00
ceph_dev_branch={env:CEPH_DEV_BRANCH:master} \
ceph_dev_sha1={env:CEPH_DEV_SHA1:latest} \
test: do not always copy admin key The admin key must be copied on the osd nodes only when we test the shrink scenario. Shrink relies on ceph-disk commands that require the admin key on the node where it's being executed. Now we only copy the key when running on the shrink-osd scenario. Signed-off-by: Sébastien Han <seb@redhat.com>
2018-06-05 11:56:55 +08:00
copy_admin_key={env:COPY_ADMIN_KEY:False} \
tests: switch to using key/value extra-vars instead of json I continue to have issues with extra-vars as json. The latest issue being that the ceph_docker_image_tag config option included in the json was being ignored. I can't find the root cause, by using the key/value format seems to work. I've also removed several options here to simply the interface. We can add those back if they become necessary. Signed-off-by: Andrew Schoen <aschoen@redhat.com>
2017-05-03 00:15:23 +08:00
"
tests: convert extra-vars to use json This will prevent ansible from misreading any of these values. There were failures with xenial deployments because the value set for ``ceph_rhcs`` was being treated as a boolean True even though I'd set the value to false. This is because boolean values passed in with --extra-vars must use the json format. The formatting of the json is very important as you need a '\' to escape the starting and ending json to make tox happy. Also, each line needs to end with '\' if it's a multi-line command. Another thing to note is that if you want to use extra vars at the command line to respond to a vars_prompt it must be in key/value format. This is why we have a -e and a --extra-vars on the purge and update tests. Signed-off-by: Andrew Schoen <aschoen@redhat.com>
2017-03-16 19:16:09 +08:00
tests: reduce the amount of time we wait This sleep 120 looks a bit long, let's reduce this to 30sec and see if things go faster. Signed-off-by: Guillaume Abrioux <gabrioux@redhat.com>
2018-06-26 19:42:27 +08:00
# wait 30sec for services to be ready
sleep 30
tests: implement reboot after a deployment We don't test server reboot, a lot of things can happen after that. So now, we deploy, reboot then we run testinfra. Signed-off-by: Sébastien Han <seb@redhat.com>
2017-09-22 05:47:36 +08:00
# test cluster state using ceph-ansible tests
Revert "tests: add more verbosity in testinfra" This reverts commit 68eb850b27cd65571b9654fe7c1fd9c1f8435fdd. Signed-off-by: Guillaume Abrioux <gabrioux@redhat.com>
2018-06-20 22:52:38 +08:00
testinfra -n 8 --sudo -v --connection=ansible --ansible-inventory={changedir}/hosts {toxinidir}/tests/functional/tests
tests: implement reboot after a deployment We don't test server reboot, a lot of things can happen after that. So now, we deploy, reboot then we run testinfra. Signed-off-by: Sébastien Han <seb@redhat.com>
2017-09-22 05:47:36 +08:00
# reboot all vms
ci: reboot with ansible instead of vagrant reload vagrant is serialized and takes a lot of time compare to simple reboot. See the benchmarks below for 3 VMs: [leseb@rick docker]$ time ANSIBLE_SSH_ARGS="-F /home/leseb/reproduce-ci/tmp.zgGC7d5mIC/build/workspace/ceph-ansible/tests/functional/centos/7/docker/vagrant_ssh_config" ansible-playbook -i /home/leseb/reproduce-ci/tmp.zgGC7d5mIC/build/workspace/ceph-ansible/tests/functional/centos/7/docker/hosts reboot.yml PLAY [mons] **************************************************************************************************************************************************************************************************** TASK [Gathering Facts] ***************************************************************************************************************************************************************************************** ok: [mon1] ok: [mon2] ok: [mon0] TASK [restart machine] ***************************************************************************************************************************************************************************************** changed: [mon2] changed: [mon1] changed: [mon0] TASK [wait for server to boot] ********************************************************************************************************************************************************************************* ok: [mon2 -> localhost] ok: [mon0 -> localhost] ok: [mon1 -> localhost] TASK [uptime] ************************************************************************************************************************************************************************************************** changed: [mon2] changed: [mon0] changed: [mon1] PLAY RECAP ***************************************************************************************************************************************************************************************************** mon0 : ok=4 changed=2 unreachable=0 failed=0 mon1 : ok=4 changed=2 unreachable=0 failed=0 mon2 : ok=4 changed=2 unreachable=0 failed=0 real 0m35.112s user 0m5.737s sys 0m1.849s [leseb@rick docker]$ time vagrant reload ==> mon0: Halting domain... ==> mon0: Starting domain. ==> mon0: Waiting for domain to get an IP address... ==> mon0: Waiting for SSH to become available... ==> mon0: Creating shared folders metadata... ==> mon0: Rsyncing folder: /home/leseb/reproduce-ci/tmp.zgGC7d5mIC/build/workspace/ceph-ansible/tests/functional/centos/7/docker/ => /home/vagrant/sync ==> mon0: Machine already provisioned. Run `vagrant provision` or use the `--provision` ==> mon0: flag to force provisioning. Provisioners marked to run always will still run. ==> mon1: Halting domain... ==> mon1: Starting domain. ==> mon1: Waiting for domain to get an IP address... ==> mon1: Waiting for SSH to become available... ==> mon1: Creating shared folders metadata... ==> mon1: Rsyncing folder: /home/leseb/reproduce-ci/tmp.zgGC7d5mIC/build/workspace/ceph-ansible/tests/functional/centos/7/docker/ => /home/vagrant/sync ==> mon1: Machine already provisioned. Run `vagrant provision` or use the `--provision` ==> mon1: flag to force provisioning. Provisioners marked to run always will still run. ==> mon2: Halting domain... ==> mon2: Starting domain. ==> mon2: Waiting for domain to get an IP address... ==> mon2: Waiting for SSH to become available... ==> mon2: Creating shared folders metadata... ==> mon2: Rsyncing folder: /home/leseb/reproduce-ci/tmp.zgGC7d5mIC/build/workspace/ceph-ansible/tests/functional/centos/7/docker/ => /home/vagrant/sync ==> mon2: Machine already provisioned. Run `vagrant provision` or use the `--provision` ==> mon2: flag to force provisioning. Provisioners marked to run always will still run. real 1m31.850s user 0m7.387s sys 0m0.796s Reboot via Ansible: 0m35.112s Reboot via vagrant: 1m31.850s We save 1/3 time. Signed-off-by: Sébastien Han <seb@redhat.com>
2017-10-13 05:41:02 +08:00
ansible-playbook -vv -i {changedir}/hosts {toxinidir}/tests/functional/reboot.yml
tests: implement reboot after a deployment We don't test server reboot, a lot of things can happen after that. So now, we deploy, reboot then we run testinfra. Signed-off-by: Sébastien Han <seb@redhat.com>
2017-09-22 05:47:36 +08:00
tests: reduce the amount of time we wait This sleep 120 looks a bit long, let's reduce this to 30sec and see if things go faster. Signed-off-by: Guillaume Abrioux <gabrioux@redhat.com>
2018-06-26 19:42:27 +08:00
# wait 30sec for services to be ready
sleep 30
tests: implement reboot after a deployment We don't test server reboot, a lot of things can happen after that. So now, we deploy, reboot then we run testinfra. Signed-off-by: Sébastien Han <seb@redhat.com>
2017-09-22 05:47:36 +08:00
# retest to ensure cluster came back up correctly after rebooting
Revert "tests: add more verbosity in testinfra" This reverts commit 68eb850b27cd65571b9654fe7c1fd9c1f8435fdd. Signed-off-by: Guillaume Abrioux <gabrioux@redhat.com>
2018-06-20 22:52:38 +08:00
testinfra -n 8 --sudo -v --connection=ansible --ansible-inventory={changedir}/hosts {toxinidir}/tests/functional/tests
tests: adds a purge_cluster_collocated scenario This scenario brings up a 1 mon 1 osd cluster using journal collocation, purges the cluster and then verifies it can redeploy the cluster. Signed-off-by: Andrew Schoen <aschoen@redhat.com>
2016-12-23 04:13:08 +08:00
test: add handler support Add idempotency and handler test. Signed-off-by: Sébastien Han <seb@redhat.com>
2017-10-03 04:46:28 +08:00
# handlers/idempotency test
ansible-playbook -vv -i {changedir}/hosts {toxinidir}/{env:PLAYBOOK:site.yml.sample} \
--extra-vars "\
common: make the delegate_facts feature optional Since we encountered issue with this on ansible2.2, this commit provide the ability to enable or disable it regarding which ansible we are running. Signed-off-by: Guillaume Abrioux <gabrioux@redhat.com>
2017-10-31 21:39:29 +08:00
delegate_facts_host={env:DELEGATE_FACTS_HOST:True} \
test: add handler support Add idempotency and handler test. Signed-off-by: Sébastien Han <seb@redhat.com>
2017-10-03 04:46:28 +08:00
fetch_directory={env:FETCH_DIRECTORY:{changedir}/fetch} \
tox: test mimic deployment Let's try to deploy mimic. Signed-off-by: Guillaume Abrioux <gabrioux@redhat.com> (cherry picked from commit d2cdfd830c339738b43e6a4417ca5d41fe416f86)
2018-07-06 16:57:32 +08:00
ceph_stable_release={env:CEPH_STABLE_RELEASE:mimic} \
test: add handler support Add idempotency and handler test. Signed-off-by: Sébastien Han <seb@redhat.com>
2017-10-03 04:46:28 +08:00
ceph_docker_registry={env:CEPH_DOCKER_REGISTRY:docker.io} \
ceph_docker_image={env:CEPH_DOCKER_IMAGE:ceph/daemon} \
tox: change container image to use master We have a latest-master image which contains builds from upstream ceph so let's use it to verify build. Signed-off-by: Sébastien Han <seb@redhat.com>
2018-10-25 22:15:36 +08:00
ceph_docker_image_tag={env:CEPH_DOCKER_IMAGE_TAG_BIS:latest-master} # not ideal but what can we do? \
test: add handler support Add idempotency and handler test. Signed-off-by: Sébastien Han <seb@redhat.com>
2017-10-03 04:46:28 +08:00
ceph_dev_branch={env:CEPH_DEV_BRANCH:master} \
test: do not always copy admin key The admin key must be copied on the osd nodes only when we test the shrink scenario. Shrink relies on ceph-disk commands that require the admin key on the node where it's being executed. Now we only copy the key when running on the shrink-osd scenario. Signed-off-by: Sébastien Han <seb@redhat.com>
2018-06-05 11:56:55 +08:00
ceph_dev_sha1={env:CEPH_DEV_SHA1:latest} \
copy_admin_key={env:COPY_ADMIN_KEY:False} " \
test: add handler support Add idempotency and handler test. Signed-off-by: Sébastien Han <seb@redhat.com>
2017-10-03 04:46:28 +08:00
--extra-vars @ceph-override.json
tests: split purge_cluster, followup on a53aa9e - split purge_cluster because we need to test filestore and bluestore scenarios. - clean some leftover. Signed-off-by: Guillaume Abrioux <gabrioux@redhat.com>
2017-10-20 23:18:39 +08:00
purge_cluster_non_container: {[purge]commands}
purge_cluster_container: {[purge]commands}
purge_filestore_osds_non_container: {[purge]commands}
purge_bluestore_osds_non_container: {[purge]commands}
purge_filestore_osds_container: {[purge]commands}
purge_bluestore_osds_container: {[purge]commands}
purge-cluster: adds support for purging lvm osds This also adds a new testing scenario for purging lvm osds Signed-off-by: Andrew Schoen <aschoen@redhat.com>
2017-08-23 22:12:40 +08:00
purge_lvm_osds: {[purge-lvm]commands}
tests: add purge_lvm_osds_container scenario This commits adds the purge_lvm_osds_container scenario. Signed-off-by: Guillaume Abrioux <gabrioux@redhat.com>
2018-11-30 18:25:25 +08:00
purge_lvm_osds_container: {[purge-lvm]commands}
switch-from-non-containerized-to-containerized: mask unit files We must mask the image so we are sure that even if the system reboots then the OSDs won't start. Also remove Ceph udev rules if found on the system prior to deploy containers. If we don't do this we are exposed to conflicts between udev rules and sytemd unit files. Also add the CI will now test the migration from a non-containerized cluster to a containerized cluster. Signed-off-by: Sébastien Han <seb@redhat.com>
2017-08-25 20:36:07 +08:00
switch_to_containers: {[switch-to-containers]commands}
tests: adds an update_cluster testing scenario This updates the centos 7 cluster scenario from jewel to kraken using the rolling_update playbook. Signed-off-by: Andrew Schoen <aschoen@redhat.com>
2017-03-08 04:05:03 +08:00
update_cluster: {[update]commands}
tests: adds *-update_docker_cluster testing scenarios Signed-off-by: Andrew Schoen <aschoen@redhat.com>
2017-06-06 22:43:14 +08:00
update_docker_cluster: {[update]commands}
shrink mon and osd Rework shrinking a monitor and an OSD playbook. Also adding test scenario. Closes: https://bugzilla.redhat.com/show_bug.cgi?id=1366807 Signed-off-by: Sébastien Han <seb@redhat.com>
2017-08-31 06:07:28 +08:00
shrink_mon: {[shrink-mon]commands}
shrink: support for container We can now shrink mon and osds on containerized deployment. Closes: https://bugzilla.redhat.com/show_bug.cgi?id=1492115 Signed-off-by: Sébastien Han <seb@redhat.com>
2017-09-18 23:45:08 +08:00
shrink_mon_container: {[shrink-mon]commands}
shrink mon and osd Rework shrinking a monitor and an OSD playbook. Also adding test scenario. Closes: https://bugzilla.redhat.com/show_bug.cgi?id=1366807 Signed-off-by: Sébastien Han <seb@redhat.com>
2017-08-31 06:07:28 +08:00
shrink_osd: {[shrink-osd]commands}
shrink: support for container We can now shrink mon and osds on containerized deployment. Closes: https://bugzilla.redhat.com/show_bug.cgi?id=1492115 Signed-off-by: Sébastien Han <seb@redhat.com>
2017-09-18 23:45:08 +08:00
shrink_osd_container: {[shrink-osd]commands}
tests: add tests for day-2-operation playbook Adding testing scenarios for day-2-operation playbook. Steps: - deploys a cluster, - run testinfra, - test idempotency, - add a new osd node, - run testinfra Signed-off-by: Guillaume Abrioux <gabrioux@redhat.com>
2018-10-16 23:05:10 +08:00
add_osds: {[add-osds]commands}
add_osds_container: {[add-osds]commands}
rgw: add testing scenario for rgw multisite This will setup 2 cluster with rgw multisite enabled. First cluster will act as the 'master', the 2nd will be the secondary one. Signed-off-by: Guillaume Abrioux <gabrioux@redhat.com>
2018-10-25 04:27:28 +08:00
rgw_multisite: {[rgw-multisite]commands}
rgw_multisite_container: {[rgw-multisite]commands}
tests: adds purge_cluster and purge_dmcrypt scenarios This also removes the purge_cluster_collocated scenario as it's not needed now because of purge_cluster. Moving all the purge commands into its own section allows for ease of reuse when creating new purge scenarios. Signed-off-by: Andrew Schoen <aschoen@redhat.com>
2017-01-27 00:38:10 +08:00
tests: make the tox.ini config call the ssh config helper script Signed-off-by: Alfredo Deza <adeza@redhat.com> Resolves: pytest#harness
2016-11-05 02:01:28 +08:00
vagrant destroy --force