Bug 1033225 - [RFE] Provide documentation on variables in host groups
Summary: [RFE] Provide documentation on variables in host groups
Keywords:
Status: CLOSED CANTFIX
Alias: None
Product: Red Hat OpenStack
Classification: Red Hat
Component: doc-Deploying_OpenStack_Enterprise_Environments
Version: 5.0 (RHEL 6)
Hardware: Unspecified
OS: Unspecified
medium
medium
Target Milestone: ---
: 5.0 (RHEL 7)
Assignee: Andrew Dahms
QA Contact: ecs-bugs
URL:
Whiteboard:
Depends On:
Blocks: RHOS-Foreman-Deployability
TreeView+ depends on / blocked
 
Reported: 2013-11-21 18:08 UTC by james labocki
Modified: 2014-10-14 12:13 UTC (History)
4 users (show)

Fixed In Version:
Doc Type: Enhancement
Doc Text:
Clone Of:
Environment:
Last Closed: 2014-10-14 12:13:23 UTC
Target Upstream Version:

Attachments (Terms of Use)
Add an attachment (proposed patch, testcase, etc.)

Description james labocki 2013-11-21 18:08:40 UTC 
This is a request to explain the variables in the hostgroups and what they map to in configuration files on the host. For example, if private_controller_ip is changed in a host group what files on the host will be modified with this address? This will help users understand the implications of the variables in their deployment.

Also, it would be useful to explain what quickstack is as it shows up in the user interface.
Comment 2 Summer Long 2013-11-26 01:46:31 UTC 
Updating priority to match severity.
Comment 3 Martin Lopes 2014-01-14 06:24:54 UTC 
This bug is being assigned to Scott Radvan, who is now the designated docs specialist for Foreman.
Comment 5 Andrew Dahms 2014-10-14 12:13:23 UTC 
At current, a list of core host group parameters is provided in the documentation. However, we do not have the information to document all host group parameters, and given the dynamic nature of host group parameters, I am closing this bug.

I shall continue to track changes to host group parameters and their listing in Foreman and the RHEL-OSP installer, and will raise a new bug to document those parameters if required.
Note You need to log in before you can comment on or make changes to this bug.