Has there been any progress wrt support for provisioning VMs on an ESXi
host? Still using cobbler+vMA+custom to provision new VMs. Would really
like to replace all that with foreman if possible.
Thanks!
Ryan
Yes, the recently released v1.1 has support for creating vsphere (esxi)
VM's.
···
On Sun, Feb 10, 2013 at 6:24 PM, Ryan Bowlby wrote:Has there been any progress wrt support for provisioning VMs on an ESXi
host? Still using cobbler+vMA+custom to provision new VMs. Would really
like to replace all that with foreman if possible.
–
Romeo
Does this new functionality in 1.1 still need vCenter to create the VMs or
can it be done without it?
Cheers,
Charlie
···
On Sat, Feb 16, 2013 at 10:46 AM, Alexandros Tsourakis wrote:That’s sweet!
Are there any instructions for this?
Cheers,
Alex.On Monday, 11 February 2013 06:17:35 UTC+1, Romeo Theriault wrote:
On Sun, Feb 10, 2013 at 6:24 PM, Ryan Bowlby rbow...@gmail.com **wrote:
Has there been any progress wrt support for provisioning VMs on an ESXi
host? Still using cobbler+vMA+custom to provision new VMs. Would really
like to replace all that with foreman if possible.Yes, the recently released v1.1 has support for creating vsphere (esxi)
VM’s.–
Romeo–
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?hl=en.
For more options, visit https://groups.google.com/groups/opt_out.
No, you can provision on vSphere directly from 1.1. Just add a new VmWare compute resource.
···
Sent from my iPhoneOn Feb 16, 2013, at 1:04 PM, Charlie Derwent shelltoesuperstar@gmail.com wrote:
Does this new functionality in 1.1 still need vCenter to create the VMs or can it be done without it?
Cheers,
CharlieOn Sat, Feb 16, 2013 at 10:46 AM, Alexandros Tsourakis alex.tsr@gmail.com wrote:
That’s sweet!
Are there any instructions for this?
Cheers,
Alex.On Monday, 11 February 2013 06:17:35 UTC+1, Romeo Theriault wrote:
On Sun, Feb 10, 2013 at 6:24 PM, Ryan Bowlby rbow...@gmail.com wrote:
Has there been any progress wrt support for provisioning VMs on an ESXi host? Still using cobbler+vMA+custom to provision new VMs. Would really like to replace all that with foreman if possible.
Yes, the recently released v1.1 has support for creating vsphere (esxi) VM’s.
–
Romeo–
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?hl=en.
For more options, visit https://groups.google.com/groups/opt_out.–
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?hl=en.
For more options, visit https://groups.google.com/groups/opt_out.
I got foreman 1.1 with vSphere 5.1.0a running. As long as you are using an
English Version of VMWare and VMware vCenter Server everything should work
just fine.
For the usage of the console in foreman you'll need to follow the
instructions here
http://www.virtuallyghetto.com/2012/01/using-vnc-client-to-connect-to-vms-in.html.
Apply it to all VMware ESXi Hosts.
I couldn't get foreman using just the VMware ESXi Hosts. It always
complaining about a cluster attribute that is required for creation of a
machine (seems to be some issue with the compute_resource implementation).
I still have two issues that I'm thinking about.
- The machine to be created gets a strange type by default. So if you
create a machine with RHEL6 as OS the vm won't be type Red Hat Enterprise
Server 6. I don't know if this is an issue but it will irritate some VMware
guys. - The default NIC type is E1000 for all new NICs. E1000 is not very
performant on network loaded vms (latency and bandwith). So it should be
possible to change the NIC type (ideal on NIC bases).
Hope this helps.
Regards Marc.
···
Am Samstag, 16. Februar 2013 19:28:44 UTC+1 schrieb Josh: > > No, you can provision on vSphere directly from 1.1. Just add a new > VmWare compute resource. > > Sent from my iPhone > > On Feb 16, 2013, at 1:04 PM, Charlie Derwent <shelltoe...@gmail.com> > wrote: > > Does this new functionality in 1.1 still need vCenter to create the VMs or > can it be done without it? > > Cheers, > Charlie > > > On Sat, Feb 16, 2013 at 10:46 AM, Alexandros Tsourakis <alex...@gmail.com > > wrote: > >> That's sweet! >> >> Are there any instructions for this? >> >> Cheers, >> Alex. >> >> On Monday, 11 February 2013 06:17:35 UTC+1, Romeo Theriault wrote: >>> >>> On Sun, Feb 10, 2013 at 6:24 PM, Ryan Bowlby ** >>> wrote: >>> >>> Has there been any progress wrt support for provisioning VMs on an ESXi >>>> host? Still using cobbler+vMA+custom to provision new VMs. Would really >>>> like to replace all that with foreman if possible. >>> >>> >>> Yes, the recently released v1.1 has support for creating vsphere (esxi) >>> VM's. >>> >>> >>> -- >>> Romeo >>> >> -- >> 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-user...@googlegroups.com . >> To post to this group, send email to forema...@googlegroups.com >> . >> Visit this group at http://groups.google.com/group/foreman-users?hl=en. >> For more options, visit https://groups.google.com/groups/opt_out. >> >> >> > > -- > 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-user...@googlegroups.com . > To post to this group, send email to forema...@googlegroups.com > . > Visit this group at http://groups.google.com/group/foreman-users?hl=en. > For more options, visit https://groups.google.com/groups/opt_out. > > > >> I got foreman 1.1 with vSphere 5.1.0a running. As long as you are using an English Version of VMWare and VMware vCenter Server everything should work just fine.
> For the usage of the console in foreman you'll need to follow the instructions here http://www.virtuallyghetto.com/2012/01/using-vnc-client-to-connect-to-vms-in.html. Apply it to all VMware ESXi Hosts.
>
> I couldn't get foreman using just the VMware ESXi Hosts. It always complaining about a cluster attribute that is required for creation of a machine (seems to be some issue with the compute_resource implementation).
>
> I still have two issues that I'm thinking about.
> 1. The machine to be created gets a strange type by default. So if you create a machine with RHEL6 as OS the vm won't be type Red Hat Enterprise Server 6. I don't know if this is an issue but it will irritate some VMware guys.
VMware guy speaking: this needs to be set correctly otherwise vmware tools will have some issues.
This is a bug, please create a new ticket as the vSphere API allows us to set this option.
> 2. The default NIC type is E1000 for all new NICs. E1000 is not very performant on network loaded vms (latency and bandwith). So it should be possible to change the NIC type (ideal on NIC bases).
This is probably because E1000 is one of the few NIC choices that supports PXE booting. The OS being installed usually doesn't have the "good NIC" driver until after the OS and vmware tools are installed. So because of this driver issue we need to use a legacy NIC driver that is found in almost all kernels.
There is probably a similar issue with SCSI driver type too.
Thanks,
Corey Osman
corey@logicminds.biz
Green IT and Data Center Automation Specialist