infrastructure/ansible
1
0
Fork 0
Code Pull requests 7 Activity Actions
ansible/inventory/host_vars/vmhost-x86-copr03.rdu-cc.fedoraproject.org

47 lines
1 KiB
Org Mode
Raw Normal View History

Try to make the naming of rdu-cc systems more consistent.
2021-02-16 13:26:52 -05:00
---
This pull request sets up a vmhost COPR environment in RDU-CC First we add in a vmhost_copr playbook which is basically the regular virthost but meant to limit things for copr admins via rbac. Second we add in host and group variables which will use the ansible module for setting up networks. This allows for bridging to work out of the box and makes sure we know the mac addresses.
2021-02-17 11:08:03 -05:00
br0_ipv4: 8.43.85.59
br0_ipv4_gw: "{{ gw }}"
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
br0_ipv4_nm: 24
This pull request sets up a vmhost COPR environment in RDU-CC First we add in a vmhost_copr playbook which is basically the regular virthost but meant to limit things for copr admins via rbac. Second we add in host and group variables which will use the ansible module for setting up networks. This allows for bridging to work out of the box and makes sure we know the mac addresses.
2021-02-17 11:08:03 -05:00
br0_ipv6: "2620:52:3:1:dead:beef:cafe:c003"
br0_ipv6_gw: "2620:52:3:1:ffff:ffff:ffff:fffe"
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
br0_ipv6_nm: 64
br0_port0_mac: "{{ mac0 }}"
datacenter: rdu-cc
dns: 8.8.8.8
gw: 8.43.85.254
has_ipv4: yes
has_ipv6: yes
This pull request sets up a vmhost COPR environment in RDU-CC First we add in a vmhost_copr playbook which is basically the regular virthost but meant to limit things for copr admins via rbac. Second we add in host and group variables which will use the ansible module for setting up networks. This allows for bridging to work out of the box and makes sure we know the mac addresses.
2021-02-17 11:08:03 -05:00
mac0: "f4:02:70:d3:42:48"
mac1: "f4:02:70:d3:42:49"
mac2: "b0:26:28:d1:dd:c0"
mac3: "b0:26:28:d1:dd:c1"
mac4: "b4:96:91:63:3b:50"
mac5: "b4:96:91:63:3b:51"
mac6: "b4:96:91:63:3b:52"
mac7: "b4:96:91:63:3b:53"
network_connections:
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
- autoconnect: yes
This pull request sets up a vmhost COPR environment in RDU-CC First we add in a vmhost_copr playbook which is basically the regular virthost but meant to limit things for copr admins via rbac. Second we add in host and group variables which will use the ansible module for setting up networks. This allows for bridging to work out of the box and makes sure we know the mac addresses.
2021-02-17 11:08:03 -05:00
ip:
Killed trailing spaces in group/host vars with fire. Normally it's just a nitpick to not have trailing spaces on variables. However, for some things like mac address, it really matters. Bunches of buildhw's were failing ansibile because they were passing "mac address " to linux-system-roles networking and ansible was going 'huh, nope, I can't find that mac address here at all'. So, just blow all the tailing spaces away to avoid any other variables that hit this. Signed-off-by: Kevin Fenzi <kevin@scrye.com>
2021-05-04 08:52:52 -07:00
address:
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
- "{{ br0_ipv4 }}/{{ br0_ipv4_nm }}"
- "{{ br0_ipv6 }}/{{ br0_ipv6_nm }}"
dhcp4: no
Killed trailing spaces in group/host vars with fire. Normally it's just a nitpick to not have trailing spaces on variables. However, for some things like mac address, it really matters. Bunches of buildhw's were failing ansibile because they were passing "mac address " to linux-system-roles networking and ansible was going 'huh, nope, I can't find that mac address here at all'. So, just blow all the tailing spaces away to avoid any other variables that hit this. Signed-off-by: Kevin Fenzi <kevin@scrye.com>
2021-05-04 08:52:52 -07:00
dns:
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
- 8.8.8.8
- 8.8.4.4
- 2001:4860:4860::8888
Killed trailing spaces in group/host vars with fire. Normally it's just a nitpick to not have trailing spaces on variables. However, for some things like mac address, it really matters. Bunches of buildhw's were failing ansibile because they were passing "mac address " to linux-system-roles networking and ansible was going 'huh, nope, I can't find that mac address here at all'. So, just blow all the tailing spaces away to avoid any other variables that hit this. Signed-off-by: Kevin Fenzi <kevin@scrye.com>
2021-05-04 08:52:52 -07:00
dns_search:
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
- fedoraproject.org
- vpn.fedoraproject.org
- rdu-cc.fedoraproject.org
gateway4: "{{ br0_ipv4_gw }}"
gateway6: "{{ br0_ipv6_gw }}"
name: br0
This pull request sets up a vmhost COPR environment in RDU-CC First we add in a vmhost_copr playbook which is basically the regular virthost but meant to limit things for copr admins via rbac. Second we add in host and group variables which will use the ansible module for setting up networks. This allows for bridging to work out of the box and makes sure we know the mac addresses.
2021-02-17 11:08:03 -05:00
state: up
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
type: bridge
- mac: "{{ br0_port0_mac }}"
This pull request sets up a vmhost COPR environment in RDU-CC First we add in a vmhost_copr playbook which is basically the regular virthost but meant to limit things for copr admins via rbac. Second we add in host and group variables which will use the ansible module for setting up networks. This allows for bridging to work out of the box and makes sure we know the mac addresses.
2021-02-17 11:08:03 -05:00
master: br0
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
name: br0-port0
state: up
type: ethernet
Copy permalink