Bug 1399339 - Keystone identity service integration guide should refer to keystone VIP
Summary: Keystone identity service integration guide should refer to keystone VIP
Keywords:
Status: CLOSED CURRENTRELEASE
Alias: None
Product: Red Hat OpenStack
Classification: Red Hat
Component: documentation
Version: 9.0 (Mitaka)
Hardware: Unspecified
OS: Linux
unspecified
medium
Target Milestone: ---
: ---
Assignee: Martin Lopes
QA Contact: RHOS Documentation Team
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2016-11-28 19:21 UTC by nalmond
Modified: 2019-12-16 07:26 UTC (History)
2 users (show)

Fixed In Version:
Doc Type: If docs needed, set a value
Doc Text:
Clone Of:
Environment:
Last Closed: 2017-06-12 05:56:45 UTC
Target Upstream Version:

Attachments (Terms of Use)
Add an attachment (proposed patch, testcase, etc.)

Description nalmond 2016-11-28 19:21:17 UTC 
Description of problem:
The documentation to integrate keystone with AD, IDM, and generic ldap currently has the user configure the auth_uri and url to point to the controller. However, this can be misleading in deployments with more than one controller. This should use the keystone endpoint VIP instead of the controller IP for multi-controller environments.

[keystone_authtoken]
auth_uri = http://controllerIP:5000/v3
auth_version = v3

https://access.redhat.com/documentation/en/red-hat-openstack-platform/9/single/integrate-with-identity-service/#configure_block_storage_to_use_keystone_v3_2

This also applies to the guide for RHOSP 7 and 8.
Comment 2 Martin Lopes 2017-06-12 05:42:10 UTC 
Backporting to earlier guides.
Comment 3 Martin Lopes 2017-06-12 05:53:09 UTC 
Backported to osp10/9/8/7 guides.
Comment 4 Martin Lopes 2017-06-12 05:54:39 UTC 
Thanks for raising this bug. All guides have been republished to include the note.

For example: 
https://access.redhat.com/documentation/en-us/red_hat_openstack_platform/9/html-single/integrate_with_identity_service/#configure_block_storage_to_use_keystone_v3_2
Note You need to log in before you can comment on or make changes to this bug.