ansible/inventory/group_vars/pdc_web

---
# Define resources for this group of hosts here.
deployment_type: prod
# These are consumed by a task in roles/fedmsg/base/main.yml
fedmsg_certs:
  - can_send:
      - logger.log
    group: sysadmin
    owner: root
    service: shell
  - can_send:
      - pdc.compose
      - pdc.rpms
      - pdc.images
    group: apache
    owner: root
    service: pdc
ipa_client_shell_groups:
  - sysadmin-mbs
  - sysadmin-noc
  - sysadmin-releng
  - sysadmin-veteran
ipa_client_sudo_groups:
  - sysadmin-mbs
  - sysadmin-releng
ipa_host_group: pdc-web
ipa_host_group_desc: Product Definition Center web app
lvm_size: 20000
mem_size: 8192
nagios_Check_Services:
  swap: false
num_cpus: 2
# This just defines the CN of the saml2 cert we pull from the private repo
# Don't be confused.  The app is actually served at apps.stg.fp.o/pdc
pdc_domain: pdc.fedoraproject.org
primary_auth_source: ipa
tcp_ports: [80]
# for systems that do not match the above - specify the same parameter in
# the host_vars/$hostname file
wsgi_fedmsg_service: pdc
wsgi_procs: 3
wsgi_threads: 2
PDC host and group vars. 2016-01-12 10:04:52 -05:00			`---`
			`# Define resources for this group of hosts here.`
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			`deployment_type: prod`
			`# These are consumed by a task in roles/fedmsg/base/main.yml`
			`fedmsg_certs:`
			`- can_send:`
			`- logger.log`
			`group: sysadmin`
			`owner: root`
			`service: shell`
			`- can_send:`
			`- pdc.compose`
			`- pdc.rpms`
			`- pdc.images`
			`group: apache`
			`owner: root`
			`service: pdc`
			`ipa_client_shell_groups:`
			`- sysadmin-mbs`
			`- sysadmin-noc`
			`- sysadmin-releng`
			`- sysadmin-veteran`
			`ipa_client_sudo_groups:`
			`- sysadmin-mbs`
			`- sysadmin-releng`
			`ipa_host_group: pdc-web`
			`ipa_host_group_desc: Product Definition Center web app`
PDC host and group vars. 2016-01-12 10:04:52 -05:00			`lvm_size: 20000`
add memory to pdc-web01 to try and keep it from hitting oom 2017-09-13 22:58:55 +00:00			`mem_size: 8192`
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			`nagios_Check_Services:`
			`swap: false`
PDC host and group vars. 2016-01-12 10:04:52 -05:00			`num_cpus: 2`
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			`# This just defines the CN of the saml2 cert we pull from the private repo`
			`# Don't be confused. The app is actually served at apps.stg.fp.o/pdc`
			`pdc_domain: pdc.fedoraproject.org`
			`primary_auth_source: ipa`
			`tcp_ports: [80]`
PDC host and group vars. 2016-01-12 10:04:52 -05:00			`# for systems that do not match the above - specify the same parameter in`
			`# the host_vars/$hostname file`
			`wsgi_fedmsg_service: pdc`
Give PDC some extra, unused fedmsg endpoints. https://pagure.io/fedora-infrastructure/issue/6482 2017-11-17 15:21:26 +00:00			`wsgi_procs: 3`
PDC host and group vars. 2016-01-12 10:04:52 -05:00			`wsgi_threads: 2`