-
Notifications
You must be signed in to change notification settings - Fork 139
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
zookeeper_url split into two vars, Easy to change the download address #1
Open
cifaz
wants to merge
100
commits into
kpx-dev:master
Choose a base branch
from
AnsibleShipyard:master
base: master
Could not load branches
Branch not found: {{ refName }}
Loading
Could not load tags
Nothing to show
Loading
Are you sure you want to change the base?
Some commits from the old base branch may be removed from the timeline,
and old review comments may become outdated.
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Supporting RHEL 6 systems
Add Docker and update CI
Add multi-docker support
Zookeeper service had state=restarted which cause that every time when playbook were run, Zookeeper restart. Added restart handler added notifications to all config files and changed state to "started".
Removed unneeded Zookeeper restart on every run
Ansible were restarting Zookeeper every time Ansible were running. Fixed service state=started and added restart handlers to restart only if configuration changes.
Fixed Zookeeper to restart every time Ansible runs on Debian
Support distro with systemd.
It's time to update the version and given that the playbook has been around I believe a v0.9.0 is in order.
Update version
Builds will fail if using 3.4.6 for the version because Apache removes old versions from their mirrors for some ungodly reason.
Bump default zookeeper_version to 3.4.7
Bump playbook version to 0.9.1
Bump playbook version to 0.9.1
Apache has removed ZK 3.4.7 from their mirrors, causing builds to fail again. I followed up in #zookeeper to see why these releases keep disappearing from the mirrors, so hopefully we'll get some answers as to how to prevent this going forward.
Back to version 3.4.6
BYPASS - Update version
…ervice_enabled_for_redhat Make zookeeper service enabled for RedHat
…riables Remove unused variables
…o_3_4_9 Bump zookeeper to 3.4.9
Ignore IDEA files.
Removing sudo from upstart script.
Adding S3 support.
The latest Zookeeper version 3.5.3-beta is distributed as plain tar archive, so `tar zxf` fails with `gzip: stdin: not in gzip format`. Also, recent versions of tar recognize format by itself, so there is no need in 'z' option.
Currently, when running ansible-zookeeper role on Debian 8 host, it fails: TASK [AnsibleShipyard.ansible-zookeeper : Enable zookeeper service] *************************************************** fatal: [debian8-host]: FAILED! => {"changed": false, "failed": true, "msg": "Could not find the requested service zookeeper: host"} This happens because `zookeeper_debian_systemd_enabled` variable is enabled only for Ubuntu >= 15.04 hosts. This PR adds check for Debian >= 8.0, so Zookeeper successfully installs on Debian 8.0
Enable systemd service for Debian 8
Remove 'z' from untar command
…cker_version_constraint Remove .travis specific docker version constraint
…ersion_to_3_4_11 Bump zookeper version to 3.4.11
In order to avoid name-resolution and connectivity issues to other cluster nodes, make sure ZK only starts up after the network has started up properly.
* Extracted hardcoded zookeeper ports into vars * Set proper variable for test
replace the hard coded /var/log/zookeeper with {{log_dir}} variable
Update zookeeper.conf.j2
…entCnxns into zoo.cfg template
max_client_connections ->maxClientCnxns
Customize own hostname with a new variable
Require ansible 2.4
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
zookeeper_url split into two vars, Easy to change the download address