580cd252c5
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>
15 lines
795 B
Text
15 lines
795 B
Text
---
|
|
csi_primary_contact: Fedora Admins - admin@fedoraproject.org
|
|
csi_purpose: Koji service employs a set of virtual machines to build packages for the Fedora project. This playbook is for the provisioning of a physical host for buildvm's.
|
|
csi_relationship: |
|
|
* Relies on ansible, virthost, and is monitored by nagios
|
|
* Several services rely on the builders, including koschei, Bodhi, Tagger, SCM, Darkserver.
|
|
* Builder vm's are hosted on hosts created with this playbook.
|
|
# These variables are pushed into /etc/system_identification by the base role.
|
|
# Groups and individual hosts should ovveride them with specific info.
|
|
# See http://infrastructure.fedoraproject.org/csi/security-policy/
|
|
csi_security_category: High
|
|
nested: True
|
|
nrpe_procs_crit: 1600
|
|
nrpe_procs_warn: 1500
|
|
virthost: true
|