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

vmware_datastore_cluster: Add automation levels, vm overrides, Space and IO Load Balance Config #1734

Open
wants to merge 17 commits into
base: main
Choose a base branch
from

Conversation

Nina2244
Copy link
Contributor

SUMMARY

Add the automation levels:

  • Space balance
  • I/O balance
  • Rule enforcement
  • Vm evacuation

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
  • Feature Pull Request
COMPONENT NAME

vmware_datastore_cluster

ADDITIONAL INFORMATION

New Pull Request after Rebase #1278

@mariolenz
Copy link
Collaborator

The CI fails with:

ERROR: Found 4 pep8 issue(s) which need to be resolved:
ERROR: plugins/modules/vmware_datastore_cluster.py:368:161: E501: line too long (200 > 160 characters)
ERROR: plugins/modules/vmware_datastore_cluster.py:374:161: E501: line too long (201 > 160 characters)
ERROR: plugins/modules/vmware_datastore_cluster.py:380:161: E501: line too long (207 > 160 characters)
ERROR: plugins/modules/vmware_datastore_cluster.py:386:161: E501: line too long (192 > 160 characters)

Could you shorten those lines, or refactor them into several lines with <= 160 characters each?

@Nina2244
Copy link
Contributor Author

recheck

@mariolenz
Copy link
Collaborator

recheck

@mariolenz
Copy link
Collaborator

recheck

@mariolenz
Copy link
Collaborator

recheck

@mariolenz
Copy link
Collaborator

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

@Nina2244
Copy link
Contributor Author

Nina2244 commented Jun 7, 2023

recheck

@Nina2244
Copy link
Contributor Author

Nina2244 commented Jun 7, 2023

recheck

@softwarefactory-project-zuul
Copy link

Build failed.
https://ansible.softwarefactory-project.io/zuul/buildset/ccba6c651e0c4885b6e0cec1cb4cb299

✔️ ansible-tox-linters SUCCESS in 9m 21s
✔️ build-ansible-collection SUCCESS in 10m 15s
ansible-test-cloud-integration-vcenter7_only-stable215 NODE_FAILURE Node request 200-0006211403 failed in 0s
ansible-test-cloud-integration-vcenter7_2esxi-stable215 NODE_FAILURE Node request 200-0006211404 failed in 0s
ansible-test-cloud-integration-vcenter7_1esxi-stable215_1_of_2 NODE_FAILURE Node request 200-0006211405 failed in 0s
ansible-test-cloud-integration-vcenter7_1esxi-stable215_2_of_2 NODE_FAILURE Node request 200-0006211406 failed in 0s
✔️ ansible-galaxy-importer SUCCESS in 4m 51s

@mariolenz
Copy link
Collaborator

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

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

None yet

2 participants