docs: update documentation
All checks were successful
development / Check commit compliance (push) Successful in 5s
All checks were successful
development / Check commit compliance (push) Successful in 5s
This commit is contained in:
parent
34e30b0a5f
commit
646f81e50b
@ -6,7 +6,7 @@
|
|||||||
|
|
||||||
Hashistack Ansible uses a configuration directory to store all the configuration files and other artifacts.
|
Hashistack Ansible uses a configuration directory to store all the configuration files and other artifacts.
|
||||||
|
|
||||||
This directory is defined with the variable `configuration_directory`. By default, it will look at `{{ lookup('env', 'PWD') }}/etc/hashistack`, which equals `$(pwd)/etc/hashistack`.
|
This directory is defined with the variable `hashistack_configuration_directory`. By default, it will look at `{{ lookup('env', 'PWD') }}/etc/hashistack`, which equals `$(pwd)/etc/hashistack`.
|
||||||
|
|
||||||
Under this directory, you are expected to place the `globals.yml` file, with your configuration.
|
Under this directory, you are expected to place the `globals.yml` file, with your configuration.
|
||||||
|
|
||||||
@ -18,9 +18,9 @@ Additionally, subdirectories can be used to tailor the configuration further.
|
|||||||
|
|
||||||
Each group within the `inventory` will look at a directory named after itself:
|
Each group within the `inventory` will look at a directory named after itself:
|
||||||
|
|
||||||
- nomad_servers group will look for `{{ configuration_directory }}/nomad_servers`
|
- nomad_servers group will look for `{{ hashistack_configuration_directory }}/nomad_servers`
|
||||||
- vault_servers group will look for `{{ configuration_directory }}/vault_servers`
|
- vault_servers group will look for `{{ hashistack_configuration_directory }}/vault_servers`
|
||||||
- consul_servers group will look for `{{ configuration_directory }}/consul_servers`
|
- consul_servers group will look for `{{ hashistack_configuration_directory }}/consul_servers`
|
||||||
|
|
||||||
Within each of these directories, you can place an additional `globals.yml file`, that will superseed the file at the root of the configuration directory.
|
Within each of these directories, you can place an additional `globals.yml file`, that will superseed the file at the root of the configuration directory.
|
||||||
|
|
||||||
|
@ -112,6 +112,16 @@ This will install roles that are not packaged with the collection, but are still
|
|||||||
|
|
||||||
You should now have some roles inside `./roles/`.
|
You should now have some roles inside `./roles/`.
|
||||||
|
|
||||||
|
9. Copy `inventory` file and `globals.yml `file locally
|
||||||
|
|
||||||
|
```bash
|
||||||
|
cp collections/ansible_collections/ednz_cloud/hashistack/playbooks/inventory/multinode.ini inventory/
|
||||||
|
```
|
||||||
|
|
||||||
|
```bash
|
||||||
|
cp collections/ansible_collections/ednz_cloud/hashistack/playbooks/group_vars/all/globals.yml etc/hashistack/globals.yml
|
||||||
|
```
|
||||||
|
|
||||||
## Generate Credentials
|
## Generate Credentials
|
||||||
|
|
||||||
Before deploying your infrastructure with Hashistack-Ansible, you need to generate credentials that will be used to bootstrap the various clusters.
|
Before deploying your infrastructure with Hashistack-Ansible, you need to generate credentials that will be used to bootstrap the various clusters.
|
||||||
|
@ -1 +1,6 @@
|
|||||||
# TLS Guide
|
# TLS Guide
|
||||||
|
|
||||||
|
|
||||||
|
create certificate/ca directory
|
||||||
|
|
||||||
|
`ansible-playbook -i inventory/multinode.ini ednz_cloud.hashistack.generate_certs.yml`
|
||||||
|
Loading…
Reference in New Issue
Block a user