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

72 lines
2 KiB
Text
Raw Normal View History

copr-be-dev-aws: disable services for the beginning
2020-02-19 21:28:50 +01:00
---
copr_dev_aws: replace copr_dev entirely
2020-02-19 23:16:36 +01:00
_forward_src: "forward_dev"
copr-be: define aws_arch_subnets
2021-10-08 16:09:20 +02:00
aws_arch_subnets:
# Your requested instance type (a1.xlarge) is not supported in your requested Availability Zone (us-east-1a).
# Your requested instance type (a1.xlarge) is not supported in your requested Availability Zone (us-east-1d).
# Your requested instance type (a1.xlarge) is not supported in your requested Availability Zone (us-east-1f).
aarch64:
- subnet-0995f6a466849f4c3
- subnet-08cadf5a14b530ac4
- subnet-07b0b3168a353e3ee
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
x86_64:
- subnet-0995f6a466849f4c3
- subnet-08cadf5a14b530ac4
- subnet-07b0b3168a353e3ee
- subnet-09c74a3e6420a206b
- subnet-01d4e967ab5e78005
- subnet-05437ac82d63b6ef5
backend_base_url: "https://download.copr-dev.fedorainfracloud.org"
builders:
# max|spawn_concurrently|prealloc
aws:
aarch64: [2, 1, 1]
x86_64: [4, 1, 1]
aws_spot:
aarch64: [5, 2, 1]
x86_64: [5, 2, 2]
ppc64le_hypervisor_01:
ppc64le: [2, 1, 1]
ppc64le_hypervisor_02:
ppc64le: [2, 1, 1]
x86_hypervisor_01:
x86_64: [2, 1, 1]
x86_hypervisor_02:
x86_64: [2, 1, 1]
x86_hypervisor_03:
x86_64: [2, 1, 1]
x86_hypervisor_04:
x86_64: [2, 1, 1]
copr-be: deploy native s390x and Red Hat subscription to prod While on it, setup the builder quota for max: 12 ATM, and we'll communicate with IBM later if that's enough.
2022-01-17 10:01:02 +01:00
ibm_cloud_tokyo:
s390x: [2, 1, 1]
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_aws_region: us-east-1
# don't forget to update ip in ./copr-keygen-stg, due to custom firewall rules
copr-be: define aws_arch_subnets
2021-10-08 16:09:20 +02: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
# eth0, eth1
copr_backend_ips: ["18.208.10.131", "172.30.2.207"]
copr-builder: cleanup provision scripts - add copr_builder_fedora_version variable, because production sometimes differs from devel for a short period of time - drop the epel-8 -> centos-stream+epel-8 links, this is now done all against RHEL - katello hack package is not in s390x images anymore, since we generate the images by 'copr-image', not by IBM Cloud snapshots - kernel-core is now fixed for aws builders, update it as well as other packages when updating the image - don't install subscription-manager when spawning builder, it is already available from image preparation time - copr-rh-subscribe.sh script is also prepare_base_image only - we don't modify /etc/copr-rpmbuild/mock.cfg.j2 for quite some time, drop the hack - the /usr/bin/copr-update-builder is fixed upstream, drop the lineinfile hack - epel-8 configs are installed via files/mock/epel now - no need to touch /etc/rpkg.conf nowadays on f35 - prepare mockbuilder user only when preparing image, not spawning - disable coredumps only when preparing the image - disable services only when preparing the image - don't update rubygem-gem2rpm all the time, on F35 we have new enough version - the /etc/copr-rpmbuild/rpkg.conf.j2 is to be kept as is on F35
2022-01-25 13:43:51 +01:00
copr_builder_fedora_version: 35
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_builder_images:
aws:
copr-be-dev: update F35 images once more - AWS images have a frozen kernel for now (rhbz#2047266) - others have disabled systemd-resolved
2022-01-28 12:35:11 +01:00
aarch64: ami-04d4eac8f0465ca74
x86_64: ami-07d7f4f012b9383c5
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
hypervisor:
copr-be-dev: update F35 images once more - AWS images have a frozen kernel for now (rhbz#2047266) - others have disabled systemd-resolved
2022-01-28 12:35:11 +01:00
ppc64le: copr-builder-ppc64le-20220128_112330
x86_64: copr-builder-x86_64-20220128_111926
copr-builders: new s390x IBM Cloud image
2022-01-08 14:05:30 +01:00
ibm_cloud:
copr-be-dev: update F35 images once more - AWS images have a frozen kernel for now (rhbz#2047266) - others have disabled systemd-resolved
2022-01-28 12:35:11 +01:00
s390x: r022-35a52110-fa0a-4df6-be88-7f9480180073
copr-builders: instantiate Power9 Oregon University OpenStack
2022-01-12 15:29:34 +01:00
osuosl:
copr-be-dev: update F35 images once more - AWS images have a frozen kernel for now (rhbz#2047266) - others have disabled systemd-resolved
2022-01-28 12:35:11 +01:00
ppc64le: copr-builder-ppc64le-20220128_112330
copr-be: deploy F35 builders to production
2022-01-28 14:08:38 +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
copr_messaging: true
datacenter: aws
devel: true
dist_git_base_url: "copr-dist-git-dev.fedorainfracloud.org"
copr: change copr-fe-dev.cloud.fedoraproject.org to copr.stg.fedoraproject.org
2022-02-10 16:13:16 +01:00
frontend_base_url: "https://copr.stg.fedoraproject.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
keygen_host: "54.225.23.248"
postfix_group: copr
copr: set rpm_vendor_copr_name to Fedora Copr
2020-12-07 17:35:55 +01:00
rpm_vendor_copr_name: Fedora Copr (devel)
copr-dev: re-enable services
2021-11-22 13:26:59 +01:00
services_disabled: false
copr-be: configure the AWS CloudFront distribution ID Relates: https://pagure.io/copr/copr/pull-request/2119
2022-03-15 16:17:16 +01:00
aws_cloudfront_distribution: EX55ITR8LVMOH
Reference in a new issue Copy permalink