Update layout docs for running console proxies
As of Rocky, the cell databases are being used for storing console authorizations, so the layout for running console proxies has changed from global to a deployment to per cell. Part of blueprint convert-consoles-to-objects Change-Id: If5c7b081682f0cb36a678d0e21e26b7985cd8527
This commit is contained in:
parent
969239029d
commit
c53c9ea759
@ -300,15 +300,13 @@ thus be configured as an API-level service with access to the
|
||||
Consoleauth service and console proxies
|
||||
~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
|
||||
|
||||
The consoleauth service should be global across all cells and thus be
|
||||
configured as an API-level service with access to the
|
||||
``[api_database]/connection`` information. The various console proxies
|
||||
should also be global across all cells but they don't need access to the
|
||||
API database.
|
||||
`As of Rocky`__, the ``nova-consoleauth`` service has been deprecated and cell
|
||||
databases are used for storing token authorizations. All new consoles will be
|
||||
supported by the database backend and existing consoles will be reset. Console
|
||||
proxies must be run per cell because the new console token authorizations are
|
||||
stored in cell databases.
|
||||
|
||||
Future work will deprecate the consoleauth service, store token
|
||||
authorizations in the cell databases, and require console proxies running
|
||||
per cell instead of globally.
|
||||
.. __: https://specs.openstack.org/openstack/nova-specs/specs/rocky/approved/convert-consoles-to-objects.html
|
||||
|
||||
Operations Requiring upcalls
|
||||
~~~~~~~~~~~~~~~~~~~~~~~~~~~~
|
||||
|
Loading…
Reference in New Issue
Block a user