You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Filing this under nice to have because ara records host facts when Ansible gathers them so they are available but we are not doing much right now other than pretty printing them:
It's still better than nothing but there could -- perhaps -- be some sort of compact summary of the node if the facts are available.
You can see an example of all the facts available on the demo: https://demo.recordsansible.org/hosts/11031.html
For example:
We have a bunch of useful variables like ansible_distribution(_version), ansible_kernel, ansible_processor, ansible_python, etc.
There's network information available with facts like ansible_default_ipv4 and for specific network interfaces (like ansible_br0)
With ansible_memory_mb we know the amount of memory, how much is used, how much is free
With ansible_mount we know about block devices, partitions, filesystems and disk usage
With ansible_loadavg (starting in ansible-core 2.14) we know, well, the load avg.
The facts are not always gathered and even if they are, the ones we would use could be filtered out, so the implementation should be tolerant to missing facts or none at all.
It's just a nice to have when facts are available ? ¯\(ツ)/¯
The text was updated successfully, but these errors were encountered:
What is the idea ?
Filing this under nice to have because ara records host facts when Ansible gathers them so they are available but we are not doing much right now other than pretty printing them:
It's still better than nothing but there could -- perhaps -- be some sort of compact summary of the node if the facts are available.
You can see an example of all the facts available on the demo: https://demo.recordsansible.org/hosts/11031.html
For example:
ansible_distribution
(_version
),ansible_kernel
,ansible_processor
,ansible_python
, etc.ansible_default_ipv4
and for specific network interfaces (likeansible_br0
)ansible_memory_mb
we know the amount of memory, how much is used, how much is freeansible_mount
we know about block devices, partitions, filesystems and disk usageansible_loadavg
(starting in ansible-core 2.14) we know, well, the load avg.The facts are not always gathered and even if they are, the ones we would use could be filtered out, so the implementation should be tolerant to missing facts or none at all.
It's just a nice to have when facts are available ? ¯\(ツ)/¯
The text was updated successfully, but these errors were encountered: