PowerShell provides a great automation platform for Windows. At VMware, we’ve been exploring PowerShell interfaces for VMware Infrastructure and VMworld gave us a good opportunity to provide a sneak peek at some of the forms those interfaces could take. You can view the slides from that session here: Download VMworld2007_IO30.pdf
In case you don’t feel like browsing through the slides, here’s a quick sample:
Get-VM qa* | Get-NetworkAdapter | where { $_.NetworkName -eq "red" } | Set-NetworkAdapter -NetworkName "blue"
This little example shows off some of the leverage and simplicity a PowerShell interface could provide. Hopefully, it’s self-explanatory but I’ll translate it anyway: For all virtual machines with names that start with "qa," change any network adapters they may have that are attached to the "red" network to instead be attached to the "blue" network. This is pretty typical PowerShell syntax, composing a few simple commands with a little bit of PowerShell language scripting to accomplish a task. And it’s indicative of the kind of simplicity we’re trying to achieve.
On the PowerShell development team, we’re very excited about this work and we’re interested in feedback from any of you who may have comments and in particular from anyone who attended the VMworld session on this topic (IO30).
To keep up with ongoing work, please subscribe to one of our blog feeds:
