PowerCLI – What’s new ?

image Unless you have been living in a cave in the middle of the woods with no internet access you will know that today VMware released the long awaited and the worst kept secret of all time, vSphere.

Along with vSphere comes alot of other lowercase v starting words including vCompute, vNetwork, vStorage and vPowerCLI, actually hold on, they seam to have forgotten the v with this one, PowerCLI it is!  PowerCLI is the new look all improved VI Toolkit.

(Personally I love the name – much better than VI Tookit. Nice one C-Dawg !)

So what’s new ?

There have been several bug fixes, speed enhancements and 8 new cmdlets, these are as follows:

Apply-VMHostProfile
Export-VMHostProfile
Get-VMHostProfile
Import-VMHostProfile
New-VMHostProfile
Remove-VMHostProfile
Set-VMHostProfile
Test-VMHostProfileCompliance

And what can we do with these, well basically manage host profiles as you can see from the below examples:

Get-VMHostProfile
Retrieves the virtual machine host profile named Profile01.

Get-VMHostProfile -Name Profile01

Apply-VMHostProfile
Apply the host profile named testProfile to the virtual machine host with an IP address 192.168.1.10.

$MyHostProfile = Get-VMHostProfile -Name testProfile
$applyHost = Get-VMHost 192.168.1.10
Apply-VMHostProfile -Entity $applyHost -Profile $MyHostProfile -Confirm:$false

Export-VMHostProfile
Exports the selected host profile to the export.prf file.

$MyHostProfile = (Get-VMHostProfile -Name testProfile )[0]
Export-VMHostProfile -FilePath export.prf -Profile $MyHostProfile -Force

So should we upgrade ? Yes – even if you don’t use vSphere, PowerCLI still works with your current VI and you will still get the benefits of the bug fixes and the spead enhancements.

For more information and a nice video showing how to use the host profile cmdlets make sure you check out the PowerCLI Blog

Alan

Alan Renouf has a role of Automation Frameworks Product Manager at VMware responsible for providing the architects and operators of the cloud infrastructure with the toolkits/frameworks and command-line interfaces they require to build a fully automated software-defined datacenter. Alan is a frequent blogger at http://blogs.vmware.com/vipowershell and has a personal blog at http://virtu-al.net. You can follow Alan on twitter as @alanrenouf.

You may also like...

3 Responses

  1. Peter Cross says:

    $cluster = Get-Cluster xxxxxx
    Get-VMHost -Location $cluster | Test-VMHostProfileCompliance

    Produces an output with trucated VMHostIds. Is the any verbose command to expand this output?

    VMHostId VMHostProf IncomplianceElementList
    ileId
    ——– ———- ———————–
    HostSys… HostPro… {network.vswitch[“key-vim-profile-host-VirtualSwitchProfi…
    HostSys… HostPro… {network.vswitch[“key-vim-profile-host-VirtualSwitchProfi…
    HostSys… HostPro… {network.vswitch[“key-vim-profile-host-VirtualSwitchProfi…
    HostSys… HostPro… {network.vswitch[“key-vim-profile-host-VirtualSwitchProfi…
    HostSys… HostPro… {network.vmPortGroup[“key-vim-profile-host-VmPortgroupPro…

  2. Virtu-Al says:

    @NiTRo
    The vMA appliance (previously called VIMA) is an appliance for vSphere (see http://www.vmware.com/support/developer/vima/).

    This has Perl but no PowerCLI.

    The release notes state that it can be used to manage ESX 3.5u2 and later.

  3. NiTRo says:

    Hi, do you know if the vMA appliance is working on vCenter 2.5 ?

Leave a Reply

%d bloggers like this: