|
I'll look into this in detail soon. Some of this may be addressed in the open beta revision. The rest (like this new bug you found) I believe can be handled by the VI SDK or other means. From my research so far things QUICKLY get hairy, at least in my terms, from a sysadmin POV. I imagine some developers may not see it the same way.
Also FYI, there are a few other ideas on my blog: http://halr9000.com/article/464 Keep the ideas coming. |
|
So my project is public now! I'm working on "Managing VMWare with Windows PowerShell: TFM®". So LucD, some form of your request is going to be a part of my book. I can't promise it'll get done in time for it to be of any use to you personally though, but I'll try.
I'm very excited, this is the first book I've ever tried writing a book. In fact, I don't think I've written anything longer than a few pages before. At some point down the road I'll need technical reviewers, I may ask for volunteers then if anybody's interested. |
|
halr9000 wrote:So my project is public now! I'm working on "Managing VMWare with Windows PowerShell: TFM®". So LucD, some form of your request is going to be a part of my book. I can't promise it'll get done in time for it to be of any use to you personally though, but I'll try.
This is one book that will be on my must read list. Jason |
|
Thanks, both of you. And thanks bottledair for the ideas, much appreciated.
Hal Rottenberg Co-Host, PowerScripting Podcast (http://powerscripting.net) |
|
You might be able to do some of it, but the tasks which you can schedule in VC are fairly limited. I'm told you can schedule anything by using the SDK, and hence, the VI toolkit. I already have on my todo to see how easy/difficult it will be to schedule arbitrary tasks using powershell.
Hal Rottenberg Co-Host, PowerScripting Podcast (http://powerscripting.net) |
|
This is probably pretty simple to do in PowerShell (now that I've had a little time to play with it), but a list of Folders or Resource Pools (and Sub-Resource Pools) with a respective count of powered on/off and suspended VMs would be nice. Possibly an option to break down the counts by host. Next would be disk utilization (free/used/total space) for these same categories. I suspect we'll end up capturing a lot of the required information into an SQL Server database and use SQL to provide us with all of this, but it would be interesting to see if it's possible (and easy) to do it in PowerShell. We run a high-availability hosting company that leases resource pools with the ability for customers to create as many virtual machines as they want within their allocated resources (disk space is the limiting factor). I'm just thinking of quick commands that we could use to find problem areas. Eric K. Miller, Genesis Hosting Solutions, LLC http://www.genesishosting.com/ - Lease part of our ESX cluster! |
|
Mornin': I am working on learning PowerShell so I can better manage our VI environment. One of the very first things I am attempting to do is to document VI. Where are all the vm's, what is their configuration info (OS, Memory,# & type of disks), what storage each disk is on, etc, etc. PowerShell & VITK provides much of this as individual scriplets, but I want to provide a daily report on the structure. My 2 cents! And btw, I bought Windows PowerShell v2.0: TFM (2rd Edition) the other day and so far it is excellent... will plan on adding yours as soon as it is out and would love to preview any chapters, scripts, bring you coffee, whatever, to get a peek at it! Thanks! |
|
Yes, a daily report sounds good. Noted. And BTW, I'm not the author of that TFM book, that's Don Jones, whom I greatly respect.
Hal Rottenberg Co-Host, PowerScripting Podcast (http://powerscripting.net) |