-
Notifications
You must be signed in to change notification settings - Fork 4
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
Vsphere audit #5205
base: main
Are you sure you want to change the base?
Vsphere audit #5205
Conversation
As of 7cb0b71 the playbook succeeds and we get most of the data we want, see this Tower run. Clearly the |
From the Ansible community - try converting MB to bytes and then using |
5ce5c04
to
3d7f163
Compare
Okay, a few math struggles later and this works well. There's a rounding-error difference between the memory usage stats in vSphere itself and the ones shown by the playbook, but it is certainly close enough. Do we want to order the storage info from most-available to least-available? Or is alphabetical by storage node okay? Also, how do we add a reminder not to use the 15TB storage nodes? |
b995315
to
e294b76
Compare
e294b76
to
70e21d3
Compare
As of dd4de74 the playbook gets the data we need. Remaining work: present space available only for general purpose storage nodes, not for all storage nodes. |
Eventually this playbook should pull the parameters we care about from vSphere:
Right now the playbook is not pulling the right values. Baby steps.