Failed to create a compute esx instance

Support
1

Hi,

I am doing a small POC on using foreman to provision linux vms on ESXi 5.5.

I am running just one standalone ESXi server (no vcenter / cluster of hosts
etc) and when I come to configure the new vm compute resource in foreman on
the Virtual Machine tab the cluster option appears to be mandatory and when
I click submit I get the following:

"Unable to Save
Failed to create a compute esx (VMWare) instance <hostname>: cluster is
required for this operation"

I dont have a cluster setup as I only have the one esxi server, is there
anyway around this on the foreman side so cluster isn't mandatory?

Thanks,
Andy.

2

After some more searching around I found this:

http://projects.theforeman.org/issues/1945

Which talks about this hack to get around the issue:

diff --git a/lib/fog/vsphere/requests/compute/list_clusters.rb b/lib/fog/vsphere/requests/compute/list_clusters.rbindex 2092213…55980c7 100644— a/lib/fog/vsphere/requests/compute/list_clusters.rb+++ b/lib/fog/vsphere/requests/compute/list_clusters.rb@@ -11,7 +11,7 @@ module Fog
end

     def raw_clusters(datacenter)-          find_raw_datacenter(datacenter).hostFolder.childEntity.grep(RbVmomi::VIM::ClusterComputeResource)+          find_raw_datacenter(datacenter).hostFolder.childEntity.grep(RbVmomi::VIM::ComputeResource)
     end

This has got me a step further I think but now I get:

"Unable to save
mac value is blank"

But on the network tab there is no field to put in a mac address…?

··· On Monday, 10 February 2014 15:10:34 UTC, Andrew Holford wrote: > > Hi, > > I am doing a small POC on using foreman to provision linux vms on ESXi 5.5. > > I am running just one standalone ESXi server (no vcenter / cluster of > hosts etc) and when I come to configure the new vm compute resource in > foreman on the Virtual Machine tab the cluster option appears to be > mandatory and when I click submit I get the following: > > "Unable to Save > Failed to create a compute esx (VMWare) instance : cluster is > required for this operation" > > I dont have a cluster setup as I only have the one esxi server, is there > anyway around this on the foreman side so cluster isn't mandatory? > > Thanks, > Andy. >
3

I can relate. I am still stuck here.
My problem is that I don't mind running vcenter, its just that in my home
lab, its just a waste of resources (I have 2 16GB boxes, but run many VMs).
I was thinking I'd just stand it up on my laptop, provision, then shut it
down, but that seems like a waste. The hack from 1945 gets me further, but
I am also stuck with the no MAC address issue. Does anyone have any ideas?
It seems like whatever service that queries vcenter for the newly created
VMs MAC address doesn't work if the request doesn't go to a VCenter/Cluster
box.

··· On Monday, February 10, 2014 11:10:34 PM UTC+8, Andrew Holford wrote: > > Hi, > > I am doing a small POC on using foreman to provision linux vms on ESXi 5.5. > > I am running just one standalone ESXi server (no vcenter / cluster of > hosts etc) and when I come to configure the new vm compute resource in > foreman on the Virtual Machine tab the cluster option appears to be > mandatory and when I click submit I get the following: > > "Unable to Save > Failed to create a compute esx (VMWare) instance : cluster is > required for this operation" > > I dont have a cluster setup as I only have the one esxi server, is there > anyway around this on the foreman side so cluster isn't mandatory? > > Thanks, > Andy. >
4

Andrew,

I got this working by making my ESXI instances a cluster (patch never worked for me) but i'd really like to see the ability
to work with individual compute nodes as separate compute resources so you can choose where a new VM would live.
(Or ideally foreman would choose based on available resources amongst all of the ESXI compute resources) Are there any plans to
make the vmware support more robust?

··· On Mon, Feb 10, 2014 at 09:02:36AM -0800, Andrew Holford wrote: > After some more searching around I found this: > > http://projects.theforeman.org/issues/1945 > > Which talks about this hack to get around the issue: > > > diff --git a/lib/fog/vsphere/requests/compute/list_clusters.rb b/lib/fog/vsphere/requests/compute/list_clusters.rb > index 2092213..55980c7 100644 > --- a/lib/fog/vsphere/requests/compute/list_clusters.rb > +++ b/lib/fog/vsphere/requests/compute/list_clusters.rb > @@ -11,7 +11,7 @@ module Fog > end > > def raw_clusters(datacenter) > - find_raw_datacenter(datacenter).hostFolder.childEntity.grep(RbVmomi::VIM::ClusterComputeResource) > + find_raw_datacenter(datacenter).hostFolder.childEntity.grep(RbVmomi::VIM::ComputeResource) > end > > > This has got me a step further I think but now I get: > > "Unable to save > mac value is blank" > > But on the network tab there is no field to put in a mac address......? > On Monday, 10 February 2014 15:10:34 UTC, Andrew Holford wrote: > > Hi, > > I am doing a small POC on using foreman to provision linux vms on ESXi 5.5. > > I am running just one standalone ESXi server (no vcenter / cluster of hosts > etc) and when I come to configure the new vm compute resource in foreman on > the Virtual Machine tab the cluster option appears to be mandatory and when > I click submit I get the following: > > "Unable to Save > Failed to create a compute esx (VMWare) instance : cluster is > required for this operation" > > I dont have a cluster setup as I only have the one esxi server, is there > anyway around this on the foreman side so cluster isn't mandatory? > > Thanks, > Andy.

–

Bryan G. Seitz

5

Hi,

I thought about that but for now I just have the one esxi server and no
cluster.

I will let you know if I get any further.

Cheers,
Andy.

··· On Monday, 10 February 2014 17:07:30 UTC, Bryan Seitz wrote: > > > > > On Mon, Feb 10, 2014 at 09:02:36AM -0800, Andrew Holford wrote: > > After some more searching around I found this: > > > > http://projects.theforeman.org/issues/1945 > > > > Which talks about this hack to get around the issue: > > > > > > diff --git a/lib/fog/vsphere/requests/compute/list_clusters.rb > b/lib/fog/vsphere/requests/compute/list_clusters.rb > > index 2092213..55980c7 100644 > > --- a/lib/fog/vsphere/requests/compute/list_clusters.rb > > +++ b/lib/fog/vsphere/requests/compute/list_clusters.rb > > @@ -11,7 +11,7 @@ module Fog > > end > > > > def raw_clusters(datacenter) > > - > find_raw_datacenter(datacenter).hostFolder.childEntity.grep(RbVmomi::VIM::ClusterComputeResource) > > > + > find_raw_datacenter(datacenter).hostFolder.childEntity.grep(RbVmomi::VIM::ComputeResource) > > > end > > > > > > This has got me a step further I think but now I get: > > > > "Unable to save > > mac value is blank" > > > > But on the network tab there is no field to put in a mac address......? > > On Monday, 10 February 2014 15:10:34 UTC, Andrew Holford wrote: > > > > Hi, > > > > I am doing a small POC on using foreman to provision linux vms on > ESXi 5.5. > > > > I am running just one standalone ESXi server (no vcenter / cluster > of hosts > > etc) and when I come to configure the new vm compute resource in > foreman on > > the Virtual Machine tab the cluster option appears to be mandatory > and when > > I click submit I get the following: > > > > "Unable to Save > > Failed to create a compute esx (VMWare) instance : > cluster is > > required for this operation" > > > > I dont have a cluster setup as I only have the one esxi server, is > there > > anyway around this on the foreman side so cluster isn't mandatory? > > > > Thanks, > > Andy. > > Andrew, > > I got this working by making my ESXI instances a cluster (patch never > worked for me) but i'd really like to see the ability > to work with individual compute nodes as separate compute resources so you > can choose where a new VM would live. > (Or ideally foreman would choose based on available resources amongst all > of the ESXI compute resources) Are there any plans to > make the vmware support more robust? > > -- > > Bryan G. Seitz >
6

This would be pretty cool. You are essentially moving some of vCenter's
features into Foreman which would be useful for people who had bunches of
independent non-clustered hosts.

Josh

··· On Mon, Feb 10, 2014 at 12:07 PM, Bryan Seitz wrote:

On Mon, Feb 10, 2014 at 09:02:36AM -0800, Andrew Holford wrote:

After some more searching around I found this:

Feature #1945: Better VMWare support for non-clusters setup - Foreman

Which talks about this hack to get around the issue:

diff --git a/lib/fog/vsphere/requests/compute/list_clusters.rb
b/lib/fog/vsphere/requests/compute/list_clusters.rb
index 2092213…55980c7 100644
— a/lib/fog/vsphere/requests/compute/list_clusters.rb
+++ b/lib/fog/vsphere/requests/compute/list_clusters.rb
@@ -11,7 +11,7 @@ module Fog
end

     def raw_clusters(datacenter)

find_raw_datacenter(datacenter).hostFolder.childEntity.grep(RbVmomi::VIM::ClusterComputeResource)

find_raw_datacenter(datacenter).hostFolder.childEntity.grep(RbVmomi::VIM::ComputeResource)

     end

This has got me a step further I think but now I get:

“Unable to save
mac value is blank”

But on the network tab there is no field to put in a mac address…?
On Monday, 10 February 2014 15:10:34 UTC, Andrew Holford wrote:

Hi,

I am doing a small POC on using foreman to provision linux vms on

ESXi 5.5.

I am running just one standalone ESXi server (no vcenter / cluster

of hosts

etc) and when I come to configure the new vm compute resource in

foreman on

the Virtual Machine tab the cluster option appears to be mandatory

and when

I click submit I get the following:

"Unable to Save
   Failed to create a compute esx (VMWare) instance <hostname>:

cluster is

required for this operation"

I dont have a cluster setup as I only have the one esxi server, is

there

anyway around this on the foreman side so cluster isn't mandatory?

Thanks,
Andy.

Andrew,

I got this working by making my ESXI instances a cluster (patch never
worked for me) but i’d really like to see the ability
to work with individual compute nodes as separate compute resources so you
can choose where a new VM would live.
(Or ideally foreman would choose based on available resources amongst all
of the ESXI compute resources) Are there any plans to
make the vmware support more robust?

–

Bryan G. Seitz

–
You received this message because you are subscribed to the Google Groups
“Foreman users” group.
To unsubscribe from this group and stop receiving emails from it, send an
email to foreman-users+unsubscribe@googlegroups.com.
To post to this group, send email to foreman-users@googlegroups.com.
Visit this group at http://groups.google.com/group/foreman-users.
For more options, visit https://groups.google.com/groups/opt_out.

7

Did you ever make any more process on this Andrew?

··· On Monday, February 10, 2014 12:15:19 PM UTC-5, Andrew Holford wrote: > > Hi, > > I thought about that but for now I just have the one esxi server and no > cluster. > > I will let you know if I get any further. > > Cheers, > Andy. > > On Monday, 10 February 2014 17:07:30 UTC, Bryan Seitz wrote: >> >> >> >> >> On Mon, Feb 10, 2014 at 09:02:36AM -0800, Andrew Holford wrote: >> > After some more searching around I found this: >> > >> > http://projects.theforeman.org/issues/1945 >> > >> > Which talks about this hack to get around the issue: >> > >> > >> > diff --git a/lib/fog/vsphere/requests/compute/list_clusters.rb >> b/lib/fog/vsphere/requests/compute/list_clusters.rb >> > index 2092213..55980c7 100644 >> > --- a/lib/fog/vsphere/requests/compute/list_clusters.rb >> > +++ b/lib/fog/vsphere/requests/compute/list_clusters.rb >> > @@ -11,7 +11,7 @@ module Fog >> > end >> > >> > def raw_clusters(datacenter) >> > - >> find_raw_datacenter(datacenter).hostFolder.childEntity.grep(RbVmomi::VIM::ClusterComputeResource) >> >> > + >> find_raw_datacenter(datacenter).hostFolder.childEntity.grep(RbVmomi::VIM::ComputeResource) >> >> > end >> > >> > >> > This has got me a step further I think but now I get: >> > >> > "Unable to save >> > mac value is blank" >> > >> > But on the network tab there is no field to put in a mac address......? >> > On Monday, 10 February 2014 15:10:34 UTC, Andrew Holford wrote: >> > >> > Hi, >> > >> > I am doing a small POC on using foreman to provision linux vms on >> ESXi 5.5. >> > >> > I am running just one standalone ESXi server (no vcenter / cluster >> of hosts >> > etc) and when I come to configure the new vm compute resource in >> foreman on >> > the Virtual Machine tab the cluster option appears to be mandatory >> and when >> > I click submit I get the following: >> > >> > "Unable to Save >> > Failed to create a compute esx (VMWare) instance : >> cluster is >> > required for this operation" >> > >> > I dont have a cluster setup as I only have the one esxi server, is >> there >> > anyway around this on the foreman side so cluster isn't mandatory? >> > >> > Thanks, >> > Andy. >> >> Andrew, >> >> I got this working by making my ESXI instances a cluster (patch never >> worked for me) but i'd really like to see the ability >> to work with individual compute nodes as separate compute resources so >> you can choose where a new VM would live. >> (Or ideally foreman would choose based on available resources amongst all >> of the ESXI compute resources) Are there any plans to >> make the vmware support more robust? >> >> -- >> >> Bryan G. Seitz >> >