Bug 1131798 - [Doc] [GSG] Update section PackStack and Passwords, ref to table 6.1, & comment after 'keystone user-password-update'
Summary: [Doc] [GSG] Update section PackStack and Passwords, ref to table 6.1, & comme...
Keywords:
Status: CLOSED CURRENTRELEASE
Alias: None
Product: Red Hat OpenStack
Classification: Red Hat
Component: doc-Getting_Started_Guide
Version: 5.0 (RHEL 7)
Hardware: Unspecified
OS: Unspecified
high
high
Target Milestone: ---
: 5.0 (RHEL 7)
Assignee: Bruce Reeler
QA Contact: RHOS Documentation Team
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2014-08-20 05:35 UTC by Bruce Reeler
Modified: 2014-10-30 22:30 UTC (History)
4 users (show)

Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Clone Of:
Environment:
Last Closed: 2014-09-04 13:07:41 UTC
Target Upstream Version:
Embargoed:


Attachments (Terms of Use)

Description Bruce Reeler 2014-08-20 05:35:18 UTC
Description of problem:
In Chapter 6 PACKSTACK AND PASSWORDS there is ref to passwords in table 6.1 when in fact now table refers to pwd locations. Also old list of services is referred to and phrasing is incorrect.


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


How reproducible:
See https://access.redhat.com/documentation/en-US/Red_Hat_Enterprise_Linux_OpenStack_Platform/5/html/Getting_Started_Guide/chap-PackStack_and_Passwords.html


Actual wording:
1) "The passwords in the Table 6.1, “PackStack and Passwords” table for Compute, OpenStack Networking, Image, Block Storage and Object Storage are the keystone authentication passwords."

2) # keystone user-password-update USERNAME 

3) Replace USERNAME with the name of the service you want to change the password to. You will have to enter the new password when the machine prompts you to do so.

4) Make sure to update the config files for the services after changing the passwords.


Suggested wording:
1)  The locations of Identity's authentication passwords for OpenStack services are shown in Table 6.1, “PackStack and Passwords”

2) # keystone user-password-update SERVICENAME (?) (These are not user names?)

3) Replace SERVICENAME with the name of the service you want to change the password FOR. You will have to enter the new password WHEN PROMPTED.

4) Confirm with Jamie L that this is still required: "Make sure to update the config files for the services after changing the passwords."

Comment 2 Bruce Reeler 2014-08-21 05:06:17 UTC
(In reply to Bruce Reeler from comment #0)
<snip>
> 
> Actual wording:
> 1) "The passwords in the Table 6.1, “PackStack and Passwords” table for
> Compute, OpenStack Networking, Image, Block Storage and Object Storage are
> the keystone authentication passwords."
> 
> 2) # keystone user-password-update USERNAME 
> 
> 3) Replace USERNAME with the name of the service you want to change the
> password to. You will have to enter the new password when the machine
> prompts you to do so.
> 
> 4) Make sure to update the config files for the services after changing the
> passwords.
> 
> 
> Suggested wording:
> 1)  The locations of Identity's authentication passwords for OpenStack
> services are shown in Table 6.1, “PackStack and Passwords”
> 
> 2) # keystone user-password-update SERVICENAME (?) (These are not user
> names?)
No, this should stay as-is, namely # keystone user-password-update USERNAME 

(the service gets given a username automatically by PackStack, e.g. nova gets given the username "nova")

> 3) Replace SERVICENAME with the name of the service you want to change the
> password FOR. You will have to enter the new password WHEN PROMPTED.
No, rather"Replace USERNAME with the name of the service user you want to change the password for. You will have to enter the new password when prompted."

> 
> 4) Confirm with Jamie L that this is still required: "Make sure to update
> the config files for the services after changing the passwords."

The "Important" admonition should change to: "Using the user-password-update command changes the passwords only on the keystone server. Ensure that you manually update the config files for the services after changing the passwords."

Comment 4 Jamie Lennox 2014-08-26 03:58:27 UTC
Looks good to me.


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