Project

General

Profile

Feature #1946

Addition VMWare options required for VM creation

Added by Brian Gupta almost 7 years ago. Updated almost 3 years ago.

Status:
Resolved
Priority:
Normal
Assignee:
-
Category:
VM management
Target version:
Difficulty:
Triaged:
No
Bugzilla link:
Pull request:
Fixed in Releases:
Found in Releases:

Description

Please add the options to select resource pool, guest operating system profile, more granular memory allocation (perhaps a slider + text field), and virtual scsi controller type.


Related issues

Related to Foreman - Feature #1945: Better VMWare support for non-clusters setupClosed
Related to Foreman - Feature #2355: Need ability to set VMware provisioning foundation - Network/SCSI/OS ProfileResolved2013-03-26
Related to Foreman - Feature #3496: SCSI Controller type selection for vSphereClosed2013-10-25
Related to Foreman - Feature #3910: for VMware compute resource (fog) give the option to add a cd drive to the created hostClosed2013-12-18
Related to Foreman - Feature #4380: [vSphere] allow selection of guest OSClosed2014-02-18
Related to Foreman - Feature #4533: Boot options configuration for VMware guestsNew2014-03-03
Related to Foreman - Feature #5760: Specify VM hardware version for new virtual hostsClosed2014-05-16
Related to Foreman - Feature #8295: Vcenter - Memory/CPU HotplugClosed2014-11-06
Related to Foreman - Feature #10889: [vSphere] Allow selection of resource poolClosed2015-06-20
Related to Foreman - Feature #10955: Support to set vmware configuration parametersNew2015-06-30
Related to Foreman - Feature #10956: Support to set vmware VM annotationsClosed2015-06-30
Related to Foreman - Feature #4509: Additional SCSI Controller with per-disk configurationClosed2014-02-28
Related to Foreman - Bug #9038: IDE Devices in vSphereNew2015-01-19

History

#1 Updated by Brian Gupta almost 7 years ago

  • Target version set to 1.1

#2 Updated by Drew Blessing almost 7 years ago

I think this request covers this but just want to note it to make sure it's considered.

If we are only supposed to add the actual VCenter server as a compute resource for provisioning, then the Virtual Machine options when setting up a new host really need to include a drop down for the specific host to install on. Not all VMware licenses have the VMotion and Storage VMotion or whatever it's called. So, not everyone can use the auto-migration of new hosts feature that I believe you must rely on in the current support.

If you can't provide a drop down to choose a host then it would also be acceptable to allow users to add a separate compute resource for each ESXi host individually. Then, the "Deploy on" option in the new host would be where you choose the specific host. Currently when you do this you can successfully add the computer resource but there is an error on the Virtual Machine tab in the new host screen.

I hope this makes sense. If not, let me know and I'll try to explain better. Thanks for your consideration.

#3 Updated by Ohad Levy over 6 years ago

Drew Blessing wrote:

I think this request covers this but just want to note it to make sure it's considered.

If we are only supposed to add the actual VCenter server as a compute resource for provisioning, then the Virtual Machine options when setting up a new host really need to include a drop down for the specific host to install on. Not all VMware licenses have the VMotion and Storage VMotion or whatever it's called. So, not everyone can use the auto-migration of new hosts feature that I believe you must rely on in the current support.

sure see #1945 - there is a simple workaround that would allow you to get that.

If you can't provide a drop down to choose a host then it would also be acceptable to allow users to add a separate compute resource for each ESXi host individually. Then, the "Deploy on" option in the new host would be where you choose the specific host. Currently when you do this you can successfully add the computer resource but there is an error on the Virtual Machine tab in the new host screen.

I hope this makes sense. If not, let me know and I'll try to explain better. Thanks for your consideration.

#4 Updated by Ohad Levy over 6 years ago

  • Target version changed from 1.1 to 1.2.0

#5 Updated by Marc Grimme over 6 years ago

I made some pull requests for fog to support things like:

  • querying for guest types (fog: servertypes)
  • querying for nic types (fog: interfacetypes) per guest type

This could be used to query for available guest types and the available nic types.
I also added a way to specify default nic_types in ~/.fog.
This could be used to at least change the default nic type which is currently E1000.

For the changes see:

Example:

To query for available guest types:
  • compute.datacenters.first.servertypes
  • compute.datacenters.first.servertypes.get("debian6Guest").interfacetypes

I don't know if this makes sense but it seams to be (at least for me) a logical dependency on how to get further with this requirements.

Hope this helps
Regards.

#6 Updated by Marc Grimme over 6 years ago

Now I also managed to make the appropriate changes for foreman vmware compute-resource to support user selecteable guesttypes and NIC interfacetypes.

See https://github.com/theforeman/foreman/pull/480.

I have not yet a clear idea on how to implement user defined storage adapters and how to map them to the volumes. This is still kind of open.

Hope this helps.

Let me know about feedback.

Regards Marc.

#7 Updated by Dominic Cleal over 6 years ago

  • Status changed from New to Ready For Testing

#8 Updated by Dominic Cleal over 6 years ago

  • Target version changed from 1.2.0 to 1.3.0

#9 Updated by Lukas Zapletal about 6 years ago

  • Target version deleted (1.3.0)

#10 Updated by Dominic Cleal almost 6 years ago

  • Related to Feature #3496: SCSI Controller type selection for vSphere added

#11 Updated by Angelo Lisco almost 6 years ago

In fog 1.16, thir relevant PR was merged:

[vSphere] Implementation of Query for Guesttype and NICTypes.
https://github.com/fog/fog/pull/1582

and hopefully this PR may appear in fog 1.17:

[vSphere] Implementation of feature to specify scsi_controller type at create type
https://github.com/fog/fog/pull/2314

Hope that soon vsphere/vmware will became a first class citizen in Foreman.
I'm scheduling a Cobbler to Foreman migration for our provisioning tasks.

#12 Updated by Dominic Cleal almost 6 years ago

  • Status changed from Ready For Testing to New

As per my note on the PR, the current Foreman 'develop' has diverged somewhat and gained bits of the functionality (e.g. NIC type selection) via other more targeted PRs. We'd still like to include the guest type support etc, so new PRs that can address this against current 'develop' would be most welcome.

#13 Updated by Josh Baird over 5 years ago

@Marc - would you mind submitting a new PR for the 'guest type' selection? Any other PR's that improve VMWare functionality would be much appreciated as well (allowing user to pick number of cores, SCSI controller type, etc).

#14 Updated by Ewoud Kohl van Wijngaarden over 5 years ago

  • Related to Feature #3910: for VMware compute resource (fog) give the option to add a cd drive to the created host added

#15 Updated by Dominic Cleal over 5 years ago

  • Related to Feature #4380: [vSphere] allow selection of guest OS added

#16 Updated by Dominic Cleal over 5 years ago

  • Related to Feature #4533: Boot options configuration for VMware guests added

#17 Updated by m w over 5 years ago

For what it is worth, this would be really useful for someone to add...

#18 Updated by Michael Moll about 5 years ago

  • Related to Feature #5760: Specify VM hardware version for new virtual hosts added

#19 Updated by Anthony Clark almost 5 years ago

I'd like to add my vote for adding a drop-down to choose a resource pool in a cluster in VMware.

#20 Updated by Michael Moll almost 5 years ago

#21 Updated by Friedrich Seifts almost 5 years ago

+1 for memory/cpu hotplug and being able to choose the resource pool.

#22 Updated by Virgil Chereches over 4 years ago

+1 for ability to choose resource pools

#23 Updated by Arnold Bechtoldt over 4 years ago

  • Related to Feature #10889: [vSphere] Allow selection of resource pool added

#24 Updated by Wolfram Strauss about 4 years ago

  • Related to Feature #10955: Support to set vmware configuration parameters added

#25 Updated by Wolfram Strauss about 4 years ago

  • Related to Feature #10956: Support to set vmware VM annotations added

#26 Updated by Michael Moll over 3 years ago

  • Related to Feature #4509: Additional SCSI Controller with per-disk configuration added

#27 Updated by Michael Moll over 3 years ago

  • Related to Bug #9038: IDE Devices in vSphere added

#28 Updated by Marek Hulán about 3 years ago

  • Target version set to 115

#29 Updated by Marek Hulán about 3 years ago

  • Target version changed from 115 to 1.6.0

#30 Updated by Marek Hulán about 3 years ago

  • Target version changed from 1.6.0 to 1.5.3

#31 Updated by Marek Hulán almost 3 years ago

  • Target version changed from 1.5.3 to 1.5.0

#32 Updated by Marek Hulán almost 3 years ago

  • Status changed from New to Resolved

I believe all items from the list are now implemented. Please let us know if something is missing. We would prefer to solve additional features through separate issues.

Also available in: Atom PDF