-
Notifications
You must be signed in to change notification settings - Fork 339
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_datastore_cluster: Add automation levels, vm overrides, Space and IO Load Balance Config #1734
base: main
Are you sure you want to change the base?
vmware_datastore_cluster: Add automation levels, vm overrides, Space and IO Load Balance Config #1734
Conversation
… Load Balance Config to this module
Build failed. ✔️ ansible-tox-linters SUCCESS in 8m 28s |
The CI fails with:
Could you shorten those lines, or refactor them into several lines with <= 160 characters each? |
Build failed. ✔️ ansible-tox-linters SUCCESS in 8m 47s |
recheck |
Build failed. ✔️ ansible-tox-linters SUCCESS in 9m 27s |
recheck |
Build failed. ✔️ ansible-tox-linters SUCCESS in 8m 36s |
recheck |
Build failed. ✔️ ansible-tox-linters SUCCESS in 8m 29s |
recheck |
Build failed. ✔️ ansible-tox-linters SUCCESS in 8m 35s |
@Nina2244 I'm beginning to think that we should not introduce new parameters with defaults (or new defaults for existing parameters) in a minor version. You see, this might break things for the users. For example, if people have configured the space balance automation level to manual and run the current version of the module, there won't be any change. But merging this PR means there will be a change to automated. So please remove the defaults and just ignore those parameters if they're not defined. If you think those defaults a good idea, we could open an issue to implement them in the next major release. There's a milestone where we could add this so we don't forget. |
Build failed. ❌ ansible-tox-linters FAILURE in 8m 35s |
Build failed. ❌ ansible-tox-linters FAILURE in 8m 32s |
Build failed. ✔️ ansible-tox-linters SUCCESS in 8m 41s |
Build failed. ❌ ansible-tox-linters POST_FAILURE in 9m 04s |
recheck |
Build failed. ❌ ansible-tox-linters FAILURE in 8m 42s |
recheck |
Build succeeded. ✔️ ansible-tox-linters SUCCESS in 9m 17s |
Build failed. ✔️ ansible-tox-linters SUCCESS in 9m 37s |
Build failed. ✔️ ansible-tox-linters SUCCESS in 9m 21s |
@Nina2244 FYI: I think the sanity tests should work now, this seems to fix the GH action. However, it looks like we still have some problems with the integration tests 😢 |
Build failed. ✔️ ansible-tox-linters SUCCESS in 10m 36s |
Build failed. ✔️ ansible-tox-linters SUCCESS in 11m 29s |
Build failed. ❌ ansible-tox-linters FAILURE in 9m 42s |
Build failed. ✔️ ansible-tox-linters SUCCESS in 9m 45s |
SUMMARY
Add the automation levels:
and add Space Load Balance Config
and the possibility to override the datastore cluster settings (keep vmdks together and automation level) for Virtual Machines.
ISSUE TYPE
COMPONENT NAME
vmware_datastore_cluster
ADDITIONAL INFORMATION
New Pull Request after Rebase #1278