@@ -422,9 +422,7 @@ pve_users: [] # List of user definitions to manage in PVE. See section on User M
422
422
pve_storages: [] # List of storages to manage in PVE. See section on Storage Management.
423
423
pve_datacenter_cfg: {} # Dictionary to configure the PVE datacenter.cfg config file.
424
424
pve_domains_cfg: [] # List of realms to use as authentication sources in the PVE domains.cfg config file.
425
- pve_no_log: false # Set this to true in production to disable logging for strorage add to avoid having credentials leaked in log.
426
- pve_addr0_priority: 255 # Type: integer Sets the Priority of the first Link for Corosync. Lower Number means higher Priority.
427
- pve_addr1_priority: 0 # Type: integer See [pvecm-network-priority] for more Information.
425
+ pve_no_log: false # Set this to true in production to prevent leaking of storage credentials in run logs. (may be used in other tasks in the future)
428
426
```
429
427
430
428
To enable clustering with this role, configure the following variables appropriately:
@@ -437,12 +435,17 @@ pve_manage_hosts_enabled : yes # Set this to no to NOT configure hosts file (cas
437
435
438
436
The following variables are used to provide networking information to corosync.
439
437
These are known as ring0_addr/ring1_addr or link0_addr/link1_addr, depending on
440
- PVE version. They should be IPv4 or IPv6 addresses. For more information, refer
441
- to the [ Cluster Manager] [ pvecm-network ] chapter in the PVE Documentation.
438
+ PVE version. They should be IPv4 or IPv6 addresses. You can also configure the
439
+ [ priority of these interfaces] [ pvecm-network-priority ] to hint to corosync
440
+ which interface should handle cluster traffic (lower numbers indicate higher
441
+ priority). For more information, refer to the [ Cluster Manager] [ pvecm-network ]
442
+ chapter in the PVE Documentation.
442
443
443
444
```
444
445
# pve_cluster_addr0: "{{ defaults to the default interface ipv4 or ipv6 if detected }}"
445
446
# pve_cluster_addr1: "another interface's IP address or hostname"
447
+ # pve_cluster_addr0_priority: 255
448
+ # pve_cluster_addr1_priority: 0
446
449
```
447
450
448
451
You can set options in the datacenter.cfg configuration file:
@@ -595,9 +598,9 @@ Refer to `library/proxmox_role.py` [link][user-module] and
595
598
596
599
## Storage Management
597
600
598
- You can use this role to manage storage within Proxmox VE (both in
599
- single server deployments and cluster deployments). For now, the only supported
600
- types are ` dir ` , ` rbd ` , ` nfs ` , ` cephfs ` , ` lvm ` ,` lvmthin ` , ` zfspool ` , ` btrfs ` , ` cifs `
601
+ You can use this role to manage storage within Proxmox VE (both in single
602
+ server deployments and cluster deployments). For now, the only supported types
603
+ are ` dir ` , ` rbd ` , ` nfs ` , ` cephfs ` , ` lvm ` ,` lvmthin ` , ` zfspool ` , ` btrfs ` , ` cifs `
601
604
and ` pbs ` . Here are some examples.
602
605
603
606
```
0 commit comments