Infrastructure/ansible
1
0
Fork 0
Code Issues Pull requests 6 Projects Releases Packages Wiki Activity Actions
ansible/inventory/group_vars/copr_front_dev_aws

38 lines
1.3 KiB
Text
Raw Normal View History

copr: I totally forgot to commit an inventory file for copr_front_dev_aws
2020-02-20 11:46:42 +01:00
---
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
allowlist_emails:
- msuchy@redhat.com
- praiskup@redhat.com
- jkadlcik@redhat.com
- schlupov@redhat.com
copr_fe_homedir: /usr/share/copr/coprs_frontend
copr: change copr-fe-dev.cloud.fedoraproject.org to copr.stg.fedoraproject.org
2022-02-10 16:13:16 +01:00
copr_frontend_public_hostname: "copr.stg.fedoraproject.org"
copr-fe-dev: enable kerberos for now
2022-03-17 10:57:17 +01:00
copr_kerberos_auth_enabled: true
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
copr_mbs_cli_login: Y29wcg==##vtvvikhcjncwkfkdcssv
copr_messaging_queue: "c8e11df7-e863-4ca4-99b9-d37c6663c7f7"
copr_pagure_events:
io.pagure.prod.pagure: "https://pagure.io/"
io.pagure.stg.pagure: "https://stg.pagure.io"
org.fedoraproject.prod.pagure: "https://src.fedoraproject.org/"
copr: remove dturecek
2020-10-14 06:11:04 +02:00
csi_primary_contact: "msuchy (mirek), frostyx, praiskup IRC #fedora-admin, #fedora-buildsys"
copr: I totally forgot to commit an inventory file for copr_front_dev_aws
2020-02-20 11:46:42 +01:00
csi_purpose: Provide the testing environment of copr's frontend
csi_relationship: This host is the testing environment for copr's web interface
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
csi_security_category: Low
copr: I totally forgot to commit an inventory file for copr_front_dev_aws
2020-02-20 11:46:42 +01:00
# consumed by roles/copr/certbot
letsencrypt:
certificates:
copr: change copr-fe-dev.cloud.fedoraproject.org to copr.stg.fedoraproject.org
2022-02-10 16:13:16 +01:00
copr.stg.fedoraproject.org:
copr: I totally forgot to commit an inventory file for copr_front_dev_aws
2020-02-20 11:46:42 +01:00
challenge_dir: /var/www/html
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
domains:
copr: change copr-fe-dev.cloud.fedoraproject.org to copr.stg.fedoraproject.org
2022-02-10 16:13:16 +01:00
- copr.stg.fedoraproject.org
copr-fe-dev: Let's Encrypt both stg.f.o and cloud.f.o addresses
2022-02-10 16:24:59 +01:00
- copr-fe-dev.cloud.fedoraproject.org
copr-fe-dev: create cert also for the aws hostname variant
2022-02-10 16:26:30 +01:00
- copr-fe-dev.aws.fedoraproject.org
copr: I totally forgot to commit an inventory file for copr_front_dev_aws
2020-02-20 11:46:42 +01:00
mail: copr-devel@lists.fedorahosted.org
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
predefined_deploy_script: httpd
copr: support for node_exporter on frontend (dev and prod)
2021-12-03 15:22:36 +01:00
tcp_ports: [22, 80, 443,
# node_exporter/prometheus
9100,
]
copr: define services_disabled per instance AFAIK we use `services_disabled: true` only when upgrading our severs from Fedora N to Fedora N+1 which is a big task and we go instances one by one. Maybe the easier ones in parallel but copr-backend requires full attention for sure. If we set `services_disabled: true` for the whole devl/production, we can't test if the services on each server are starting properly nor we can't run at least the frontend until all servers are ready. Let's configure the variable per instance, so whoever is upgrading it can disable/enable the services when needed.
2021-11-30 02:14:01 +01:00
services_disabled: false
copr: auto-setup the ipv6 configuration Turns out that, even though IPv6 is configured on the initial VM boot, the IPv6 needs manual tweeks and reboot (or nmcli dance). Related to: https://pavel.raiskup.cz/blog/switch-fedora-box-to-ipv6-in-aws.html
2021-11-30 13:28:59 +01:00
aws_ipv6_addr: "2600:1f18:8ee:ae00:66a:fd15:3f16:4092/128"
Reference in a new issue Copy permalink