The reward for successfully employing the technique: speed.
#RAZORSQL GET VIEW PROPERTIES HOW TO#
This is not the most obvious route at first, but eventually you can see how to use the method to update managed object view data, and then access the nested managed objects' views using " LinkedView" objects that then reside "in" the parent managed object as properties. Conversely, there is but one (1) call to communicate with vCenter for all "child" managed objects involved when UpdateViewData() is used. To get additional managed object info using Get-View, there is a Get-View call involved for every managed object references (MORefs). The speed gain comes, in part, from the sheer number of calls being made that require a round trip request to the given vCenter server(s).
UpdateViewData() - Speed testing results in a couple of different environment sizes: To see the speed differences for the main info-gathering portion of each way, I measured these two pieces mentioned above: lines 04-07 for the first way, and line 04 for the second way. The second way uses one UpdateViewData() call to make the FirewallSystem managed objects available from the original array of cluster managed objects. Line 04 in 2nd way: The first way uses the standard way of additionally calling Get-View for each cluster to get the HostSystems, and then again for each HostSystem to get the FirewallSystem objects.
#RAZORSQL GET VIEW PROPERTIES CODE#
The differences in code between the two ways: # get the VM managed objects with a couple of properties $arrNetworkViews = Get-View -ViewType Network -Property Name,VM -Filter = $strNetworkNamePattern} # get the virtual networks whose name match this pattern $strNetworkNamePattern = "MyVMNetwork1711"
# the network name pattern to use for getting vitual networks You could use the following standard way using multiple Get-View calls: This example goes about doing so by getting said network(s), getting the VMs connected to them, and then getting guest IP info. Say you wanted to get the IPs configured on VMs that are connected to particular VM networks. "So, what?" So, speed!Įxample 0: Get guest IP info for VMs using given VM network The UpdateViewData() method had already been able to selectively update properties of the given managed object view, but one would have to use Get-View again to retrieve views of nested managed objects that are properties of that parent managed object. The technique is centered around using the UpdateViewData() method of a "view" of a managed object (".NET View object") to retrieve nested views of managed objects. VMware has provided a way to speed things up even more.Ī while back (Aug 2011), the official PowerCLI blog had a post about how to "Optimize the performance of PowerCLI's views". It can take quite a bit longer to write a script using Get-View versus using other cmdlets, but the speed payoff is usually well worth the additional upfront time investement. When properly used, the Get-View cmdlet is known to be far faster than using other PowerCLI cmdlets for getting info (such as Get-VM, Get-VMHost, Get-Datastore, etc.). We are always looking for speed, speed, speed in our PowerShell / PowerCLI scripts.
0 kommentar(er)
