vmrun can be installed on a Foreman Smart-Proxy (AKA Sat6 capsule) host and
run any command or script INSIDE of a guest VM running on a
vCenter computing resource - i
*.e. it can configure whatever, including network interfaces. *
in order to run something inside of VM - vmrun only need to
know (beside of vCenter credentials of course)
path to .VMX file (already known after VM provisioning)
- guest OS username (i.e. root, administrator) and password
- command line or script name to be executed
In fact VIX API and vmrun can do way more that this - I feel it simply must
be integrated into Foreman Proxy.
I’ve been using it for various VCenter related automation tasks and like
it’s versatility and power.
+1 to supporting this, I could see a lot of use for this downstream as well
with so many customers running VMware.
···
On Monday, October 16, 2017 at 2:40:56 PM UTC-4, Evgeny Vasilchenko wrote:
>
> I'd like to share an idea for provisioning of VMware guest VM's with
> Foreman.
>
> The idea required programming new type of Foreman proxy - unfortunately, I
> neither have time or enough skills for that.
>
> *The goal:*
>
> - Allow configuration of Linux (and maybe Windows) VM network
> interfaces with VMWare VIX's API
> instead of DHCP
>
> *Facts:*
>
> - VMWare offers a free VM management API called *VIX* -
> https://blogs.vmware.com/vix/2008/07/what-is-vix-and.html
> - *VIX is an API that lets you programmatically control the
> products that host VMware VMs, and control the VMs themselves.*
> - it works with many VMWare products including vCenter
> -
> - VIX package can be installed on both
>
> *Linux and Windows *
> - VIX has a wrapper utility called *vmrun* (
> https://www.vmware.com/support/developer/vix-api/vix112_vmrun_command.pdf)
> which offers a CLI for controlling VM's running - e.g. starting, stopping,
> pausing, deleting, etc...
>
> - vmrun can be installed on a *Foreman Smart-Proxy* (AKA Sat6 capsule)
> *host* and
> - run any command or script *INSIDE* of a guest VM running on a
> vCenter computing resource - i
>
> *.e. it can configure whatever, including network interfaces. *
> - in order to run something inside of VM - vmrun only need to
> know (beside of vCenter credentials of course)
> - *path to .VMX file* (already known after VM provisioning)
> - guest OS username (i.e. root, administrator) and password
> - command line or script name to be executed
>
> In fact VIX API and vmrun can do way more that this - I feel it simply
> must be integrated into Foreman Proxy.
> I've been using it for various VCenter related automation tasks and like
> it's versatility and power.
>
> Any ideas?
>
>
>
>
Would a VMware VIX backend to Remote Execution be feasable and useful?
···
On Mon, Oct 16, 2017 at 11:39:56AM -0700, Evgeny Vasilchenko wrote:
>I'd like to share an idea for provisioning of VMware guest VM's with
>Foreman.
>
>The idea required programming new type of Foreman proxy - unfortunately, I
>neither have time or enough skills for that.
>
>*The goal:*
>
> - Allow configuration of Linux (and maybe Windows) VM network interfaces
> with VMWare VIX's API
> instead of DHCP
>
>*Facts:*
>
> - VMWare offers a free VM management API called *VIX*
> - https://blogs.vmware.com/vix/2008/07/what-is-vix-and.html
> - *VIX is an API that lets you programmatically control the products
> that host VMware VMs, and control the VMs themselves.*
> - it works with many VMWare products including vCenter
> -
>- VIX package can be installed on both
>
>*Linux and Windows *
> - VIX has a wrapper utility called *vmrun*
> (https://www.vmware.com/support/developer/vix-api/vix112_vmrun_command.pdf)
> which offers a CLI for controlling VM's running - e.g. starting, stopping,
> pausing, deleting, etc...
>
> - vmrun can be installed on a *Foreman Smart-Proxy* (AKA Sat6 capsule)
> *host* and
> - run any command or script *INSIDE* of a guest VM running on a
> vCenter computing resource - i
>
>*.e. it can configure whatever, including network interfaces. *
> - in order to run something inside of VM - vmrun only need to
> know (beside of vCenter credentials of course)
> - *path to .VMX file* (already known after VM provisioning)
> - guest OS username (i.e. root, administrator) and password
> - command line or script name to be executed
>
>In fact VIX API and vmrun can do way more that this - I feel it simply must
>be integrated into Foreman Proxy.
>I've been using it for various VCenter related automation tasks and like
>it's versatility and power.
>
>Any ideas?
Could you please list things that VIX allows and can't be achieved with
current fog adapter? I'd like to avoid supporting 2 ways to talk to vmware
and I don't think it makes sense to rewrite what we have unless there are
some big benefits.
VIX is an API that lets you programmatically control the
products that host VMware VMs, and control the VMs themselves.
it works with many VMWare products including vCenter
VIX package can be installed on both
*Linux and Windows *
VIX has a wrapper utility called vmrun ( Broadcom Inc. | Connecting Everything)
which offers a CLI for controlling VM’s running - e.g. starting, stopping,
pausing, deleting, etc…
vmrun can be installed on a Foreman Smart-Proxy (AKA Sat6 capsule) host and
run any command or script INSIDE of a guest VM running on a
vCenter computing resource - i
*.e. it can configure whatever, including network interfaces. *
in order to run something inside of VM - vmrun only need to
know (beside of vCenter credentials of course)
path to .VMX file (already known after VM provisioning)
- guest OS username (i.e. root, administrator) and password
- command line or script name to be executed
In fact VIX API and vmrun can do way more that this - I feel it simply
must be integrated into Foreman Proxy.
I’ve been using it for various VCenter related automation tasks and like
it’s versatility and power.
