« A Closer Look at PowerVC | Main | Following Up on the Technical University Event »

November 12, 2013


If you are, for instance, building a new custom VM for the first time you'd be crazy not to use the HMC GUI.

On the other hand, if you have to build dozens of them, you'd be crazy not to script the HMC CLI.

Same thing for dLPAR operations, once you've done it more than a few times using the GUI it's easily worth digging out the chsyscfg and chhwres commands.

You don't have to go that far to find these conflicts - just think about smitty Vs pure ksh command execution (I still see a lot of people increasing filesystems from smitty). For them it's safer (less chance of a miss-typed command) and officially supported too. Of course these people never tried to do the same 1000 times in a row, so they never had to learn why scripting could be beneficial.
And back to the HMC Vs VIO question: I have a few environments that are behind 2 firewalls and I have absolutely no access to the HMC WebGUI - I have to use SSH in order to manage anything related to LPAR management. And if you do not have a WebGUI to HMC, you can not "simply" click those things together either: You could use the viosvrcmd command from HMC (and learn to use it), or login to the VIOS and use the same commands that you could use from the HMC console regardless :))

The comments to this entry are closed.