Note: This bug is displayed in read-only format because the product is no longer active in Red Hat Bugzilla.

Bug 1091346

Summary: [Doc] Please, specify that creating an environment file for the foreman installer is suggested
Product: Red Hat OpenStack Reporter: Ramon Acedo <ramon>
Component: doc-Deploying_OpenStack_Enterprise_EnvironmentsAssignee: Andrew Dahms <adahms>
Status: CLOSED DUPLICATE QA Contact: ecs-bugs
Severity: medium Docs Contact:
Priority: medium    
Version: 5.0 (RHEL 6)CC: adahms, mlopes, yeylon
Target Milestone: ---Keywords: Documentation, Triaged
Target Release: 5.0 (RHEL 7)   
Hardware: Unspecified   
OS: Unspecified   
Whiteboard:
Fixed In Version: Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of: Environment:
Build Name: 15807, Installation and Configuration Guide-4 Build Date: 26-03-2014 09:37:23 Topic ID: 19224-620205 [Latest]
Last Closed: 2014-10-30 10:48:47 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 Ramon Acedo 2014-04-25 11:48:45 UTC
Title: Configure the Foreman Installer

In the section "Procedure 3.2. Configuring the Foreman installer" it is suggested to modify the file foreman_server.sh and set the values of the environment variables in it.


Suggestions for improvement:

A better practice which seems to be the original idea of the foreman_server.sh script is to create a rc file with the desired values, as an example:

# cat << EOF > foreman-server.rc
> export PROVISIONING_INTERFACE=eth0
> export FOREMAN_GATEWAY=192.168.5.100
> export FOREMAN_PROVISIONING=true
> EOF

And then source the file before running the foreman_server.sh script as explained in the next section.

Comment 2 Martin Lopes 2014-04-28 00:17:48 UTC
This bug is being assigned to Scott Radvan, who is now the designated docs specialist for Foreman.

Comment 3 Andrew Dahms 2014-10-30 10:48:47 UTC
Thank you for raising this bug.

The issue raised in this bug has also been raised in BZ#1107833, where it has been addressed by exporting the variables required to configure the installation script.

Given the revisions made, I am closing this bug, but please let us know if you have any further concerns.

Kind regards,

Andrew

*** This bug has been marked as a duplicate of bug 1107833 ***