Keystone Verify - Further clarity on the use of ADMIN_PASS

A user reported an issue that the documentation was not clear as to where
the "ADMIN_PASS" paramater came from. I've clarified this further and
added a link to the relevant step to enforce it's origin. Also corrected
a very minor typo.

Note that this is now aware of the way that Debian-based platforms configure
the users in Keystone and links to the relevant page for further assistance.

Change-Id: Ie1722812386591fa0563b57a4127b0042da1ee40
backport: havana
Closes-Bug: #1252281
(cherry picked from commit 6dc666cef7)
This commit is contained in:
Rhys Oxenham
2013-12-10 23:27:41 +00:00
committed by Andreas Jaeger
parent d614b7226a
commit b2096448cd

View File

@@ -15,8 +15,16 @@
<screen><prompt>#</prompt> <userinput>unset OS_SERVICE_TOKEN OS_SERVICE_ENDPOINT</userinput></screen>
<para>You can now use regular username-based authentication.
Request a authentication token using the <literal>admin</literal>
user and the password you chose for that user.</para>
Request an authentication token using the <literal>admin</literal>
user and the password you chose during the earlier administrative
user-creation step.</para>
<para os="rhel;centos;fedora;opensuse;sles;ubuntu">
See <xref linkend="keystone-users"/> for further details.
</para>
<para os="debian">
See <xref linkend="keystone-install"/> for further details.
</para>
<screen><prompt>#</prompt> <userinput>keystone --os-username=admin --os-password=<replaceable>ADMIN_PASS</replaceable> \
--os-auth-url=http://controller:35357/v2.0 token-get</userinput></screen>