community.proxmox.proxmox_cluster_ha_groups module – Management of HA groups in Proxmox VE Cluster
Note
This module is part of the community.proxmox collection (version 1.3.0).
You might already have this collection installed if you are using the ansible package. It is not included in ansible-core. To check whether it is installed, run ansible-galaxy collection list.
To install it, use: ansible-galaxy collection install community.proxmox. You need further requirements to be able to use this module, see Requirements for details.
To use it in a playbook, specify: community.proxmox.proxmox_cluster_ha_groups.
New in community.proxmox 1.1.0
Synopsis
- Configure HA groups via
/cluster/ha/groups.
Requirements
The below requirements are needed on the host that executes this module.
- proxmoxer >= 2.0
- requests
Parameters
Parameter | Comments |
|---|---|
api_host string / required | Specify the target host of the Proxmox VE cluster. Uses the |
api_password string | Specify the password to authenticate with. Uses the |
api_port integer | Specify the target port of the Proxmox VE cluster. Uses the |
api_token_id string | Specify the token ID. Uses the |
api_token_secret string | Specify the token secret. Uses the |
api_user string / required | Specify the user to authenticate with. Uses the |
comment string | Description |
name string / required | group name |
nodes list / elements=string | List of cluster node members, where a priority can be given to each node. A resource bound to a group will run on the available nodes with the highest priority. If there are more nodes in the highest priority class, the services will get distributed to those nodes. The priorities have a relative meaning only. The higher the number, the higher the priority. It can either be a string |
nofailback boolean | The CRM tries to run services on the node with the highest priority. If a node with higher priority comes online, the CRM migrates the service to that node. Setting Choices:
|
restricted boolean | Resources bound to restricted groups may only run on nodes defined by the group. The resource will be placed in the stopped state if no group node member is online. Resources on unrestricted groups may run on any cluster node if all group members are offline, but they will migrate back as soon as a group member comes online. One can implement a ‘preferred node’ behavior using an unrestricted group with only one member. Choices:
|
state string / required | Whether the HA groups should be there (created if missing) or not (deleted if they exist). Choices:
|
validate_certs boolean | If This should only be used on personally controlled sites using self-signed certificates. Uses the Choices:
|
Attributes
Attribute | Support | Description |
|---|---|---|
action_group | Action group: community.proxmox.proxmox | Use |
check_mode | Support: none | Can run in |
diff_mode | Support: none | Will return details on what has changed (or possibly needs changing in |
Examples
- name: Create HA group
community.proxmox.proxmox_cluster_ha_groups:
api_host: "{{ ansible_host }}"
api_password: "{{ proxmox_root_pw | default(lookup('ansible.builtin.env', 'PROXMOX_PASSWORD', default='')) }}"
api_user: root@pam
state: "present"
name: ha0
comment: yes
nodes: node0:0,node1:1
nofailback: true
restricted: false
- name: Delete HA group
community.proxmox.proxmox_cluster_ha_groups:
api_host: "{{ ansible_host }}"
api_password: "{{ proxmox_root_pw | default(lookup('ansible.builtin.env', 'PROXMOX_PASSWORD', default='')) }}"
api_user: root@pam
state: "absent"
name: ha0
Collection links
© 2012–2018 Michael DeHaan
© 2018–2025 Red Hat, Inc.
Licensed under the GNU General Public License version 3.
https://docs.ansible.com/ansible/latest/collections/community/proxmox/proxmox_cluster_ha_groups_module.html