-
-
Notifications
You must be signed in to change notification settings - Fork 148
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Corosync role variable handling #75
Conversation
Replace ring0_addr/ and friends with addr0/addr1 Remove bindnet vars and flags Deduplicate some tasks Check for facts instead of IPv4 address for cluster hosts
Backwards compat test: https://travis-ci.org/lae/ansible-role-proxmox/jobs/596410730 |
@trickert76 if you've got time to look at this, let me know. Otherwise I'm just gonna merge near the end of the week. |
I'll try to check that today. |
yaml is such a pain sometimes
9bbec82
to
397aa9f
Compare
Looks good to me. |
# PVE 6.x (Debian Buster) clustering options | ||
pve_cluster_link0_addr: "{{ ansible_default_ipv4.address }}" | ||
# pve_cluster_link1_addr: "another interface's IP address or hostname" | ||
# pve_cluster_addr0: "{{ ansible_default_ipv4.address }}" |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Just my two cents, I've learned, that the default interfaces may change. For example docker installations add docker0 and then because d is before e, the default interfaces in ansible changes. Maybe we should mention that. I've added somewhere else in my playbook a set_fact based on a filter of all interfaces starting with 'e' to get the first address. But when you use more then one ethernet device, this will maybe overridden. Nothing to change here.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
is ok for me.
This collapses all of the address-related variables used for bringing up clusters to
pve_cluster_addr0
andpve_cluster_addr1
, while maintaining backwards compatibility. The bindnet parameters are no longer passed topvecm
either, as they turned out to be redundant to the ring parameters.This also removes instances in the configuration where the hosts' default IPv4 address was used even if ring0 address was overridden. See #47 for more information.