We are no longer using the bkernel role (using the old card thats in
buildhw-x86-01), so this removes that role and mentions of it.
Also, because we are urgently building kernels all the time now,
add one more buildhw-x86 and one more buildhw-a64 to secure-boot channel
so we can build more/faster kernels.
Signed-off-by: Kevin Fenzi <kevin@scrye.com>
pesign needs to map the socket into the chroot/container, but also set
acls to allow the users in the container to use it. We setup a
secureboot group to map these builders and only run this setup on them.
For now buildhw-x86-02 is the only builder we want to enable.
Once we know it's working well we can retire the bkernel role and repave
buildhw-x86-01. buildhw-a64-02 will be added once we fix the aarch64
signing.
Signed-off-by: Kevin Fenzi <kevin@scrye.com>
This isn't really a 'buildhw', but it's pretty close.
It's an lpar on a power10 box.
I'm making it a hw builder in staging because if we tried to make
it a bvmhost and put vm's on it, we would need to setup macvtap, which
would be fine, but extra complication where we don't really need it in
staging currently.
01 will be created once we reconfigure the one thats currently serving
as bvmhost-p10-01. Which will happen after we move 1/2 the builders
off to a new bvmhost-p10-02 lpar on this same second power10.
Signed-off-by: Kevin Fenzi <kevin@scrye.com>
bvmhost-a64-05 has less memory than 01-04, so fewer buildvm's on it.
However, even with that it sometimes is OOM killing one.
So, lets drop 48 for now to give it more free memory.
Signed-off-by: Kevin Fenzi <kevin@scrye.com>
These are various machines that are not yet deployed, or no longer exist
in rdu3 (though they did in iad2). This should clean up nagios
a fair bit and when/if we redeploy these we can add them back in.
Signed-off-by: Kevin Fenzi <kevin@scrye.com>
Note that these don't do nested virt due to the way we have the host
setup. We are working on changing that, but for now, this should work
fine for normal builds. Only parts of composes that need nested virt
will fail for a week or so until we get a power9 moved to the new dc
or reconfigure a power10 box.
Signed-off-by: Kevin Fenzi <kevin@scrye.com>
This machine has a smart card in it for secure boot signing,
so use it for now for the dc move and then we will move to
the new signing setup that can just use (select) buildvm's and
sigul.
Signed-off-by: Kevin Fenzi <kevin@scrye.com>
This sets up a compose/db/koji for riscv in rdu3.
Along with the two x86 builders.
Once this is deployed, need to sync database over and upgrade it,
then switch dns and it should be back.
Signed-off-by: Kevin Fenzi <kevin@scrye.com>
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>
