Hi.
Is adapting VMFleet for an stretched Azurestack HCI Cluster on the roadmap?
On a non stretched HCI Cluster everything is working.
And running straight fleetsweeps against it also is working.
But any command that is querying the storagepools like Get-FleetVolumeEstimate and, most important, Measure-FleetCoreWorkload to get a nice summary report of every workload benchmark is not working, because it exiting when it realize the two storagepools which exists in a stretched cluster!
Stretched Cluster support would be very important nowadays.
Hi. Is adapting VMFleet for an stretched Azurestack HCI Cluster on the roadmap? On a non stretched HCI Cluster everything is working. And running straight fleetsweeps against it also is working. But any command that is querying the storagepools like Get-FleetVolumeEstimate and, most important, Measure-FleetCoreWorkload to get a nice summary report of every workload benchmark is not working, because it exiting when it realize the two storagepools which exists in a stretched cluster!
Stretched Cluster support would be very important nowadays.
Thanks Olaf