diff --git a/contrib/network-storage/glusterfs/roles/glusterfs/README.md b/contrib/network-storage/glusterfs/roles/glusterfs/README.md index 1d0adff8bdf5b4fc1cdabf5c067d213fdb146fbf..fd80004c03a3bb56931a4b13e7191e9a225b8a01 100644 --- a/contrib/network-storage/glusterfs/roles/glusterfs/README.md +++ b/contrib/network-storage/glusterfs/roles/glusterfs/README.md @@ -8,7 +8,7 @@ Installs and configures GlusterFS on Linux. For GlusterFS to connect between servers, TCP ports `24007`, `24008`, and `24009`/`49152`+ (that port, plus an additional incremented port for each additional server in the cluster; the latter if GlusterFS is version 3.4+), and TCP/UDP port `111` must be open. You can open these using whatever firewall you wish (this can easily be configured using the `geerlingguy.firewall` role). -This role performs basic installation and setup of Gluster, but it does not configure or mount bricks (volumes), since that step is easier to do in a series of plays in your own playbook. Ansible 1.9+ includes the [`gluster_volume`](https://docs.ansible.com/gluster_volume_module.html) module to ease the management of Gluster volumes. +This role performs basic installation and setup of Gluster, but it does not configure or mount bricks (volumes), since that step is easier to do in a series of plays in your own playbook. Ansible 1.9+ includes the [`gluster_volume`](https://docs.ansible.com/ansible/latest/collections/gluster/gluster/gluster_volume_module.html) module to ease the management of Gluster volumes. ## Role Variables diff --git a/docs/ansible.md b/docs/ansible.md index 202a793332e2dd05e194a46922a234d1f10de65a..99d72b4dc11112d75be49095c843eeb0146a894f 100644 --- a/docs/ansible.md +++ b/docs/ansible.md @@ -68,7 +68,7 @@ Optional variables are located in the `inventory/sample/group_vars/all.yml`. Mandatory variables that are common for at least one role (or a node group) can be found in the `inventory/sample/group_vars/k8s-cluster.yml`. There are also role vars for docker, kubernetes preinstall and master roles. -According to the [ansible docs](https://docs.ansible.com/ansible/playbooks_variables.html#variable-precedence-where-should-i-put-a-variable), +According to the [ansible docs](https://docs.ansible.com/ansible/latest/playbooks_variables.html#variable-precedence-where-should-i-put-a-variable), those cannot be overridden from the group vars. In order to override, one should use the `-e` runtime flags (most simple way) or other layers described in the docs. diff --git a/docs/large-deployments.md b/docs/large-deployments.md index 130bcf0e79eca8cdd18180dc31409e9154e1e311..ec6618bf40e84db5a89d5989eb26f5d14fa89f00 100644 --- a/docs/large-deployments.md +++ b/docs/large-deployments.md @@ -3,7 +3,7 @@ Large deployments of K8s For a large scaled deployments, consider the following configuration changes: -* Tune [ansible settings](https://docs.ansible.com/ansible/intro_configuration.html) +* Tune [ansible settings](https://docs.ansible.com/ansible/latest/intro_configuration.html) for `forks` and `timeout` vars to fit large numbers of nodes being deployed. * Override containers' `foo_image_repo` vars to point to intranet registry. diff --git a/docs/vars.md b/docs/vars.md index 784cb30b3466d89aee42007cc98171a934c364d6..8e6218fad802873a4520eb107b7b82e463df4ad1 100644 --- a/docs/vars.md +++ b/docs/vars.md @@ -3,7 +3,7 @@ ## Generic Ansible variables You can view facts gathered by Ansible automatically -[here](https://docs.ansible.com/ansible/playbooks_variables.html#information-discovered-from-systems-facts). +[here](https://docs.ansible.com/ansible/latest/playbooks_variables.html#information-discovered-from-systems-facts). Some variables of note include: