Another topic of interest that yesterday's tests spawned is "Local storage matching". Setup is ACS 4.17.2 with XCP-NG with local storage only (for VR and User vms) Here is an example:
there are 30 hosts that will be joined to a pool with the following local storages: - server 1-10 - have 1 ssd local storage of size 500 GB - server 11-20 have 1 x 500 SSD and 1 x NVME 1.5TB - serves 21-30 have 1 x 1TB ssd and 1 x 1TB HDD local storage After joining the hosts, storages will be tagged to fit environment needs. - default tag - will be for SSD disks, that is for instances with no special requirements - speed tag - for instances that require NVME storage - store tag - for instances that are used for storing data or backup and do not require much speed - (NFS etc..) Tagging logic: 1-10 - have just 1 ssd so tag "default" is applied on all of them 11-20 - have 2 storage pools they are with different disk properties and different disk sizes. We can differentiate by disk size. 21-30 - same as previous example but of same size so we cannot decide. Neither are disk properties exposed in the CMK LIST STORAGE POOLS command. Disk names cannot be used too as when hosts are joined ACS renames local storages with generic UUID like 4c4ed139-721c-8491-e65c-775e9d599fdd. Are there any methods that can be used to understand what is the underlying storage below? Regards, Jordan
