Point from Vault page to Cert page
Change-Id: Icb335809742e2575328f0b3507571f18c7a63505
This commit is contained in:
parent
1d1c587da0
commit
cf1028e904
@ -1,5 +1,6 @@
|
|||||||
|
=================
|
||||||
Appendix C: Vault
|
Appendix C: Vault
|
||||||
==============================
|
=================
|
||||||
|
|
||||||
Overview
|
Overview
|
||||||
++++++++
|
++++++++
|
||||||
@ -109,11 +110,10 @@ environment variable each time to point at the individual units.
|
|||||||
vault operator unseal djvVAAste0F5iSe43nmBs2ZX5r+wUqHe4UfUrcprWkyM
|
vault operator unseal djvVAAste0F5iSe43nmBs2ZX5r+wUqHe4UfUrcprWkyM
|
||||||
vault operator unseal iSXHBdTNIKrbd3JIEI+n+q7j04Q4HPsQOHgk7apupttT
|
vault operator unseal iSXHBdTNIKrbd3JIEI+n+q7j04Q4HPsQOHgk7apupttT
|
||||||
|
|
||||||
|
|
||||||
Authorize vault charm
|
Authorize vault charm
|
||||||
~~~~~~~~~~~~~~~~~~~~~
|
~~~~~~~~~~~~~~~~~~~~~
|
||||||
|
|
||||||
vault is now ready for use - however the charm needs to be authorized
|
Vault is now ready for use - however the charm needs to be authorized
|
||||||
using a root token to be able to create secrets storage back-ends and
|
using a root token to be able to create secrets storage back-ends and
|
||||||
roles to allow other applications to access vault for encryption key
|
roles to allow other applications to access vault for encryption key
|
||||||
storage.
|
storage.
|
||||||
@ -149,6 +149,19 @@ After the action completes execution, the vault unit will go active
|
|||||||
and any pending requests for secrets storage will be processed for
|
and any pending requests for secrets storage will be processed for
|
||||||
consuming applications.
|
consuming applications.
|
||||||
|
|
||||||
|
Managing TLS certificates
|
||||||
|
~~~~~~~~~~~~~~~~~~~~~~~~~
|
||||||
|
|
||||||
|
Vault can be used to manage a deployment's TLS certificates, either by basing
|
||||||
|
them on a self-signed CA certificate (that Vault can generate by itself) or on
|
||||||
|
a third-party CA certificate that you can upload to Vault. It is the
|
||||||
|
recommended way to use TLS in Charmed OpenStack. This topic is covered on the
|
||||||
|
`Certificate lifecycle management`_ page.
|
||||||
|
|
||||||
|
.. note::
|
||||||
|
|
||||||
|
The OVN charms require TLS certificates to be managed by Vault.
|
||||||
|
|
||||||
Enabling HA
|
Enabling HA
|
||||||
~~~~~~~~~~~
|
~~~~~~~~~~~
|
||||||
|
|
||||||
@ -239,3 +252,6 @@ and the appropriate unseal keys):
|
|||||||
vault operator unseal iSXHBdTNIKrbd3JIEI+n+q7j04Q4HPsQOHgk7apupttT
|
vault operator unseal iSXHBdTNIKrbd3JIEI+n+q7j04Q4HPsQOHgk7apupttT
|
||||||
|
|
||||||
The ``juju status`` command will return: ``active, Unit is ready...``
|
The ``juju status`` command will return: ``active, Unit is ready...``
|
||||||
|
|
||||||
|
.. LINKS
|
||||||
|
.. _Certificate lifecycle management: app-certificate-management.html
|
||||||
|
Loading…
x
Reference in New Issue
Block a user