Bug 869321 - Configuring CloudForms System Engine
Configuring CloudForms System Engine
Product: CloudForms Common
Classification: Red Hat
Component: Docs Installation Guide (Show other bugs)
Unspecified Unspecified
unspecified Severity unspecified
: rc
: ---
Assigned To: Lana Brindley
Depends On:
  Show dependency treegraph
Reported: 2012-10-23 11:16 EDT by Garik Khachikyan
Modified: 2015-01-04 16:59 EST (History)
4 users (show)

See Also:
Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of:
Instance Name: Not Defined Build: CSProcessor Builder Version 1.7 Build Filter: null Build Name: 11159, Installation Guide-1.1-1 Build Date: 19-10-2012 13:56:09
Last Closed: 2012-10-23 12:32:42 EDT
Type: Bug
Regression: ---
Mount Type: ---
Documentation: ---
Verified Versions:
Category: ---
oVirt Team: ---
RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: ---

Attachments (Terms of Use)

  None (edit)
Description Garik Khachikyan 2012-10-23 11:16:14 EDT
Description of problem:
`katello-configure` needs to be specified with configuration property --deployment=cfse (as the absence right now points to Katello)
So doing the installation makes the stuff ok, but just refers all the UI links via "/katello/<pages>" which is not correct ("/cfse/<pages>) is the right one IMO.

Version-Release number of selected component (if applicable):

How reproducible:

Steps to Reproduce:
1.doing `katello-configure` without --deployment=cfse
Actual results:
doc does not contain a note having --deployment=cfse option to be specified.

Expected results:
point users to have --deployment=cfse (other options: headpin, katello, sam)

Additional info:
Comment 1 James Laska 2012-10-23 11:28:13 EDT
Thanks for raising this issue Garik.

I'm not in favor of changing the default configuration documentation for the 1.1 release at this time.  I'm not opposed to the change for a future release, but in my view, it's too late to make this change for 1.1.

We've never documented using --deployment=cfse in previous releases, and I'm concerned that if we start to document it now, we may expose unexplored/untested areas of katello.  

Additionally, recommending use of an optional non-required parameter for katello-configure seems incomplete.  If --deployment=cfse is truly important, perhaps it should be a required parameter ... otherwise we'll have confused customers with different baseurls.

Lastly, changing to recommending using --deployment will differ from testing performed throughout the beta.

My recommendation would be to leave the documentation and code as is for 1.1 and explore a more cohesive approach for a future release.
Comment 6 RHEL Product and Program Management 2012-10-23 12:32:42 EDT
Quality Engineering Management has reviewed and declined this request.
You may appeal this decision by reopening this request.

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