Well, actually its day 4 now so I’m a bit behind in the blogging. Don’t worry I’ve made copious notes of the various things I’ve done. So there will be blogfest offline on the plane if the in flight movie options don’t do it for me.
So you know powersHell and the PowerCLI right? No? OK, don’t worry about that – I’ve got something in the pipeline planed that will act as a door opener for all those who have yet to dip their toe into the powersHell waters. For those you have. The news is that were will be a new version of PowerCLI – 4.1 by the end of the year. Expect all so that then there will be ESX4.1/vCenter4.1 release. More or less the powerCLI development is dictated by the release strategy of the platform it manages.
I forget exactly the current number of PowerCLI command lets (150/160) but even more will be added into the PowerCLI at the 4.1 release. Including cmdlet to handle iSCIS (Yeah!!!) and to handle the NIC Teaming Policy Settings (Double-yeah) all of which require good knowledge of the SDK, a map and torch OR alternatively you download mine or any number of other bloggers PS sample and pretend your boss you did it all by yourself. WE KNOW WHO YOU ARE!
Also on show was a demo of Onxy, which has been put together by the Bulgian Dev team inside VMware [These guys are truely international!]. The demo wasn’t much more than what shown on the VMW site – which embedded into my blog a couple of days ago. In case you haven’t see it yet, Onxy is like a macro recorder which sits between the vSphere Client and vCenter “recording” all your interactions – leaving you with a cut and paste job on the PS code window.
I made a point of attending the session so I could hand in my business card (actually tore strip of my paper keycard from the Marriot, and wrote my name on it) to be entered into a lotto to join the Alpha programme. Some of the PowerShell Gurus like LucD and Hal Rottenberg were a little word that exposing the SDK so easily might be a little “dangerous” in the wrong hands. But personally, the cmdlets can do as much (if not more) damage before you even get to the SDK. For instance I could write powersHell that shutdown all your VMs, deleted them and then your datastore. The only thing stopping that is a little old thing called a username and password.
Also on show was www.thevesi.org (free community supported product the brain child of VizionCore and Scott Herold – my co-author on the Vi3 book). Its much higher level version of the PowerGUI front end. Like Onyx, VESI gives you a graphic front-end (not the vSphere client) which carries many “bulk admin” tasks – and leaves you with a PS window ready to be cut & pasted into a PS1 file. I was quite empressed by the VESI. Especially the chart and VISO output features. It’s the kind of thing some folks wind-up paying for, whilst the VESI is for free…