Bug 1235081 - [Docs] [Director] "openstack overcloud deploy" parameters not documented
Summary: [Docs] [Director] "openstack overcloud deploy" parameters not documented
Keywords:
Status: CLOSED CURRENTRELEASE
Alias: None
Product: Red Hat OpenStack
Classification: Red Hat
Component: documentation
Version: Director
Hardware: Unspecified
OS: Unspecified
medium
medium
Target Milestone: ga
: Director
Assignee: Dan Macpherson
QA Contact:
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2015-06-23 23:35 UTC by Dan Sneddon
Modified: 2016-01-04 01:39 UTC (History)
4 users (show)

Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Clone Of:
Environment:
Last Closed: 2016-01-04 01:39:25 UTC
Target Upstream Version:
Embargoed:


Attachments (Terms of Use)

Description Dan Sneddon 2015-06-23 23:35:23 UTC
Description of problem:
The installation documentation for OSP 7 doesn't show how to send parameters to "openstack overcloud deploy"

Version-Release number of selected component (if applicable):
poodle-2015-06-23.14

How reproducible:
100%

Steps to Reproduce:
1. Attempt to deploy overcloud using docs at http://rhos-release.virt.bos.redhat.com/mburns/2015-06-23.1/html/basic_deployment/basic_deployment.html
2.
3.

Actual results:
The instructions say to source deploy-overcloudrc, which is no longer valid. Then the instructions say to use "openstack overcloud deploy", but there are no instructions for deploying with the parameters on the command-line.

Expected results:
The process should be documented properly (according to new builds).

Additional info:
The behavior is documented in "openstack help overcloud deploy", but the behavior of the -e parameter is going to change in a near-future release.

Comment 3 Andrew Dahms 2015-06-24 10:31:28 UTC
Assigning to Dan for review.

Comment 5 Dan Macpherson 2015-06-30 04:28:46 UTC
Targeting this for GA release.

Comment 7 Andrew Dahms 2015-08-16 02:49:21 UTC
Looks good to me; moving to VERIFIED.

Comment 8 Andrew Dahms 2016-01-04 01:39:25 UTC
This content is now live on the Customer Portal; closing.


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