View Constraints

Document created by madison.collins on Jul 23, 2015Last modified by fran.schwarzmann on Aug 15, 2016
Version 2Show Document
  • View in full screen mode

This information can also be found in the user manual in your VMTurbo Operations Manager.


View Constraints


As you browse the hierarchy in the Inventory view, you can drill down to specific entities to see information about their utilization of the resources they consume, as well as consumption of resources by related entities. For example, for a single physical machine you can see how its resources are consumed, as well as how the VMs that machine hosts consume its physical resources.


For many types of entities the Inventory view shows a Resources panel that lists resource details for the specific entity such as:

     • Resources on the entity, showing utilization percent, actual utilization, peak consumption, and capacity

     • Consumed resources — For example, a VM consumes resources from the physical machine that hosts it


These panels also include a Constraints button that switches the panel to show the constraints that are in effect for the given entity.



To view the constraints, it’s best to maximize the panel, then switch to the Constraints view.


As you look at this panel, you can investigate some of the restrictions that Operations Manager respects as it calculates placement for this entity. If the recommended move for a VM seems unusual to you, there is probably a constraint that explains this recommendation. You can use this panel to identify such a constraint.


If you decide to loosen the constraints on this entity, you can go to the Policies view to manage imported placement policies, or VMTurbo segments you might have created for your environment.



Inspecting Available Providers


For entities that consume resources, constraints can limit the set of providers that are available. For example, if a VM is constrained to a specific cluster of PMs, then only those PMs can provide compute resources. Also, if some hosts are constrained to specific datastores, then the VM can be further constrained to storage resources from different datastores, depending on which host the VM is on.


For another example, assume Host A with access to Storage 1. A VM on Host A can move to any other storage that is attached to Host A. Also, that VM can move to any other host that is attached to Storage 1. Wherever the VM moves, its next moves will be constrained by where it currently resides.



You can select multiple constraints to see which providers are available. Usually, the more constraints you select, the fewer providers are available.



Inspecting Consumers


If you select an entity that provides resources up the supply chain to VMs, then the constraints limit which VMs can use those resources. Similar to inspecting providers, you can select a provider and see which consumers are currently running on that provider. Note that the panel only shows consumers that are currently active.


1 person found this helpful