Add note to keystone-manage bootstrap doc
A lot of people are very surprised that we no longer reference port 35357 in our Ubuntu (and SUSE) install guides. Add a note to clarify that this is not a bug and we do really mean it. This does not change the RDO install guide because our guide still instructs users to use port 35357 because the RDO package still includes an Apache vhost file that uses 35357. Change-Id: I334ba888190705a345d50cebe577b832753f202c Related-bug: #1755026 Related-bug: #1755511 Related-bug: #1756178
This commit is contained in:
parent
b3f8f1e82a
commit
1b01ebce56
doc/source/install
@ -125,6 +125,13 @@ Install and configure components
|
||||
|
||||
5. Bootstrap the Identity service:
|
||||
|
||||
.. note::
|
||||
|
||||
Before the Queens release, keystone needed to be run on two separate ports to
|
||||
accomodate the Identity v2 API which ran a separate admin-only service
|
||||
commonly on port 35357. With the removal of the v2 API, keystone can be run
|
||||
on the same port for all interfaces.
|
||||
|
||||
.. code-block:: console
|
||||
|
||||
# keystone-manage bootstrap --bootstrap-password ADMIN_PASS \
|
||||
|
@ -118,6 +118,13 @@ Install and configure components
|
||||
|
||||
5. Bootstrap the Identity service:
|
||||
|
||||
.. note::
|
||||
|
||||
Before the Queens release, keystone needed to be run on two separate ports to
|
||||
accomodate the Identity v2 API which ran a separate admin-only service
|
||||
commonly on port 35357. With the removal of the v2 API, keystone can be run
|
||||
on the same port for all interfaces.
|
||||
|
||||
.. code-block:: console
|
||||
|
||||
# keystone-manage bootstrap --bootstrap-password ADMIN_PASS \
|
||||
|
Loading…
x
Reference in New Issue
Block a user