I'm working for a company that is using VMware estate quite extensively.
We're now in the phase of deploying a tool that is going to ease the
provisioning and management of hosts in one single place. Foreman looks the
best fit for our purpose but sadly the VMware support (like editing VM
options once a host has been created) is not fully developed. From my talks
up to that moment with some of the devs I know that you're basically
lacking a VMware infrastructure to test on. This is why I convinced the
management of the company to donate a slice of our VMware infrastructure to
the Foreman project. If any one of you is up for this as-well we can
clarify the details later on.
This is great news! I hope this will help Foreman's VMWare support mature
in the future. I do agree that it is lacking.
Josh
···
On Thu, Sep 3, 2015 at 10:44 AM, Martin Dobrev wrote:
Hi,
I’m working for a company that is using VMware estate quite extensively.
We’re now in the phase of deploying a tool that is going to ease the
provisioning and management of hosts in one single place. Foreman looks the
best fit for our purpose but sadly the VMware support (like editing VM
options once a host has been created) is not fully developed. From my talks
up to that moment with some of the devs I know that you’re basically
lacking a VMware infrastructure to test on. This is why I convinced the
management of the company to donate a slice of our VMware infrastructure to
the Foreman project. If any one of you is up for this as-well we can
clarify the details later on.
> Hi,
>
> I'm working for a company that is using VMware estate quite extensively.
> We're now in the phase of deploying a tool that is going to ease the
> provisioning and management of hosts in one single place. Foreman looks the
> best fit for our purpose but sadly the VMware support (like editing VM
> options once a host has been created) is not fully developed. From my talks
> up to that moment with some of the devs I know that you're basically
> lacking a VMware infrastructure to test on. This is why I convinced the
> management of the company to donate a slice of our VMware infrastructure to
> the Foreman project. If any one of you is up for this as-well we can
> clarify the details later on.
Thanks, that's very generous of you. Shlomi (another foreman dev) has
provided me some VMWare infra recently I use to develop stuff, from the
development point of view I don't have a problem.
I was thinking we could have at least something like this bats test[1]
we have for libvirt, but for VMWare. As long as we can pass some
parameter to the bats test with the VMWare credentials/URL that ought to
be fine. Is this something acceptable, or would there be any other use you'd
prefer?
···
On 09/03, Martin Dobrev wrote:
>
> Have a lovely day/evening,
> Martin
>
> --
> You received this message because you are subscribed to the Google Groups "foreman-dev" group.
> To unsubscribe from this group and stop receiving emails from it, send an email to foreman-dev+unsubscribe@googlegroups.com.
> For more options, visit https://groups.google.com/d/optout.
I should note that this isn't finished, it isn't running on ci.theforeman.org like our other tests.
Testing compute resources via foreman-bats is an inefficient way to
exercise the functionality too, we ought to prefer writing tests for
(ruby-libvirt|rbvmomi), Fog and/or Foreman itself to decrease distance
between the code under test and the tests.
···
On 08/09/15 12:22, Daniel Lobato Garcia wrote:
> I was thinking we could have at least something like this bats test[1]
> we have for libvirt, but for VMWare. As long as we can pass some
> parameter to the bats test with the VMWare credentials/URL that ought to
> be fine. Is this something acceptable, or would there be any other use you'd
> prefer?
>
> [1] https://github.com/theforeman/foreman-bats/blob/master/fb-setup-libvirt.bats
