Add more detailed hardware metrics to the collection and output of `validator-info`

[WadeBarnes]

The output of validator-info currently returns limited hardware metrics for a given node. To better facilitate node monitoring as well as continuous node compliance monitoring, validator-info should report a more complete set of hardware metrics including:

• Hard Disk Stats
  • Total size (amount), available (amount), and used (amount and percent) for all volumes.
  • Total size (amount), available (amount), and used (amount and percent) for indy-node specifically.
• Memory and CPU
  • The CPU and memory use of the node processes is reported, however,
  • The output should be updated to provide more details regarding overall system memory and CPU usage and load.
• Network Interface IP Binding
  • Information regarding NIC and IP address bindings.
  • To be used to ensure the node has been configured with separate IP addresses, bound to separate NICs, and assigned to different subnets.

All information should be included in the output of validator-info on the node itself, and authenticated calls to the get-validator-info transaction. It appears the results for each are different, with the results of validator-info containing more information.

This is to address HDD, Memory, and CPU resource discussions here; https://github.com/hyperledger/indy-node-monitor/issues/24#issuecomment-785888739

Requirements:

• https://github.com/hyperledger/indy-node/issues/1672
• https://github.com/hyperledger/indy-node/issues/1673

[lohanspies]

We should also potentially include RAID 1 detection as this is a technical policy requirement. Unless this will fall into the technical policy checks.

[WadeBarnes]

We should also potentially include RAID 1 detection as this is a technical policy requirement. Unless this will fall into the technical policy checks.

@lohanspies, Would you be able to provide a link to the associated document please?

[lohanspies]

https://sovrin.org/wp-content/uploads/Steward-Technical-and-Organizational-Policies-V2.pdf Node Technical Policies number 7 "MUST have at least 1 TB, with the ability to grow to 2 TB, of reliable (e.g., RAIDed) disk space, with an adequately sized boot partition." Don't specifically mention RAID as a requirement though, however it is being checked here - https://github.com/sovrin-foundation/steward-tools/blob/4b746d7d3a3ccd5981c9c984df39dab44258c2fc/steward_tech_check.py#L101

[WadeBarnes]

https://sovrin.org/wp-content/uploads/Steward-Technical-and-Organizational-Policies-V2.pdf Node Technical Policies number 7 "MUST have at least 1 TB, with the ability to grow to 2 TB, of reliable (e.g., RAIDed) disk space, with an adequately sized boot partition." Don't specifically mention RAID as a requirement though, however it is being checked here - https://github.com/sovrin-foundation/steward-tools/blob/4b746d7d3a3ccd5981c9c984df39dab44258c2fc/steward_tech_check.py#L101

Collection of that information would be covered under this ticket which is asking for the metrics collected by the script to be integrated into validator-info; https://github.com/hyperledger/indy-node/issues/1670