Great project - Thanks

[Paul2000DE]

Thanks for this project. We integrated this already to our pipeline when creating new VMs. We have different clusters and one of our bigger clusters has a mixed hardware set like:

Detected nodes:
DEN01 | 192.168.10.10 | x86-64-v4
DEN02 | 192.168.10.11 | x86-64-v4
DEN03 | 192.168.10.12 | x86-64-v4
DEN04 | 192.168.10.13 | x86-64-v4
DEN05 | 192.168.10.14 | x86-64-v4
DEN06 | 192.168.10.15 | x86-64-v4
DEN07 | 192.168.10.16 | x86-64-v4
DEN08 | 192.168.10.17 | x86-64-v4
DEN09 | 192.168.10.18 | x86-64-v4
DEN10 | 192.168.10.19 | x86-64-v4
DEN11 | 192.168.10.20 | x86-64-v3
DEN12 | 192.168.10.21 | x86-64-v3
DEN13 | 192.168.10.22 | x86-64-v3
DEN14 | 192.168.10.23 | x86-64-v3
DEN15 | 192.168.10.24 | x86-64-v3
DEN16 | 192.168.10.25 | x86-64-v2-AES
DEN17 | 192.168.10.26 | x86-64-v2-AES
DEN18 | 192.168.10.27 | x86-64-v2-AES
DEN19 | 192.168.10.28 | x86-64-v4
DEN20 | 192.168.10.29 | x86-64-v4
DEN21 | 192.168.10.30 | x86-64-v4
DEN22 | 192.168.10.31 | x86-64-v4
DEN23 | 192.168.10.32 | x86-64-v4
DEN24 | 192.168.10.33 | x86-64-v4
DEN25 | 192.168.10.34 | x86-64-v4
DEN26 | 192.168.10.35 | x86-64-v4
DEN27 | 192.168.10.36 | x86-64-v4
DEN28 | 192.168.10.37 | x86-64-v4
DEN29 | 192.168.10.38 | x86-64-v4
DEN30 | 192.168.10.39 | x86-64-v4
DEN31 | 192.168.10.40 | x86-64-v4
DEN32 | 192.168.10.41 | x86-64-v4
DEN33 | 192.168.10.42 | x86-64-v4
DEN34 | 192.168.10.43 | x86-64-v4

Cluster CPU type: x86-64-v2-AES

It correctly fetches the data and CPU types. You can clearly see when we extended the cluster and when we started to replace older nodes with newest generations. This tool is really helpful when coming from VMware!

Thanks