It should be ok to deploy these before koji exists there.
kojid won't start without intervention, so we should be able to deploy
and start it when koji is ready.
Signed-off-by: Kevin Fenzi <kevin@scrye.com>
This will allow us to use a group_vars/rdu3_production/staging to set
variables for all those hosts and more clearly allow us to see whats in
which datacenter (hopefully).
Signed-off-by: Kevin Fenzi <kevin@scrye.com>
We want a pair of x86_64 buildvm's to do tasks that don't need to be on
a riscv instance (create/newrepos, etc).
So adjust playbooks and add them.
Signed-off-by: Kevin Fenzi <kevin@scrye.com>
webkitgtk is unable to finish building on the current builders, so
lets drop one and add memory to another. Will make 20 the only one in
the heavybuilder channel for it. Hopefully this will get it to complete.
Signed-off-by: Kevin Fenzi <kevin@scrye.com>
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 moved them to f40 via upgrade, sync up ansible to match so that when
we reinstall them they will get 40 instead of 39
Signed-off-by: Kevin Fenzi <kevin@scrye.com>
We have these 7 emags that were bvmhosts running 32bit arm builders.
Since we no longer need those, lets repurpose them as aarch64 buildhw.
Signed-off-by: Kevin Fenzi <kevin@scrye.com>
We have 4 of the new mt snow boxes that were bvmhosts before, but we
moved the vm's to the newer generation versions, so we should use these
as buildhw boxes. I plan to add 2 of them to the runroot channel for
composes and 2 of them general builders in the heavybuild channel to
help with chromium builds.
Signed-off-by: Kevin Fenzi <kevin@scrye.com>
This removes osbs and allmost all it's associated playbooks and files.
It served long and well, but we no longer need it.
flatpaks are building with a koji-flatpak plugin.
base/minimal/toolbox containers are building with kiwi.
We aren't building any other containers right now, and we did they could
be added to kiwi.
This is the end of an era... I look with nostolga on
ansible-ansible-openshift-ansible (a role to setup ansible on a control
host and run it from our ansible).
Good bye osbs!
Signed-off-by: Kevin Fenzi <kevin@scrye.com>
We want to move (well, really re-install) all these over on the new lpar
in rdu. This will have much higher stats and be in general faster by
both network and cpu. Hopefully all these will replace all the old
boston ones.
We may need to break these up some more into smaller vm's if the number
isn't able to keep up ok. We can adjust after things are all working.
Signed-off-by: Kevin Fenzi <kevin@scrye.com>
Lets move this vm over to rdu, and set it up as a new varnish cache.
This way we can test 01 doing builds before moving others.
Signed-off-by: Kevin Fenzi <kevin@scrye.com>
This is a new z16 lpar in rdu.
This is for staging.
We should not mess with its network because it has a nice weird bonded
set of interfaces that we have a bridge on top of.
Set to make a new buildvm-s390x-01.stg on it.
Signed-off-by: Kevin Fenzi <kevin@scrye.com>
These machines are newer versions of bvmhost-a64-12/13/14/15
They have more cpus, so we will be moving the buildvm-a64's over to
them, and then turning the 4 old bvmhost's into buildhw's.
Signed-off-by: Kevin Fenzi <kevin@scrye.com>
We need these builders in staging to also be in the osbuild group so
they get the iptables rule to allow them to talk to osbuild api.
Signed-off-by: Kevin Fenzi <kevin@scrye.com>
This new arm box was going to be for staging, but we are ok with the old
out of warentee emag there for now while we ask for more replacements.
Moving this to openqa could help us keep up on aarch64 testing.
Signed-off-by: Kevin Fenzi <kevin@scrye.com>
We have been having issues with webkitgtk not being able to build due to
memory constraints on the existing builders. Also, we are overcomitted
on memory on the kvm lpar. So, to hopefully fix this:
* remove 3 existing builders.
* just leave the 3 cpus and 17gb memory from one free for the host
* make 2 of the other builders double the size in memory, cpu and disk.
* Will add these 2 to the heavybuilder channel and hopefully webkitgtk
will be happy again.
I'm a bit concerned that this might slow the mass rebuild down, but we
will see. :)
Signed-off-by: Kevin Fenzi <kevin@scrye.com>
