Monday, 8 June 2009
Adding actions to the Virtualization EcoShell
I’m prepping my Virtualization EcoShell presentation which I’ll deliver at the Belgium VMware Usergroup Meeting and discovered a great new feature. It’s adding your own actions as new items. Just click “Add new item” in the actions menu on the right side of the Virtualization EcoShell. This enables you to specify a script performing the Action. When you click an Action, objects currently selected in the grid are piped into the script. I created a little Jing demo showing how to add Carter’s CPU-Ready script.
Trackbacks
Trackback specific URI for this entry
No Trackbacks
Comments
Display comments as
(Linear | Threaded)
Great job Eric 
. I didn't know this feature was so "hidden". I will try to make it more public and document how to do some custom work. one quick note, when you modified the script from it's original $input | foreach-object {}, it changes the behavior of VESI slightly. With your code, it will query all results and return them all at once. if you break it out to fit into the existing $input | foreach-object {} structure, it will return results one at a time as it receives them back at the cost of more, but faster get-stat calls. If you have a lot of VMs, I'd recommend the foreach-object method, or you may experience a long period of unresponsiveness.
-Scott
. I didn't know this feature was so "hidden". I will try to make it more public and document how to do some custom work. one quick note, when you modified the script from it's original $input | foreach-object {}, it changes the behavior of VESI slightly. With your code, it will query all results and return them all at once. if you break it out to fit into the existing $input | foreach-object {} structure, it will return results one at a time as it receives them back at the cost of more, but faster get-stat calls. If you have a lot of VMs, I'd recommend the foreach-object method, or you may experience a long period of unresponsiveness.
-Scott
#1
Scott Herold
(Homepage)
on
2009-06-11 16:17
(Reply)
