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.
Bug 970703 - [RFE] some sort of katello-foreman-libvirt optional packaging for configuring libvirt-based provisioning
Summary: [RFE] some sort of katello-foreman-libvirt optional packaging for configuring...
Keywords:
Status: CLOSED WONTFIX
Alias: None
Product: Red Hat Satellite
Classification: Red Hat
Component: Uncategorized
Version: Nightly
Hardware: Unspecified
OS: Unspecified
unspecified
high
Target Milestone: Unspecified
Assignee: satellite6-bugs
QA Contact: Katello QA List
URL:
Whiteboard: RFE
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2013-06-04 16:06 UTC by Corey Welton
Modified: 2017-02-09 20:52 UTC (History)
7 users (show)

Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Clone Of:
Environment:
Last Closed: 2017-02-09 20:52:00 UTC
Target Upstream Version:
Embargoed:

Attachments (Terms of Use)

Description Corey Welton 2013-06-04 16:06:51 UTC 
Description of problem:
Simply put, the current process to setup libvirt so that a user can use it in conjunction with foreman is completely arduous.  Installing a bunch of virtualization, DHCP, TFTP packages and manually creating the files for foreman's consumption -- it's very, very error-prone.  

At the same time, I can see where users may not want to use the libvirt option, opting for baremetal, and doesn't want all the dependencies or cruft that might come with stuff they'd never use.

Thus, I think we should have a package set -- "katello-foreman-libvirt" or something that has dependencies on all those aforementioned, required packages and installs at least usable, skeleton versions of the required config files that would give users a "quickstart" to get them up and running, which they could tweak later (i.e., change subnets, etc.) if they so desired.


Requires:
@virtualization
libvirt
tftp
[...]

Creates and/or correctly populates:
/etc/libvirt/qemu/networks/foreman.xml
/etc/libvirt/storage/default-pool.xml
/etc/dhcp/dhcpd.conf
[...]


...and so on.
Comment 1 Mike McCune 2013-06-06 17:02:38 UTC 
amen :)
Comment 2 Mike McCune 2013-06-06 17:05:12 UTC 
Added:

https://trello.com/card/add-meta-package-and-katello-configure-options-to-easily-setup-libvirt-provisioning-on-a-katello-and-foreman-box/511bd7357c52d1c61c00510e/121
Comment 4 Corey Welton 2013-06-24 14:40:47 UTC 
One more consideration for this bug - the ISO installer currently only installs katello-foreman-all, which does not pull in foreman-libvirt. If this stuff is abstracted out, the installer will need to provide option to install product with or without libvirt support, and as such, install the package (or not).
Comment 9 Mike McCune 2013-11-01 20:34:38 UTC 
this is really solved  by:

https://github.com/domcleal/katellovirt

can be used by:

# puppet module install domcleal/katellovirt
# puppet apply -v -e 'include katellovirt'

the question is: "How do we support this?"

For MDP we can point users at this method but we will need a way to install and ship that puppet module and perhaps have an option on kafo to set this up.

I'm going to move this to MDP3 so we can figure out a *right* way to do this and for MDP2 we can use the above 2 liner to get things setup.
Comment 10 Todd Warner 2017-02-09 20:52:00 UTC 
Due to the age of this request, and our prioritization, I am closing this bugzilla. The prioritization ensured that it was not something we could ever address in a meaningful timeframe.

-todd warner, PM, Satellite
Note You need to log in before you can comment on or make changes to this bug.