Skip to content
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

Merged
merged 5 commits into from
Oct 12, 2019
Merged

Corosync role variable handling #75

merged 5 commits into from
Oct 12, 2019

Conversation

lae
Copy link
Owner

@lae lae commented Oct 11, 2019

This collapses all of the address-related variables used for bringing up clusters to pve_cluster_addr0 and pve_cluster_addr1, while maintaining backwards compatibility. The bindnet parameters are no longer passed to pvecm 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.

gilou and others added 4 commits October 10, 2019 19:56
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
@lae lae added this to the 1.6.2 milestone Oct 11, 2019
@lae
Copy link
Owner Author

lae commented Oct 11, 2019

@lae lae requested a review from trickert76 October 11, 2019 03:48
@lae
Copy link
Owner Author

lae commented Oct 11, 2019

@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.

@trickert76
Copy link
Collaborator

I'll try to check that today.

yaml is such a pain sometimes
@trickert76
Copy link
Collaborator

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 }}"
Copy link
Collaborator

@trickert76 trickert76 Oct 12, 2019

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.

Copy link
Collaborator

@trickert76 trickert76 left a 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.

@lae lae merged commit 71b1212 into develop Oct 12, 2019
@lae lae deleted the feature/ring0_references branch August 4, 2020 17:51
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

Successfully merging this pull request may close these issues.

3 participants