I am trying to construct a deployment set of scripts. The environment is bringing in OEM systems pre-loaded with base vSphere but need script to automate a bunch of steps for vSwitch creation, MTU etc....
As such I built a deployment system for these steps using "VMWare POWERCLI"
I built this initially on Windows, but want to deploy this en-mass, so want to wrap this up as a "deployment system" for sites and to avoid License issues, want to convert it to work on CentOS.
So I figured it would be easy, develop on Windows then move scripts over to CentOS, launch power shell from within bash... call on pre-built VMWare POWERCLI scripts....
Step 1: Download and Install
From Linux system (Example CentOS 6) install package
[root@vsmgr00 ~]# cp /media/labfiles/Software/vmware/6/VMware-PowerCLI-6.3.0-3639347.oss.tgz /tmp/
[root@vsmgr00 ~]# cd /tmp/
[root@vsmgr00 tmp]# tar -zxvf VMware-PowerCLI-6.3.0-3639347.oss.tgz
Launch PowerCLI shell
Within Windows you just launch it and it works
Launch CLI Power Shell
Connect to vCenter. Example: vcenter.acme.com
Connect—CISeruer ucenter.acme.com Specify Credential Please specify vcenter.acme.com credenbal Password: " height="474" width="705">
1) What is the proper way to get Linux PowerCLI shell to launch?
2) Is the failure I am seeing due to CentOS Perl library, if so, why did it not check during install, and what is expected version?
I'm afraid you are mixing two different CLI here.
PowerCLI, which is an add-on for PowerShell can be used on Windows platforms.
The CLI you see to have installed on the Linux box, is a Perl based CLI.
And you can't use scripts from PowerCLI in a Perl shell I'm afraid.
Download location for single set of tools called "POWER CLI"
One a .exe (windows). One a tarball for 32bit. One a tarball for 64bit.
But not the same tool set?
Not able to use scripts written in common on one and used on another platform?
Are we sure on that statement? Because it does not make sense to me.