Bug 1019214 - [RFE] Connect foreman bootiso when creating a new VM and boot from it.
[RFE] Connect foreman bootiso when creating a new VM and boot from it.
Status: ON_QA
Product: Red Hat Satellite 6
Classification: Red Hat
Component: Bootdisk Plugin (Show other bugs)
6.0.2
Unspecified Unspecified
unspecified Severity low (vote)
: GA
: --
Assigned To: Lukas Zapletal
Sachin Ghai
http://projects.theforeman.org/issues...
: FutureFeature, Triaged
: 1286702 (view as bug list)
Depends On:
Blocks: 260381
  Show dependency treegraph
 
Reported: 2013-10-15 06:03 EDT by pgustafs
Modified: 2017-06-14 05:54 EDT (History)
17 users (show)

See Also:
Fixed In Version:
Doc Type: Enhancement
Doc Text:
Story Points: ---
Clone Of:
Environment:
Last Closed:
Type: Bug
Regression: ---
Mount Type: ---
Documentation: ---
CRM:
Verified Versions:
Category: ---
oVirt Team: ---
RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: ---


Attachments (Terms of Use)


External Trackers
Tracker ID Priority Status Summary Last Updated
Foreman Issue Tracker 3287 None None None 2016-04-26 13:06 EDT

  None (edit)
Comment 1 RHEL Product and Program Management 2013-10-15 06:07:53 EDT
Since this issue was entered in Red Hat Bugzilla, the release flag has been
set to ? to ensure that it is properly evaluated for this release.
Comment 2 Dominic Cleal 2013-10-15 06:09:05 EDT
"User wants to be able to connect foreman bootiso when creating a new VM and boot from it as an alternative to PXE boot (they using vmware as virtualization platform.)

There is networks where PXE boot not is possible due to various reasons a good alternative to PXE boot would be to having foreman connect an foreman bootiso to the VM when it's created and boot from it instead."
Comment 4 Dominic Cleal 2013-10-15 07:52:15 EDT
Peter, what configuration method do you think is needed here?  I can think of the following, where a mixture might be best:

1. global setting to always use bootdisk for VMs that would otherwise PXE boot
2. per-compute resource setting
3. per-subnet setting
4. always use it if there's no DHCP and TFTP proxy on the subnet
Comment 5 pgustafs 2013-10-15 08:20:55 EDT
(In reply to Dominic Cleal from comment #4)
> Peter, what configuration method do you think is needed here?  I can think
> of the following, where a mixture might be best:
> 
> 1. global setting to always use bootdisk for VMs that would otherwise PXE
> boot
> 2. per-compute resource setting
> 3. per-subnet setting
> 4. always use it if there's no DHCP and TFTP proxy on the subnet

Dominic, I think a mixture would be good:

1. global setting to always use bootdisk for VMs that would otherwise PXE boot
2. per-subnet setting
3. always use it if there's no DHCP and TFTP proxy on the subnet
4. Per-host setting, e.g. an checkbox when creating the host
Comment 7 Corey Welton 2014-05-07 20:40:09 EDT
Moving to 6.0.4 for QE purposes.
Comment 8 Bryan Kearney 2015-08-25 13:22:43 EDT
Upstream bug component is Bootdisk Plugin
Comment 9 Bryan Kearney 2016-03-23 09:32:37 EDT
Moving to POST since upstream bug http://projects.theforeman.org/issues/3287 has been closed
-------------
Anonymous
Applied in changeset commit:foreman_bootdisk|de59b7bba2ff16953fa6eaffef205000ec60aced.
Comment 15 Ondřej Pražák 2016-11-04 07:48:37 EDT
*** Bug 1286702 has been marked as a duplicate of this bug. ***

Note You need to log in before you can comment on or make changes to this bug.