Bug 1186534
Summary: | it should be easier (less manual steps) to prepare KVM virtualization host | ||
---|---|---|---|
Product: | Red Hat Satellite 5 | Reporter: | Jan Hutař <jhutar> |
Component: | Client | Assignee: | Tomáš Kašpárek <tkasparek> |
Status: | CLOSED DEFERRED | QA Contact: | Red Hat Satellite QA List <satqe-list> |
Severity: | low | Docs Contact: | |
Priority: | unspecified | ||
Version: | 570 | CC: | tlestach |
Target Milestone: | --- | Keywords: | Reopened |
Target Release: | --- | ||
Hardware: | Unspecified | ||
OS: | Unspecified | ||
Whiteboard: | |||
Fixed In Version: | Doc Type: | Bug Fix | |
Doc Text: | Story Points: | --- | |
Clone Of: | Environment: | ||
Last Closed: | 2018-04-09 12:24:58 UTC | Type: | Bug |
Regression: | --- | Mount Type: | --- |
Documentation: | --- | CRM: | |
Verified Versions: | Category: | --- | |
oVirt Team: | --- | RHEL 7.3 requirements from Atomic Host: | |
Cloudforms Team: | --- | Target Upstream Version: | |
Embargoed: | |||
Bug Depends On: | |||
Bug Blocks: | 1127217 |
Description
Jan Hutař
2015-01-27 22:10:54 UTC
I disagree. 1) First of all I will point out (not to be difficult, but because of point 2 to follow) that our documentation already says (and has said for a long time) that you must install virt-install (or python-virtinst on RHEL 6 or previous) as a manual step when setting up virtual host: https://access.redhat.com/documentation/en-US/Red_Hat_Satellite/5.7/html/Getting_Started_Guide/sect-Managing_Virtualized_Client_Systems.html#sect-Setting_Up_the_Host_System_for_Your_Virtual_Systems 2) koan is installed any time we are provisioning anything, including a re-provision of a physical or virtual system. Koan does not in fact require virt-install or rhn-virtualization-host in that instance. 3) The argument could be made the we should make virt-install a dependency of rhn-virtualization-host, but then the question becomes "how do we ensure that rhn-virtualization-host is installed?" What if qemu-kvm is not installed, should we require it as well? What if someone wanted to use Satellite to manage a non-KVM host? We would be moving from "KVM is the only supported (documented) solution but others will work" to "KVM is required by the tooling and all other virtualization platforms are disallowed". I would love to see this process work better, but it's not as simple as adding a dependency to koan. OK then. One solution on how to achieve improvement in root of this request would be to add "KVM virtualization host" virtualization type into kickstart profile creation wizard. We have re-reviewed this bug, as part of an ongoing effort to improve Satellite/Proxy feature and bug updates, review and backlog. This is a low priority bug and has no currently open customer cases. While this bug may still valid, we do not see it being implemented prior to the EOL of the Satellite 5.x product. As such, this is being CLOSED DEFERRED. Closing now to help set customer expectations as early as possible. You are welcome to re-open this bug if needed. |