This topic is a work in progress. I have not made foreman work with ESX server 100%25 but I wanted to at least copy my notes here for others to hack away at.
Although ESX and ESXi are different products they should be considered identical when it comes to working with the Vmware SDK.
Furthermore, vSphere is almost identical to ESX SDK with the exception that vSphere has additional objects and actions available to choose from when using the SDK.
All of these "ESX" products implement the [[http://www.vmware.com/support/developer/vc-sdk/]Vsphere SDK] through Https
- libvirt 0.8.3+ (not totally sure on this) but I know it doesn't work with 0.8.1
- ESX, ESXi, vsphere server, VMware Server
- A CA (Certificate Authority) to sign new certificates (psst, use your puppet CA or other CA you might have)
- RHEL6 or CentOS6 (not required but its what I use)
- Install libvirt
- Create ssl key
- Sign key with CA cert and CA key
- Transfers these keys to your ESX or Vsphere server
I tried various versions. The latest has too many dependancies so I stuck with 0.9.1 which is perfect for what I need.
I have compiled some RPMs to make it easier to install but you may need to resolve some additional dependancies.
This shouldn't be too bad if you have the EPEL repo.
You will need to use the following to install all the rpms once downloaded.
yum -y --nogpgcheck localinstall libvirt-*
rpm -Uvh libvirt-*