infrastructure/ansible
1
0
Fork 0
Code Pull requests 7 Activity Actions
ansible/inventory/group_vars/resultsdb_dev

55 lines
2.2 KiB
Text
Raw Normal View History

adding resultsdb-dev group and resultsdb-dev01.qa host
2014-06-25 21:44:54 +00:00
---
refactoring taskotron dev to be more conformant, work with new roles
2015-09-30 21:57:21 +00:00
############################################################
# general information
############################################################
Inventory group/host variables: Sort yaml This was done using yq ( https://mikefarah.gitbook.io/yq/operators/sort-keys ) Doing things this way makes it much easier to see if a variable is set in a file or if two hosts differ in what variables they set. Hopefully we can keep things sorted moving forward. Basically this means just sort a-z anything you add to any host or group vaiable and it will be in the right place. Additionally, this enforces 'normal' intent rules for all the variable files which we should also try and obey. 2 spaces for first level, 3 for next, etc. When in doubt you can run yq on it. This should cause NO actual vairable changes, it's all just readability fixing for humans, ansible parses it exactly the same. Signed-off-by: Kevin Fenzi <kevin@scrye.com>
2021-11-16 13:27:57 -08:00
allowed_hosts:
- 10.5.124
resultsdb-dev: add fedmsg variables Try to fix fedmsg tracebacks: https://pagure.io/taskotron/issue/263 Also synchronize resultsdb-{dev,stg,prod} files a bit to allow easy comparison.
2018-05-15 13:17:22 +02:00
deployment_type: dev
Inventory group/host variables: Sort yaml This was done using yq ( https://mikefarah.gitbook.io/yq/operators/sort-keys ) Doing things this way makes it much easier to see if a variable is set in a file or if two hosts differ in what variables they set. Hopefully we can keep things sorted moving forward. Basically this means just sort a-z anything you add to any host or group vaiable and it will be in the right place. Additionally, this enforces 'normal' intent rules for all the variable files which we should also try and obey. 2 spaces for first level, 3 for next, etc. When in doubt you can run yq on it. This should cause NO actual vairable changes, it's all just readability fixing for humans, ansible parses it exactly the same. Signed-off-by: Kevin Fenzi <kevin@scrye.com>
2021-11-16 13:27:57 -08:00
execdb_db_host: "{{ execdb_db_host_machine }}"
############################################################
# execdb details
############################################################
execdb_db_host_machine: db-qa01.qa.fedoraproject.org
execdb_db_name: execdb_dev
execdb_db_password: "{{ dev_execdb_db_password }}"
execdb_db_port: 5432
execdb_db_user: "{{ dev_execdb_db_user }}"
execdb_endpoint: 'execdb'
execdb_secret_key: "{{ dev_execdb_secret_key }}"
resultsdb-dev: add fedmsg variables Try to fix fedmsg tracebacks: https://pagure.io/taskotron/issue/263 Also synchronize resultsdb-{dev,stg,prod} files a bit to allow easy comparison.
2018-05-15 13:17:22 +02:00
external_hostname: taskotron-dev.fedoraproject.org
refactoring taskotron dev to be more conformant, work with new roles
2015-09-30 21:57:21 +00:00
freezes: false
Inventory group/host variables: Sort yaml This was done using yq ( https://mikefarah.gitbook.io/yq/operators/sort-keys ) Doing things this way makes it much easier to see if a variable is set in a file or if two hosts differ in what variables they set. Hopefully we can keep things sorted moving forward. Basically this means just sort a-z anything you add to any host or group vaiable and it will be in the right place. Additionally, this enforces 'normal' intent rules for all the variable files which we should also try and obey. 2 spaces for first level, 3 for next, etc. When in doubt you can run yq on it. This should cause NO actual vairable changes, it's all just readability fixing for humans, ansible parses it exactly the same. Signed-off-by: Kevin Fenzi <kevin@scrye.com>
2021-11-16 13:27:57 -08:00
resultsdb_db_host: "{{ resultsdb_db_host_machine }}"
refactoring taskotron dev to be more conformant, work with new roles
2015-09-30 21:57:21 +00:00
############################################################
# resultsdb details
############################################################
adding resultsdb-dev group and resultsdb-dev01.qa host
2014-06-25 21:44:54 +00:00
changing resultsdb-dev01 to f22 and reworking for package installs
2015-09-30 21:40:52 +00:00
# the db_host_machine bits are so that delegation continues to work, even if
# that db is localhost relative to resultsdb
moving taskotron-stg and resultsdb-stg to f22, more refactoring for consistency
2015-10-12 23:03:44 +00:00
#
changing resultsdb-dev01 to f22 and reworking for package installs
2015-09-30 21:40:52 +00:00
resultsdb_db_host_machine: db-qa01.qa.fedoraproject.org
adding resultsdb-dev group and resultsdb-dev01.qa host
2014-06-25 21:44:54 +00:00
resultsdb_db_name: resultsdb_dev
changing resultsdb-dev01 to f22 and reworking for package installs
2015-09-30 21:40:52 +00:00
resultsdb_db_password: "{{ dev_resultsdb_db_password }}"
Inventory group/host variables: Sort yaml This was done using yq ( https://mikefarah.gitbook.io/yq/operators/sort-keys ) Doing things this way makes it much easier to see if a variable is set in a file or if two hosts differ in what variables they set. Hopefully we can keep things sorted moving forward. Basically this means just sort a-z anything you add to any host or group vaiable and it will be in the right place. Additionally, this enforces 'normal' intent rules for all the variable files which we should also try and obey. 2 spaces for first level, 3 for next, etc. When in doubt you can run yq on it. This should cause NO actual vairable changes, it's all just readability fixing for humans, ansible parses it exactly the same. Signed-off-by: Kevin Fenzi <kevin@scrye.com>
2021-11-16 13:27:57 -08:00
resultsdb_db_port: 5432
resultsdb_db_user: "{{ dev_resultsdb_db_user }}"
resultsdb_endpoint: 'resultsdb_api'
Fix small variable-name inconsistencies for resutlsdb Gets rid of quite some of the conditionals and minimizes the amount of different variable names used in result/execdb
2016-02-03 13:06:28 +00:00
############################################################
resultsdb-dev: add fedmsg variables Try to fix fedmsg tracebacks: https://pagure.io/taskotron/issue/263 Also synchronize resultsdb-{dev,stg,prod} files a bit to allow easy comparison.
2018-05-15 13:17:22 +02:00
# resultsdb-frontend details
Fix small variable-name inconsistencies for resutlsdb Gets rid of quite some of the conditionals and minimizes the amount of different variable names used in result/execdb
2016-02-03 13:06:28 +00:00
############################################################
resultsdb_fe_endpoint: "resultsdb"
fixing typo in variable name
2016-02-03 13:25:57 +00:00
resultsdb_frontend_secret_key: "{{ dev_resultsdb_frontend_secret_key }}"
Inventory group/host variables: Sort yaml This was done using yq ( https://mikefarah.gitbook.io/yq/operators/sort-keys ) Doing things this way makes it much easier to see if a variable is set in a file or if two hosts differ in what variables they set. Hopefully we can keep things sorted moving forward. Basically this means just sort a-z anything you add to any host or group vaiable and it will be in the right place. Additionally, this enforces 'normal' intent rules for all the variable files which we should also try and obey. 2 spaces for first level, 3 for next, etc. When in doubt you can run yq on it. This should cause NO actual vairable changes, it's all just readability fixing for humans, ansible parses it exactly the same. Signed-off-by: Kevin Fenzi <kevin@scrye.com>
2021-11-16 13:27:57 -08:00
resultsdb_secret_key: "{{ dev_resultsdb_secret_key }}"
tcp_ports: [80, 443, "{{ resultsdb_db_port }}", "{{ execdb_db_port }}"]
vault_db_host: "{{ vault_db_host_machine }}"
vault_db_host_machine: db-qa01.qa.fedoraproject.org
vault_db_name: vault_dev
vault_db_password: "{{ dev_vault_db_password }}"
vault_db_port: 5432
vault_db_user: "{{ dev_vault_db_user }}"
vault_endpoint: 'vault'
vault_masterkey: "{{dev_vault_masterkey}}"
Vault deployment on dev
2018-05-30 14:47:41 +02:00
############################################################
# vault details
############################################################
Add OIDC config to settings template
2018-05-31 13:41:43 +02:00
vault_public_url: "https://taskotron-dev.fedoraproject.org/vault"
Vault deployment on dev
2018-05-30 14:47:41 +02:00
vault_secret_key: "{{ dev_vault_secret_key }}"
Copy permalink