Bug 961583
Summary: | foreman smart proxy not setup/enabled in katello-configure | ||
---|---|---|---|
Product: | Red Hat Satellite | Reporter: | Corey Welton <cwelton> |
Component: | Installation | Assignee: | Katello Bug Bin <katello-bugs> |
Status: | CLOSED WONTFIX | QA Contact: | Katello QA List <katello-qa-list> |
Severity: | unspecified | Docs Contact: | |
Priority: | unspecified | ||
Version: | Nightly | CC: | bkearney, dcleal, jsherril |
Target Milestone: | Unspecified | Keywords: | Triaged |
Target Release: | Unused | ||
Hardware: | Unspecified | ||
OS: | Unspecified | ||
Whiteboard: | |||
Fixed In Version: | Doc Type: | Bug Fix | |
Doc Text: | Story Points: | --- | |
Clone Of: | Environment: | ||
Last Closed: | 2014-01-08 22:17:53 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: |
Description
Corey Welton
2013-05-10 02:37:13 UTC
I'm not sure it makes sense to auto-setup a smart proxy, as there are network infrastructure implications involved. A user (maybe most users?) may not want a smart proxy installed by default on the same machine as foreman. I agree we should install a basic smart proxy and puppetmaster centrally, which also gives us the ability to bootstrap Satellite nodes. I'm going to bump this to MDP3 though, as it'll be much easier once we have a kafo-based katello-configure. For now only the node installer is kafo-based, so integrating the two sets of installer modules before then will be much trickier. I am gonna punt this for now. Lets go with the current two installer now, and we can combine later. |