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

Bug 1074343

Summary:	[Doc] Packstack should be documented as a deployment tool only for PoC and AIO installs
Product:	Red Hat OpenStack	Reporter:	Summer Long <slong>
Component:	doc-Installation_and_Configuration_Guide	Assignee:	Bruce Reeler <breeler>
Status:	CLOSED CURRENTRELEASE	QA Contact:	ecs-bugs
Severity:	high	Docs Contact:
Priority:	high
Version:	4.0	CC:	breeler, rlandman, yeylon
Target Milestone:	z3	Keywords:	Documentation, Triaged
Target Release:	4.0
Hardware:	Unspecified
OS:	Unspecified
Whiteboard:
Fixed In Version:		Doc Type:	Bug Fix
Doc Text:		Story Points:	---
Clone Of:	1074308	Environment:
Last Closed:	2014-03-26 06:20:12 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:	1074308, 1074408, 1074409
Bug Blocks:

Description Summer Long 2014-03-09 22:48:56 UTC

+++ This bug was initially created as a clone of Bug #1074308 +++

Description of problem:
Today Packstack is described in the release notes as:

https://access.redhat.com/site/documentation/en-US/Red_Hat_Enterprise_Linux_OpenStack_Platform/4/html-single/Release_Notes/index.html#idm59109272

> PackStack is a command line utility that enables rapid deployment of
> OpenStack on existing servers over an SSH connection. PackStack is
> suitable for deploying both single-node proof-of-concept
> installations and more complex multi-node installations. Deployment
> options are provided either interactively, via the command line, or
> non-interactively by means of a text file containing a set of
> preconfigured values for OpenStack parameters.

This should be changed to make it clearer that Packstack is suitable only for PoC, Demo and All In One (AIO) installs.

Changing the above to be:
**************
PackStack is a command line utility that enables rapid deployment of OpenStack on existing servers over an SSH connection.  Deployment options are provided either interactively, via the command line, or non-interactively by means of a text file containing a set of preconfigured values for OpenStack parameters.

PackStack is suitable for deploying the following types of configurations:

* Single-node proof-of-concept installations (where all controller services and your virtual machines run on a single physical host).  This is referred to All-in-One (AIO) install.

* Proof-of-Concept installations where there is a single controller node and multiple Compute Nodes.  This is similar to the AIO install above, except you may use one or more additional hardware nodes for running virtual machines.

PackStack is not suitable as a production deployment tool, as it uses many assumptions in its configuration to make demos and proof-of-concept installs easier.  For production deployments it is recommended that you use Foreman or configured individual services manually.

PackStack will not be able to deploy services in a highly available or load balanced configuration, nor will it provide the flexibility needed to configure arbitrary networking.  These are features that will be reserved for the production deployment tools (Foreman, and in the future, TripleO).
**************

Comment 2 Summer Long 2014-03-09 22:55:46 UTC

Assigning to Bruce Reeler, as the assigned author for PackStack.

This update should just copy the text updated in the RelNotes for:
https://bugzilla.redhat.com/show_bug.cgi?id=1074308

Now that the GSG and the ICG are both in pressgang, the common topic for "The PackStack Deployment Utility" can be updated to take care of both.

Comment 4 Bruce Reeler 2014-03-14 06:27:19 UTC

Comments after review by mlopes:
* I'd rather say "PackStack makes assumptions, rather than "uses"
"PackStack is not suitable as a production deployment tool, as it uses
many assumptions in its configuration to make demos and proof-of-concept
installations easier."

* I suppose the usage of arbitrary here seems a bit arbitrary:
"nor can it provide the flexibility needed to configure arbitrary
networking."

* I think it's worth a mention there that PackStack uses puppet modules

Comment 5 Bruce Reeler 2014-03-14 06:35:03 UTC

(In reply to Bruce Reeler from comment #4)
> Comments after review by mlopes:
> * I'd rather say "PackStack makes assumptions, rather than "uses"
> "PackStack is not suitable as a production deployment tool, as it uses
> many assumptions in its configuration to make demos and proof-of-concept
> installations easier."

I think I'll leave this as is, because I assume PackStack has a config file(s),
and it uses the config file, so "uses assumptions" is more reflective of what it
does. Also, "uses" is a bit less anthropomorphic than "makes assumptions". "Makes assumptions" is too close to "thinks" for my liking!

> 
> * I suppose the usage of arbitrary here seems a bit arbitrary:
> "nor can it provide the flexibility needed to configure arbitrary
> networking."

used 'complex' instead.

> 
> * I think it's worth a mention there that PackStack uses puppet modules

added.

Comment 6 Bruce Reeler 2014-03-25 00:13:08 UTC

Reviewed by Mlopes. Setting to on QA.