VMware vSphere

 View Only
Expand all | Collapse all

Storage vMotion VM according to their observed IOPS

  • 1.  Storage vMotion VM according to their observed IOPS

    Posted Aug 19, 2023 07:54 AM

    I'd like to move VMs automatically according to their impact on datastores.

    I rarely use vCenter anymore though, and it had been months, maybe over a year since the last time vROps ran was last started; I'm a need-a-tetanus-shot rusty on their capabilities. I remember vaguely that — an even older version than my already old v8.2 — Operations used to show on those welcome assistants, pre-made workflows to sort VMs in tiers with using tags. Kind of what I want, however, if I remember correctly, that still required foreseeing the VM's storage impact to manually apply a storage policy, the whole tag system was just some fancy scheme to keep track of datastores and keep compliance.

    One of my goals is to reduce the likelihood of VMs being migrated to certain datastores unless IOPS skyrocket and there's just no other way; like the similar feature host anti-affinity (or Admission Control fits too) but for datastores and reevaluated constantly. It's sort of keeping track of the VM('s needs) rather than of the datastores.

    I turned on Storage DRS, clustered the previously-standalone datastores, enabled SIOC on all datastores, even those not related. I confirmed vROps is still connected to vCenter, to Active Directory, and sending data back to 'center. It was. At two hours top back online, it's going to be a while before I get a baseline but it was enough to correct the IO imbalance just by enabling Storage DRS. I still would like some way to influence VM-to-datastore placement, though.

    Is this possible?




    This is still vSphere 7: ESXi/vCenter 7-ish, vRealize Operations Manager 8.

  • 2.  RE: Storage vMotion VM according to their observed IOPS

    Posted Aug 20, 2023 10:49 AM

    I would already upgrade vROPS to VMware Aria Operations.