Define users, tenants, and roles in OpenStack Installation Guide for Red Hat Enterprise Linux, CentOS, and Fedora  - havana

Bug #1277289 reported by Dan-mossor
6
This bug affects 1 person
Affects Status Importance Assigned to Milestone
openstack-manuals
Fix Released
Undecided
Rhys Oxenham

Bug Description

The first paragraph states to "use the authorization token created in the previous section." The RH derivative documentation creates two authentication tokens in the section previous to this, both the identity service token and the Keystone PKI tokens. This step does not identify which token is to be used.

In comparison with the Ubuntu documentation, it was discovered that the token generated for the identity service is the one to be used for the OS_SERVICE_TOKEN environment variable, since the Ubuntu documentation doesn't include the generation of the PKI tokens.

Suggested edit:
Typically, you would indicate a user and password to authenticate with the Identity Service. At this point, however, we have not created any users, so we have to use the authorization token created in step 4 of the previous section. You can pass this with the --os-token option to the keystone command or set the OS_SERVICE_TOKEN environment variable. We'll set OS_SERVICE_TOKEN, as well as OS_SERVICE_ENDPOINT to specify where the Identity Service is running. Replace FCAF3E... with your authorization token.

Even better edit:
Typically, you would indicate a user and password to authenticate with the Identity Service. At this point, however, we have not created any users, so we have to use the authorization token created in step 4 of the previous section. You can pass this with the --os-token option to the keystone command or set the OS_SERVICE_TOKEN environment variable. We'll set OS_SERVICE_TOKEN, as well as OS_SERVICE_ENDPOINT to specify where the Identity Service is running.

# export OS_SERVICE_TOKEN=$ADMIN_TOKEN
# export OS_SERVICE_ENDPOINT=http://controller:35357/v2.0

-----------------------------------
Built: 2014-02-06T20:04:57 00:00
git SHA: 4ddeb388fbacb250f965e28fc017ba6dd2317bb8
URL: http://docs.openstack.org/trunk/install-guide/install/yum/content/keystone-users.html
source File: file:/home/jenkins/workspace/openstack-install-deploy-guide-fedora/doc/install-guide/section_keystone-users.xml
xml:id: keystone-users

tags: added: install-guide
Revision history for this message
OpenStack Infra (hudson-openstack) wrote : Fix proposed to openstack-manuals (master)

Fix proposed to branch: master
Review: https://review.openstack.org/74388

Changed in openstack-manuals:
assignee: nobody → Rhys Oxenham (rdoxenham)
status: New → In Progress
Revision history for this message
OpenStack Infra (hudson-openstack) wrote : Fix merged to openstack-manuals (master)

Reviewed: https://review.openstack.org/74388
Committed: https://git.openstack.org/cgit/openstack/openstack-manuals/commit/?id=c2e6c077f31d29bd21e743a2ded36916857b14bb
Submitter: Jenkins
Branch: master

commit c2e6c077f31d29bd21e743a2ded36916857b14bb
Author: Rhys Oxenham <email address hidden>
Date: Tue Feb 18 14:22:39 2014 +0100

    Adds clarity to the usage of the authorisation token

    As reported in LP#1277289, the usage of the authorisation
    token is not clear in the instructions. It refers to a token
    previously created but potentially leaves the user
    confused as to which one to use. This patch adds the clarity
    required and posts a link to the documentation section.

    Change-Id: Ib16bd2770d4c4aac5292e9a3d2f25c2417e818f2
    Closes-Bug: #1277289
    backport: havana

Changed in openstack-manuals:
status: In Progress → Fix Released
Revision history for this message
OpenStack Infra (hudson-openstack) wrote : Fix proposed to openstack-manuals (stable/havana)

Fix proposed to branch: stable/havana
Review: https://review.openstack.org/74819

Revision history for this message
OpenStack Infra (hudson-openstack) wrote : Fix merged to openstack-manuals (stable/havana)

Reviewed: https://review.openstack.org/74819
Committed: https://git.openstack.org/cgit/openstack/openstack-manuals/commit/?id=ee63789be033329466aa6543548b3520aba1ab4e
Submitter: Jenkins
Branch: stable/havana

commit ee63789be033329466aa6543548b3520aba1ab4e
Author: Rhys Oxenham <email address hidden>
Date: Tue Feb 18 14:22:39 2014 +0100

    Adds clarity to the usage of the authorisation token

    As reported in LP#1277289, the usage of the authorisation
    token is not clear in the instructions. It refers to a token
    previously created but potentially leaves the user
    confused as to which one to use. This patch adds the clarity
    required and posts a link to the documentation section.

    Change-Id: Ib16bd2770d4c4aac5292e9a3d2f25c2417e818f2
    Closes-Bug: #1277289
    backport: havana
    (cherry picked from commit c2e6c077f31d29bd21e743a2ded36916857b14bb)

tags: added: in-stable-havana
Revision history for this message
OpenStack Infra (hudson-openstack) wrote : Fix included in openstack/openstack-manuals 15.0.0

This issue was fixed in the openstack/openstack-manuals 15.0.0 release.

To post a comment you must log in.
This report contains Public information  
Everyone can see this information.

Other bug subscribers

Remote bug watches

Bug watches keep track of this bug in other bug trackers.