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/ansible.cfg

42 lines
1.4 KiB
INI
Raw Normal View History

ansible: add a note in ansible.cfg Comments inside this file must be set BEFORE the option. NOT after the option, otherwise the comment will be interpreted as a value to that option. Signed-off-by: Sébastien Han <seb@redhat.com>
2017-05-16 20:42:39 +08:00
# Comments inside this file must be set BEFORE the option.
# NOT after the option, otherwise the comment will be interpreted as a value to that option.
Use Vagrant's Ansible provisioner Use Vagrant's built-in support for Ansible provisioner. This eliminates the need for a hosts file, and simplifies the ansible config file. Renames config from .ansible.cfg to ansible.cfg since Ansible expects the file to be called ansible.cfg and be adjacent to Vagrantfile when using the Vagrant provisioner.
2014-05-11 09:52:26 +08:00
[defaults]
Remove ansible managed header from ceph.conf Fixes: #125 Signed-off-by: Sébastien Han <sebastien.han@enovance.com>
2014-10-10 21:41:31 +08:00
ansible_managed = Please do not change this file directly since it is managed by Ansible and will be overwritten
ansible.cfg: Add library path to configuration Ceph module path needs to be configured if we want to avoid issues like: no action detected in task. This often indicates a misspelled module name, or incorrect module path Currently the ansible-lint command in Travis CI complains about that. Signed-off-by: Dimitri Savineau <dsavinea@redhat.com>
2019-02-19 00:38:35 +08:00
library = ./library
Using config_template Thanks to @cloudnull great patch at https://github.com/ansible/ansible/pull/12555 we now have the ability to add more configuration options instead of having to push a PR to add a new option to the template. So you can dynamically add and remove flags. To use it, edit `ceph_conf_overrides` in `group_vars/all` like so: ``` ceph_conf_overrides global: foo: 12345 bar: 6789 ``` Signed-off-by: Sébastien Han <seb@redhat.com>
2015-12-16 23:11:14 +08:00
action_plugins = 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
callback_plugins = plugins/callback
Replace ipaddr() with ips_in_ranges() This change implements a filter_plugin that is used in the ceph-facts, ceph-validate roles and infrastucture-playbooks. The new filter plugin will return a list of all IP address that reside in any one of the given IP ranges. The new filter replaces the use of the ipaddr filter. ceph.conf already support a comma separated list of CIDRs for the public_network and cluster_network options. Changes: [1] and [2] introduced a regression in ceph-ansible where public_network can no longer be a comma separated list of cidrs. With this change a comma separated list of subnet CIDRs can also be used for monitor_address_block and radosgw_address_block. [1] commit: d67230b2a26b40651c1c1dbee68a92b0e851f3d5 [2] commit: 20e4852888ecc76d8d0fa194a438fa2a90e1cde3 Related-To: https://bugs.launchpad.net/tripleo/+bug/1840030 Related-To: https://bugzilla.redhat.com/show_bug.cgi?id=1740283 Closes: #4333 Please backport to stable-4.0 Signed-off-by: Harald Jensås <hjensas@redhat.com> (cherry picked from commit e695efcaf79909e2237197fd473117930e8d83e5)
2019-08-15 01:14:09 +08:00
filter_plugins = plugins/filter
Update for infrastructure-playbooks execution - Updates to allow running infrastructure-playbooks both from within its directory or root directory of ceph-ansible. Signed-off-by: Ivan Font <ifont@redhat.com>
2016-10-26 00:27:49 +08:00
roles_path = ./roles
ansible: add logging path Ability to log ansible plays in a log file. Default location is /var/log/ansible.log Be sure the user running Ansible has permissions on the logfile. Fixes: https://bugzilla.redhat.com/show_bug.cgi?id=1445065 Signed-off-by: Sébastien Han <seb@redhat.com>
2017-04-25 16:10:09 +08:00
# Be sure the user running Ansible has permissions on the logfile
ansible.cfg: change log_path to directory used by fact_caching_connection Since fact_caching_connection uses a directory in $HOME already, write the ansible.log to the same directory. Fixes: #3509 Signed-off-by: Patrick C. F. Ernzer <pcfe@redhat.com>
2019-01-17 06:40:27 +08:00
log_path = $HOME/ansible/ansible.log
ansible: shorten default control_path Default ansible control_path option is too long, so we shorten it by changing the ansible.cfg file. For more info see: https://github.com/ansible/ansible/issues/11536 Fixes: https://bugzilla.redhat.com/show_bug.cgi?id=1447569 Signed-off-by: Sébastien Han <seb@redhat.com>
2017-05-11 14:57:53 +08:00
test: use yaml stdout callback This provides a much more readable output for tasks. It'll be easier to debug traces. Signed-off-by: Sébastien Han <seb@redhat.com>
2018-12-14 18:14:30 +08:00
forks = 20
Tune ansible.cfg Based on the OpenShift one: https://docs.openshift.com/container-platform/3.7/scaling_performance/install_practices.html#scaling-performance-install-optimization * Increases number of forks. * Disables host_key_checking * Smart gathering facts * Fact caching jsonfile * Enables profile_tasks callback * Mutliplexes ssh connections (ControlMaster) * Enables pipelining
2018-03-08 23:54:43 +08:00
host_key_checking = False
gathering = smart
fact_caching = jsonfile
fact_caching_connection = $HOME/ansible/facts
ansible: increase fact cache timeout 10m seems a bit low, indeed, a complete run can take more than 1h. Let's increase it to 2h Signed-off-by: Guillaume Abrioux <gabrioux@redhat.com>
2019-02-06 15:32:04 +08:00
fact_caching_timeout = 7200
Tune ansible.cfg Based on the OpenShift one: https://docs.openshift.com/container-platform/3.7/scaling_performance/install_practices.html#scaling-performance-install-optimization * Increases number of forks. * Disables host_key_checking * Smart gathering facts * Fact caching jsonfile * Enables profile_tasks callback * Mutliplexes ssh connections (ControlMaster) * Enables pipelining
2018-03-08 23:54:43 +08:00
nocows = 1
whitelist->allowlist https://github.com/tox-dev/tox/blob/master/docs/changelog.rst#v3180-2020-07-23 Signed-off-by: David Galloway <dgallowa@redhat.com>
2022-05-25 02:43:05 +08:00
callback_allowlist = profile_tasks
test: use yaml stdout callback This provides a much more readable output for tasks. It'll be easier to debug traces. Signed-off-by: Sébastien Han <seb@redhat.com>
2018-12-14 18:14:30 +08:00
stdout_callback = yaml
ansible.cfg: set force_valid_group_names param As of 2.10, group names containing a dash are invalid. However, setting this option makes it still possible to use a dash in group names and prevent this warning to show up. It might need to be definitely addressed in a future ansible release. Closes: https://bugzilla.redhat.com/show_bug.cgi?id=1880476 Signed-off-by: Guillaume Abrioux <gabrioux@redhat.com> (cherry picked from commit 6938ed13021201cc1cfcd3f3087849fed3157a69)
2020-09-24 09:51:56 +08:00
force_valid_group_names = ignore
Disable facts by default in ansible.cfg As a continuation of a7f2fa73e63e69dba2e41aaac9732397eec437c9, this change switches fact injection to off by default in the provided ansible.cfg. Signed-off-by: Alex Schultz <aschultz@redhat.com> (cherry picked from commit db031a4993480ca987011630fa716f7e2ccda976)
2021-03-11 23:43:53 +08:00
inject_facts_as_vars = False
Tune ansible.cfg Based on the OpenShift one: https://docs.openshift.com/container-platform/3.7/scaling_performance/install_practices.html#scaling-performance-install-optimization * Increases number of forks. * Disables host_key_checking * Smart gathering facts * Fact caching jsonfile * Enables profile_tasks callback * Mutliplexes ssh connections (ControlMaster) * Enables pipelining
2018-03-08 23:54:43 +08:00
ansible: disable retry files Closes: https://github.com/ceph/ceph-ansible/issues/1611 Signed-off-by: Sébastien Han <seb@redhat.com>
2017-06-22 21:55:19 +08:00
# Disable them in the context of https://review.openstack.org/#/c/469644
retry_files_enabled = False
ansible.cfg: increase ssh timeout CI slaves are slow so by setting a higher value we can avoid the following error: Timeout (12s) waiting for privilege escalation prompt: Now we wait for 32 sec... More info here: https://github.com/ansible/ansible/issues/14426 Signed-off-by: Sébastien Han <seb@redhat.com>
2017-09-06 17:25:47 +08:00
# This is the default SSH timeout to use on connection attempts
# CI slaves are slow so by setting a higher value we can avoid the following error:
# Timeout (12s) waiting for privilege escalation prompt:
tests: increase ssh timeout and retries in ansible.cfg We see quite a few failures in the CI related to testing nodes losing ssh connection. This modification allows ansible to retry more times and wait longer before timing out. This seems to really affect testing scenarios that use a large amount of testing nodes. The centos7_cluster scenario specifically has 12 nodes and suffered from these failures often. Signed-off-by: Andrew Schoen <aschoen@redhat.com>
2018-06-07 03:59:47 +08:00
timeout = 60
ansible.cfg: increase ssh timeout CI slaves are slow so by setting a higher value we can avoid the following error: Timeout (12s) waiting for privilege escalation prompt: Now we wait for 32 sec... More info here: https://github.com/ansible/ansible/issues/14426 Signed-off-by: Sébastien Han <seb@redhat.com>
2017-09-06 17:25:47 +08:00
ansible: shorten default control_path Default ansible control_path option is too long, so we shorten it by changing the ansible.cfg file. For more info see: https://github.com/ansible/ansible/issues/11536 Fixes: https://bugzilla.redhat.com/show_bug.cgi?id=1447569 Signed-off-by: Sébastien Han <seb@redhat.com>
2017-05-11 14:57:53 +08:00
[ssh_connection]
ansible: fix control path line If the comment is put after the line then it is interpreted so we need to move it before and have a dedicated line. Signed-off-by: Sébastien Han <seb@redhat.com>
2017-05-16 20:39:03 +08:00
# see: https://github.com/ansible/ansible/issues/11536
keep port as part of the control path On a Vagrant setup, every host is 127.0.0.1 and every user is vagrant. To not have ansible do the same stuff on the same machine (the one we connected first), we should keep the port as part of the control path. Also this helps in setups where different hosts might be hidden behind the same IP, but on different ports (e.g. using DNAT).
2017-05-31 00:25:29 +08:00
control_path = %(directory)s/%%h-%%r-%%p
ansible.cfg: do not enforce PreferredAuthentications There's no need to enforce PreferredAuthentications by default. Users can still choose to override the ansible.cfg with any additional parameter like this one to fit their infrastructure. Fixes: #4826 Signed-off-by: Guillaume Abrioux <gabrioux@redhat.com> (cherry picked from commit d682412e2aa5eeb411cc0dff9a3ffef4b4aa8683)
2019-12-10 00:10:11 +08:00
ssh_args = -o ControlMaster=auto -o ControlPersist=600s
test: use yaml stdout callback This provides a much more readable output for tasks. It'll be easier to debug traces. Signed-off-by: Sébastien Han <seb@redhat.com>
2018-12-14 18:14:30 +08:00
pipelining = True
ansible: set ssh retry option to 5 We noticed that sometime, ceph-ansible can fail with error : `Failed to connect to the host via ssh:` It can occurs after the task `restart firewalld` has been played. Setting `retries` to 5 should prevent from unexcepted ssh failure. Signed-off-by: Guillaume Abrioux <gabrioux@redhat.com>
2018-01-23 21:38:35 +08:00
# Option to retry failed ssh executions if the failure is encountered in ssh itself
tests: increase ssh timeout and retries in ansible.cfg We see quite a few failures in the CI related to testing nodes losing ssh connection. This modification allows ansible to retry more times and wait longer before timing out. This seems to really affect testing scenarios that use a large amount of testing nodes. The centos7_cluster scenario specifically has 12 nodes and suffered from these failures often. Signed-off-by: Andrew Schoen <aschoen@redhat.com>
2018-06-07 03:59:47 +08:00
retries = 10