The Ceph configuration section in the README is a bit lackluster and requires the user to parse through the example provided themselves - of which some might not even be needed for some users. Ideally, this section should provide steps and explanations along the way for configuring PVE Ceph with the help of this role.

I haven't exactly used this feature myself, so it might be best for someone w

So this script works wonderfully in Ansible Tower, but it pulls in every host from the cluster. This is problematic if you have limited subscriptions.

If you could provide a filter, then the hosts being pulled into Ansible Tower(and probably AWX) could be limited to running or some other attribute E.G. Resource Pool, operating system type(windows or linux), etc.

• storage, in which we can have a base and zfs and plain and ...
• runnable (the "vm"/"lxc"s)
• backend, where we wrap the api and can possibly mock it
• main
• cluster, where put the rest: cluster, storagenode, ...

If there is one test we can easily create more. And it's nicer to develop against test data than to keep running it against a live server.

pve_lxc_disk_free claims to provide information about free disk space for an lxc container, however the used disk space is exported.

Using Proxmox VE 5.4-6