-
Notifications
You must be signed in to change notification settings - Fork 336
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
vmware_cluster_ha - add set of heartbeat datastores #1732
base: main
Are you sure you want to change the base?
Conversation
Build failed. ✔️ ansible-tox-linters SUCCESS in 8m 26s |
recheck |
Build failed. ✔️ ansible-tox-linters SUCCESS in 8m 30s |
recheck |
Build failed. ✔️ ansible-tox-linters SUCCESS in 9m 26s |
recheck |
Build failed. ✔️ ansible-tox-linters SUCCESS in 9m 08s |
It looks like your changes break this test for idempotency: community.vmware/tests/integration/targets/vmware_cluster_ha/tasks/main.yml Lines 76 to 82 in 60df9ac
|
recheck |
Build succeeded. ✔️ ansible-tox-linters SUCCESS in 8m 38s |
@Nina2244 Finally, I found the time to test this. However, I'm not really sure if the module works as intended. If a cluster already has a list of hearbeat datastores defined, it seems to work fine. That is, if the configured list of datastores differs from the one that is defined, this will be remediated. But if no heartbeat datastores are configured, defining On they other hand, if there is a list of heartbeat datastores configured but not defined in |
@mariolenz really nice that you tested the other both cases. I will look for it why there is no change in both cases. |
@Nina2244 Since I'm beginning to think that we should not introduce new parameters with default behavior (this might break existing playbooks) I wonder how this new parameter
What do you think? BTW, I think you can compare both lists directly. Or, since there's not really an order to the datastores, you might want to make a set out of them first. So you could check for |
…andidate policy
@mariolenz i added the thing with None, and with the empty list, but I not really understand what you mean with your third point. |
Build failed. ✔️ ansible-tox-linters SUCCESS in 8m 33s |
Build failed. ✔️ ansible-tox-linters SUCCESS in 9m 42s |
recheck |
Build failed. ✔️ ansible-tox-linters SUCCESS in 8m 55s |
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.
The CI is still making trouble, but I hope we'll get it into 3.8.
description: | ||
- A list of the heartbeat datastores. | ||
- If list ist [] then all datastores of the cluster will be set as heartbeat_datastores. | ||
type: list |
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.
type: list | |
version_added: '3.8.0' | |
type: list |
- allFeasibleDs -> Automatically select datastores accessible from the hosts. Causes that C(heartbeat_datastores) will be ignored. | ||
- userSelectedDs -> Use datastores only from the specified list. | ||
- allFeasibleDsWithUserPreference -> Use datastores from the specified list and complement automatically if needed. | ||
type: str |
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.
type: str | |
version_added: '3.8.0' | |
type: str |
Build failed. ✔️ ansible-tox-linters SUCCESS in 9m 23s |
Build succeeded. ✔️ ansible-tox-linters SUCCESS in 10m 45s |
Build succeeded. ✔️ ansible-tox-linters SUCCESS in 11m 22s |
SUMMARY
Add the possibility to set the heartbeat datastores of an cluster.
Is the new Pullrequest for #1663.
ISSUE TYPE
COMPONENT NAME
vmware_cluster_ha
ADDITIONAL INFORMATION