We no longer need to keep any config around from boston, so nuke that.
All the buildvm's are now kvm, so we don't need a seperate group/config
for that, so remove it.
Consolidate the variables down to buildvm_s390x group and only have ip
address for host vars.
Signed-off-by: Kevin Fenzi <kevin@scrye.com>
We can consolidate a bunch of things here in group vars that was in
host vars and avoid a bunch of duplication. So, now: all the
buildvm_s390x builders are in that group, but there's now a
buildvm_s390x_kvm and buildvm_s390x_zvm for those seperate lpars and
those define the default network setup for each lpar. Finally the hosts
vars only now needs to have the ip addresses.
Signed-off-by: Kevin Fenzi <kevin@scrye.com>
Turns out the current version of linux-system-roles network doesn't like
setting ipv6 no and setting search domains since NetworkManager wants to
set them for both ipv4 and ipv6. There's some upstream fix, but not in
our current version.
Signed-off-by: Kevin Fenzi <kevin@scrye.com>
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>
