Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Role idempotency, lots of small changes #250 #1

Merged
merged 18 commits into from
Jan 11, 2022

Conversation

rslllstefan
Copy link
Owner

marcobellaccini and others added 18 commits January 14, 2019 14:28
…stemd unit files for Debian/Ubuntu (tested on Ubuntu 20.04).

For systemd based services the PIDfile directory will not be created anymore, it will be created automatically by systemd via the 'RuntimeDirectory' setting.
Added a couple of configuration settings to the systemd unit file which were copied from the unit file which is installed on Ubuntu via the official repository (which is currently at major version 5 of redis, maybe other settings might be better for version 6 - nevertheless the service seems to work).
…updated checksums' (PR 202) from https://github.com/marcobellaccini/ansible-redis

# Conflicts:
#	.travis.yml
#	README.md
#	meta/main.yml
#	tasks/dependencies.yml
#	tasks/install.yml
#	tasks/sentinel.yml
#	tasks/server.yml
#	vars/main.yml
- Configuration creation and updates are handled via lineinfile such that we do not interfere with changes written by the server/sentinel processes. Additionally master/replica information is sourced dynamically (see runtime_facts.yml) such that we don't force role changes when re-running the playbook.
- Added support for "sentinel announce-ip" option (setting "redis_sentinel_announce_ip" to true will result in the "ansible_default_ipv4.address" being used.
- Installing a different redis version will lead to a rolling restart of all servers/sentinels.
- Minimal support for removing nodes (see README.md)
@rslllstefan rslllstefan merged commit 8f9f4f4 into rslllstefan:master_rs Jan 11, 2022
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

3 participants