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
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
The text was updated successfully, but these errors were encountered:
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
The text was updated successfully, but these errors were encountered: