john_lauro
Contributor
Contributor

vmware-cmd over 15 minutes via vcenter

New to VMA...  Fresh install of the appliance  vMA-5.5.0.1-1663088.

Running:

vi-admin@localhost:~> time vmware-cmd -H vcenter.ces.cvnt.net -U root -P xxx -h vm3.ces.cvnt.net -l

...  (about 23 entries)

real    16m24.956s

user    15m35.606s

sys     0m2.792s

If I skip vcenter, things are reasonable:

vi-admin@localhost:~> time vmware-cmd -U root -P yyy -H vm3.ces.cvnt.net -l  

...

real    0m2.423s

user    0m1.996s

sys     0m0.040s

Connecting vcenter server with sphere client is fine.  Running the appliance version of vcenter if that makes a difference.

0 Kudos
1 Reply
john_lauro
Contributor
Contributor

I started looking at the code on vmware-cmd, and it's rather poorly disigned.  It actually ends of pulling all configurations over all servers but filters the hosts as pulls them instead of only grabbing info from the requested host.  There weird thing is it goes to all that trouble to pull all configurations, and doesn't even have an option to not specify a host so that you can actually get all configurations at once.  It also seems to do it rather inefficiently, possibly even going to remote data centers instead of getting data from vcenter. Powercli seems to work much better, other than I don't want to use windows or power shell...  Is there something that works better than vmware-cmd (broken for large non local deployments), and that is script-able under linux?

0 Kudos