Feature #18064
closed
Ability to import and provision existing VMs
Added by Timo Goebel almost 8 years ago.
Updated over 6 years ago.
Category:
Compute resources
|
Description
It should be possible to create new hosts by importing an existing VM into Foreman. It could be done similar to the clone action of a host, but triggered from the VM listing in the compute resources show page. The attributes provided by the compute resource should be imported.
The use case is, that you might not be able to create your VM through Foreman (because of internal policies, special configuration needs, ...) but still want to use Foreman to install the VM.
- Status changed from New to Ready For Testing
- Assignee set to Timo Goebel
- Pull request https://github.com/theforeman/foreman/pull/4195 added
- Bugzilla link set to 1421441
- Status changed from Ready For Testing to Closed
- % Done changed from 0 to 100
- Pull request https://github.com/theforeman/foreman/pull/4401 added
- Pull request deleted (
https://github.com/theforeman/foreman/pull/4401)
- Translation missing: en.field_release set to 209
- Related to Bug #19252: Associating VM fails with unknown permission for compute_resources_vms#associate added
- Related to Bug #19414: Discovery host form errors out with Please try to update your request added
- Related to Bug #19419: Invalid syntax in aws fog extension added
- Related to Bug #19436: dropdowns on discovered host do not work added
- Related to Bug #19566: Creating a new host VM on xen fails with: undefined method `new_host?' added
- Is duplicate of Bug #19989: cannot edit hosts with names starting with "new" added
- Related to Bug #20453: When cloning a host, build mode is off added
- Related to Bug #20820: ajax vars not loaded for host import added
- Related to Feature #22387: VMWare: Detect Operatingsystem when importing a VM added
- Related to Bug #23859: Ternary operation with vm_exists? in orchestration compute added
Also available in: Atom
PDF