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

Bug 1081074

Summary:	Abstract could benefit from a bit more information
Product:	Red Hat OpenStack	Reporter:	Matt Reid <mreid>
Component:	doc-Installation_and_Configuration_Guide	Assignee:	Don Domingo <ddomingo>
Status:	CLOSED DUPLICATE	QA Contact:	ecs-bugs
Severity:	medium	Docs Contact:
Priority:	unspecified
Version:	4.0	CC:	ddomingo, sclark, slong
Target Milestone:	---	Keywords:	Documentation
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:
Last Closed:	2014-03-27 03:13: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:
Bug Depends On:
Bug Blocks:	1099570

Description Matt Reid 2014-03-26 15:22:04 UTC

Description of problem: The current abstract for the Install & Config guide says
"Installing and Configuring OpenStack environments with Red Hat Enterprise Linux OpenStack Platform 4 (Havana)."

One of the key differences between this doc and the Getting Started Guide is that the Install guide covers the process of installation using The Foreman, and is more suited for production than using packstack in the Getting Started Guide.

The abstract in the GSG says:
"This guide covers the basic getting started tasks for OpenStack Havana. The deployment method described here uses PackStack for proof of concept deployments, and is not meant for production environments."

It seems like the Install Abstract should be more like the GSG Abstract and at least specifically call out that it covers using The Foreman, if not mention that it is the preferred way to set up a production ready OpenStack environment.

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

Additional info:

Comment 2 Don Domingo 2014-03-27 03:13:47 UTC


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