You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
- Add performance tuning configuration (thanks @t0k4rt)
- Set raft multiplier to 1
- Conditionally install Python dependency baed on virtualenv or --user
Addresses #129 (comment)
- Update includes to import_tasks and include_tasks
- Remove invalid consul_version key from configuration
- Update Vagrantfile
- Set client address to 0.0.0.0 so Vagrant based deploy checks now pass
- Update documentation
- [Node leave drain time](https://www.consul.io/docs/agent/options.html#leave_drain_time) is the dwell time for a server to honor requests while gracefully leaving
683
+
684
+
- Default value: 5s
685
+
686
+
#### `rpc_hold_timeout`
687
+
688
+
- [RPC hold timeout](https://www.consul.io/docs/agent/options.html#rpc_hold_timeout) is the duration that a client or server will retry internal RPC requests during leader elections
689
+
- Default value: 7s
690
+
670
691
## Dependencies
671
692
672
693
Ansible requires GNU tar and this role performs some local use of the
@@ -813,21 +834,6 @@ consul3.node.consul. 0 IN A 10.1.42.230
813
834
- Custom list of addresses to listen on.
814
835
- Default value: *[]*
815
836
816
-
### `consul_performance`
817
-
818
-
This is a nested object of Consul performance related options.
819
-
820
-
#### `consul_performance.raft_multiplier`
821
-
822
-
This is the [raft multiplier](https://www.consul.io/docs/agent/options.html#raft_multiplier). See also [Server Performance](https://www.consul.io/docs/guides/performance.html).
823
-
824
-
#### `consul_performance.leave_drain_time`
825
-
826
-
This is the [leave drain time](https://www.consul.io/docs/agent/options.html#leave_drain_time).
827
-
828
-
#### `consul_performance.rpc_hold_timeout`
829
-
830
-
This is the [RPC hold timeout](https://www.consul.io/docs/agent/options.html#rpc_hold_timeout).
Copy file name to clipboardExpand all lines: examples/README_VAGRANT.md
+10-29Lines changed: 10 additions & 29 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -1,55 +1,38 @@
1
1
# Consul with Ansible
2
2
3
-
This project provides documentation and a collection of scripts to help you
4
-
automate the deployment of Consul using
5
-
[Ansible](https://www.ansible.com/). These are the instructions for
6
-
deploying a development cluster on Vagrant and VirtualBox.
3
+
This project provides documentation and a collection of scripts to help you automate the deployment of Consul using [Ansible](https://www.ansible.com/). These are the instructions for deploying a development cluster on Vagrant and VirtualBox.
7
4
8
-
The documentation and scripts are merely a starting point designed to both
9
-
help familiarize you with the processes and quickly bootstrap an environment
10
-
for development. You may wish to expand on them and customize
11
-
them with additional features specific to your needs later.
5
+
The documentation and scripts are merely a starting point designed to both help familiarize you with the processes and quickly bootstrap an environment for development. You may wish to expand on them and customize them with additional features specific to your needs later.
12
6
13
7
If you are looking for the main role documentation, it is in the [README.md](https://github.com/brianshumate/ansible-consul/blob/master/README.md).
14
8
15
9
## Vagrant Development Cluster
16
10
17
-
In some situations deploying a small cluster on your local development
18
-
machine can be handy. This document describes such a scenario using the
19
-
following technologies:
11
+
In some situations deploying a small cluster on your local development machine can be handy. This document describes such a scenario using the following technologies:
20
12
21
13
*[Consul](https://consul.io)
22
14
*[VirtualBox](https://www.virtualbox.org/)
23
15
*[Vagrant](http://www.vagrantup.com/) with Ansible provisioner and
24
16
supporting plugin
25
17
*[Ansible](https://www.ansible.com/)
26
18
27
-
Each of the virtual machines for this guide are configured with
28
-
1GB RAM, 2 CPU cores, and 2 network interfaces. The first interface uses
29
-
NAT and has connection via the host to the outside world. The second
30
-
interface is a private network and is used for Consul intra-cluster
31
-
communication in addition to access from the host machine.
19
+
Each of the virtual machines for this guide are configured with 1GB RAM, 2 CPU cores, and 2 network interfaces. The first interface uses NAT and has connection via the host to the outside world. The second interface is a private network and is used for Consul intra-cluster communication in addition to access from the host machine.
32
20
33
-
The Vagrant configuration file (`Vagrantfile`) is responsible for
34
-
configuring the virtual machines and a baseline OS installation.
21
+
The Vagrant configuration file (`Vagrantfile`) is responsible for configuring the virtual machines and a baseline OS installation.
35
22
36
-
The Ansible playbooks then further refine OS configuration, perform Consul
37
-
software download, installation, configuration, and the joining of server nodes into a ready to use cluster.
23
+
The Ansible playbooks then further refine OS configuration, perform Consul software download, installation, configuration, and the joining of server nodes into a ready to use cluster.
38
24
39
25
## Designed for Ansible Galaxy
40
26
41
-
This role is designed to be installed via the `ansible-galaxy` command
42
-
instead of being directly run from the git repository.
27
+
This role is designed to be installed via the `ansible-galaxy` command instead of being directly run from the git repository.
43
28
44
29
You should install it like this:
45
30
46
31
```
47
32
ansible-galaxy install brianshumate.consul
48
33
```
49
34
50
-
You'll want to make sure you have write access to `/etc/ansible/roles/` since
51
-
that is where the role will be installed by default, or define your own
52
-
Ansible role path by creating a `$HOME/.ansible.cfg` or even `./anisible.cfg`
35
+
You'll want to make sure you have write access to `/etc/ansible/roles/` since that is where the role will be installed by default, or define your own Ansible role path by creating a `$HOME/.ansible.cfg` or even `./anisible.cfg`
53
36
file with these contents:
54
37
55
38
```
@@ -61,8 +44,7 @@ Change `PATH_TO_ROLES` to a directory that you have write access to.
61
44
62
45
## Quick Start
63
46
64
-
Begin from the top level directory of this project and use the following
65
-
steps to get up and running:
47
+
Begin from the top level directory of this project and use the following steps to get up and running:
66
48
67
49
1. Install [VirtualBox](https://www.virtualbox.org/wiki/Downloads), [Vagrant](http://downloads.vagrantup.com/), [vagrant-hosts](https://github.com/adrienthebo/vagrant-hosts), and [Ansible](http://docs.ansible.com/ansible/intro_installation.html).
68
50
2. Edit `/etc/hosts` or use the included `bin/preinstall` script to add
@@ -113,8 +95,7 @@ BOX_NAME=freebsd/FreeBSD-11.0-STABLE CONSUL_IFACE=em1 vagrant up
113
95
* VirtualBox version 5.1.30
114
96
* Vagrant version 2.0.1
115
97
* Vagrant Hosts plugin version 2.8.0
116
-
2. This project uses Debian 8 (Jessie) by default, but you can choose another
117
-
OS distribution with the *BOX_NAME* environment variable
98
+
2. This project uses Debian 9 (Stretch) by default, but you can choose another OS distribution with the *BOX_NAME* environment variable
118
99
3. The `bin/preinstall` shell script performs the following actions for you:
119
100
* Adds each node's host information to the host machine's `/etc/hosts`
0 commit comments