5 Replies
Last post:
Sep 30, 2008 11:33 AM by
LucD
On the other hand, Get-VirtualSwitch does not return all virtual switches. Instead you must specify a VMHost or VM argument that causes a subset to be returned. Does anyone prefer this behavior? Would it cause problems if Get-VirtualSwitch returned all virtual switches, even given the fact that you may have a lot of virtual switches with different names across different hosts?
Currently, this is how Get-Folder works. You will often have dupe
folder names in a virtual center (especially the built-in "vm"
folder). I've never had the thought, "I wish Get-Folder gave me fewer
results". But I do think it can be difficult to match the folders to
their parents which is an area I think you guys could improve by
adding reference (parent) properties.
To take it even farther, should Get-HardDisk return all hard disks, along with a pointer to the VM that owns them?
I'm leaning towards being all-inclusive with filternig being optional
based on a Name (or other parameter). However, every time you do this
you (virtually) create a new flat namespace which can add confusion.
I don't have the right answer.
I thought one of the nice features of PowerShell was that you could 'read' a line practically as plain English (wasn't that the purpose of the verb-noun format ?).
In the example I would need to 'know' how large the default scope of the cmdlet was to understand what was being done.
I prefer something like this
That way I 'see' that I'm doing this against all port groups, called "App Group", in the cluster, irrespective of the number of hosts in the cluster
And my network admins will still be jealous
Hence my remark to have no default scope for the Get-VirtualSwitch, Get-Harddisk... type cmdlets.
In the example I would need to 'know' how large the default scope of the cmdlet was to understand what was being done.
I prefer something like this
Get-Cluster MyCluster | Get-VirtualPortGroup "App Group" | Set-VirtualPortGroup -vlan 100
That way I 'see' that I'm doing this against all port groups, called "App Group", in the cluster, irrespective of the number of hosts in the cluster
And my network admins will still be jealous
Hence my remark to have no default scope for the Get-VirtualSwitch, Get-Harddisk... type cmdlets.