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
Any pre-requisites that may not be covered by Ansible itself or the role should be mentioned here. For instance, if the role uses the EC2 module, it may be a good idea to mention in this section that the boto package is required.
10
+
11
+
Role Variables
12
+
--------------
13
+
14
+
A description of the settable variables for this role should go here, including any variables that are in defaults/main.yml, vars/main.yml, and any variables that can/should be set via parameters to the role. Any variables that are read from other roles and/or the global scope (ie. hostvars, group vars, etc.) should be mentioned here as well.
15
+
16
+
Dependencies
17
+
------------
18
+
19
+
A list of other roles hosted on Galaxy should go here, plus any details in regards to parameters that may need to be set for other roles, or variables that are used from other roles.
20
+
21
+
Example Playbook
22
+
----------------
23
+
24
+
Including an example of how to use your role (for instance, with variables passed in as parameters) is always nice for users too:
25
+
26
+
- hosts: servers
27
+
roles:
28
+
- { role: username.rolename, x: 42 }
29
+
30
+
License
31
+
-------
32
+
33
+
BSD
34
+
35
+
Author Information
36
+
------------------
37
+
38
+
An optional section for the role authors to include contact information, or a website (HTML is not allowed).
replace_node - Replace gluster node with a new node.
5
+
6
+
Requirements
7
+
------------
8
+
9
+
- Ansible >= 2.6
10
+
- lvm2 (Optional)
11
+
12
+
NOTE: Inventory should contain a single node, which should be part of the cluster. This node should be different than any of the three variables explained below, this requirement is to collect the right peers for the new node.
| gluster_maintenance_old_node | | UNDEF | The node which has to be replaced with a new node. Just the node name is needed to get the peer id, the node need not be accessible. Provide the name that was used to probe the peers. |
20
+
| gluster_maintenance_new_node | | UNDEF | New node which will replace the old node. This name can be same as the old node or different name. |
21
+
| gluster_maintenance_cluster_node | | UNDEF | The node on which the peer, volume-id details are collected. This node should be part of the trusted storage pool. And should be different from old_node or new_node. |
22
+
23
+
24
+
25
+
Dependencies
26
+
------------
27
+
28
+
Depends on:
29
+
30
+
- gluster.repositories (Optional: to subscribe to channels)
31
+
- gluster.infra (Optional: to setup bricks)
32
+
33
+
Example Playbook
34
+
----------------
35
+
36
+
Note that `server' in the inventory and the variable gluster_maintenance_cluster_node are unique (if the number of nodes are more than 2).
37
+
38
+
```
39
+
---
40
+
- remote_user: root
41
+
gather_facts: no
42
+
hosts: server
43
+
vars:
44
+
- gluster_maintenance_old_node: store
45
+
- gluster_maintenance_new_node: store
46
+
- gluster_maintenance_cluster_node: data
47
+
roles:
48
+
- gluster.maintenance
49
+
```
50
+
51
+
In the above example, a new host named store will replace the old host (the replaced node has the same hostname as the old node, however ensure that old node is not accessible with the hostname, else
replace_node - Replace gluster node with a new node.
5
+
6
+
Requirements
7
+
------------
8
+
9
+
- Ansible >= 2.6
10
+
- lvm2 (Optional)
11
+
12
+
NOTE: Inventory should contain a single node, which should be part of the cluster. This node should be different than any of the three variables explained below, this requirement is to collect the right peers for the new node.
| gluster_maintenance_old_node || UNDEF | The node which has to be replaced with a new node. Just the node name is needed to get the peer id, the node need not be accessible. Provide the name that was used to probe the peers. |
20
+
| gluster_maintenance_new_node || UNDEF | New node which will replace the old node. This name can be same as the old node or different name. |
21
+
| gluster_maintenance_cluster_node || UNDEF | The node on which the peer, volume-id details are collected. This node should be part of the trusted storage pool. And should be different from old_node or new_node. |
22
+
23
+
24
+
25
+
Dependencies
26
+
------------
27
+
28
+
Depends on:
29
+
30
+
- gluster.repositories (Optional: to subscribe to channels)
31
+
- gluster.infra (Optional: to setup bricks)
32
+
33
+
Example Playbook
34
+
----------------
35
+
36
+
Note that `server' in the inventory and the variable gluster_maintenance_cluster_node are unique (if the number of nodes are more than 2).
0 commit comments