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

23 lines
702 B
Text
Raw Normal View History

Unify copr prod and dev playbooks
2014-09-05 15:38:22 +02:00
---
[WIP] Copr playbooks refactoring using ansible roles, new role for copr-keygen
2014-10-10 12:35:14 +02:00
#_forward-src: "{{ files }}/copr/forward-dev"
_forward_src: "forward_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
backend_base_url: "https://download.copr-dev.fedorainfracloud.org"
builders:
# max|max_spawn|max_prealloc
aws:
aarch64: [5, 2, 2]
armhfp: [3, 1, 1]
x86_64: [20, 5, 5]
copr_aws_region: us-east-1
[copr] further restrict access to keygen host
2015-02-17 10:58:01 +01:00
# don't forget to update ip in ./copr-keygen-stg, due to custom firewall rules
[copr] update ips for the new cloud
2015-05-18 22:57:27 +02:00
copr: production: keygen <-> backend IP connection
2019-07-18 10:57:34 +02:00
# eth0, eth1
copr: dev: fix backend <--> keygen IPs
2019-07-26 16:47:17 +02:00
copr_backend_ips: ["172.25.33.80", "172.25.144.254"]
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
devel: true
dist_git_base_url: "copr-dist-git-dev.fedorainfracloud.org"
frontend_base_url: "https://copr-fe-dev.cloud.fedoraproject.org"
Upgrade copr-keygen-dev IP after upgrade to F30
2019-07-11 19:44:12 +02:00
keygen_host: "172.25.33.73"
[copr] variable should contain path to config postfix_maincf: "postfix/main.cf/main.cf.copr"; also enable for production
2015-04-20 17:55:53 +02:00
postfix_maincf: "postfix/main.cf/main.cf.copr"
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
resolvconf: "resolv.conf/cloud"
copr: disable services in group_vars/copr_dev
2020-02-21 12:44:18 +01:00
services_disabled: true
Copy permalink