Note: This bug is displayed in read-only format because
the product is no longer active in Red Hat Bugzilla.
Red Hat Satellite engineering is moving the tracking of its product development work on Satellite to Red Hat Jira (issues.redhat.com). If you're a Red Hat customer, please continue to file support cases via the Red Hat customer portal. If you're not, please head to the "Satellite project" in Red Hat Jira and file new tickets here. Individual Bugzilla bugs will be migrated starting at the end of May. If you cannot log in to RH Jira, please consult article #7032570. That failing, please send an e-mail to the RH Jira admins at rh-issues@redhat.com to troubleshoot your issue as a user management inquiry. The email creates a ServiceNow ticket with Red Hat. Individual Bugzilla bugs that are migrated will be moved to status "CLOSED", resolution "MIGRATED", and set with "MigratedToJIRA" in "Keywords". The link to the successor Jira issue will be found under "Links", have a little "two-footprint" icon next to it, and direct you to the "Satellite project" in Red Hat Jira (issue links are of type "https://issues.redhat.com/browse/SAT-XXXX", where "X" is a digit). This same link will be available in a blue banner at the top of the page informing you that that bug has been migrated.
Description of problem:
[RFE]
In environments without a DHCP server it is possible to provision systems using the iPXE bootdisk or the 'full' bootdisk image. It would be great if Satellite 6 could to this automatically in environments without DHCP/TFTP capabilities.
The existing foreman bootdisk functionality, with or without the PXELess discovery already covers the requirements to be able to bootstrap and provision a host in an environment without DHCP/TFTP available.
Currently Satellite can create virtual machines, it will configure the vm to boot via the network card. In an environment with DHCP/TFTP available, this fully automates the create+provision vm process.
What we are asking, is that Satellite could:
1. Create the VM.
2. Make the foreman bootdisk ISO image availabe to the VM
e.g Upload iso image to: RHEV ISO_Domain/VMWare Datastore etc.
3. Connect the ISO to the VM.
4. Configure the VM to boot from cdrom.
5. Start the VM, and it will provision using the foreman bootdisk.
This would enable fully automated provisioning of the vm, in an environments without DHCP/TFTP available.
** It is the manual steps to connect the foreman bootdisk ISO to the guest we want to eliminate.
*** Ideally this would be implemented with the ability to add custom plug-ins. To enable customers the ability to add support to do the same functionality for baremetal servers using BMC virtual-media functionality on out-of-band management solutions like Dell's iDRAC, HP's iLO etc.