d78a90b3ae
The documentation for vault suggests creating a token from the root token specifically for the vault authorisation action. To lock the token down the number of times the token can be used is set. The charm action uses the token multiple times so the action fails. Since the token is created with a relatively short ttl it seems reasonable to remove the usage limit entirely. Feedback from users has shown that when following the documentation the need to unseal each vault unit individually was missed so this instruction is now next to the unseal explanation as well as being reiterated in the HA section. When deploying an HA configuration etcd must support etcd3, this requirement was lacking in the instructions so it has been added. Change-Id: I07c233ccadd52ec7fe2fff6276e56cd88c48acf1 Closes-Bug: #1779875 |
||
---|---|---|
deploy-guide/source | ||
.gitignore | ||
.gitreview | ||
LICENSE | ||
README.rst | ||
requirements.txt | ||
setup.cfg | ||
setup.py | ||
tox.ini |
README.rst
Team and repository tags
OpenStack Charm Deployment Guide
To build the guide, execute the following command:
$ tox
After running tox
, the documentation will be available
for viewing in HTML format in the deploy-guide/build/html
directory. View these new documents in your favorite web browser.
Submitting changes to this documentation
If you wish to raise an issue against the documentation, please do so at https://bugs.launchpad.net/charm-deployment-guide.
Submissions to this source are controlled via the OpenStack gerrit system at https://review.openstack.org. If you wish to submit content then please see https://docs.openstack.org/infra/manual/developers.html for details on how to submit changes.