Feature #5055
closed
set up two additional rpi4-deb9build slaves
Added by laforge about 3 years ago.
Updated about 3 years ago.
Description
It has been pointed out that sometimes (heavy osmo-trx development activity), the single rpi4-deb9build slave is too slow to handle all the builds.
I've purchased two more 8GB raspi4 units, and will bring them to AM93 tomorrow, and bring them online in the 10.9.25.x/24 network.
Once they are up and running (should be tomorrow), I'll install the debian9 lxc container.
I'll leave it to
osmith to then
- apply the ansible playbook for creating a jenkins slave
- create the slaves in jenkins
- create some kind of group ("label") for rpi4 builds
- make all 4 rpi4-deb9build slaves share that label
- make existing build jobs use that label instead of the specific rpi4-deb9build slave directly
- Status changed from New to Stalled
some network relatd problems came up, expect to deploy the units tomorrow.
- Status changed from Stalled to New
- Assignee changed from osmith to roh
the two pre-configured (SSH, fixed IP) RPI4 units + power supplies (+ uHDMI adapter, + label for the existing one) are with Maike an will be in AM93 today.
roh, please connect them tomorrow. I think for now it is best to simply put them next to the first rpi4-deb9build. We can think of a more proper solution later on. Once connected , plesae re-assign to osmith.
Oliver: They underlying rapsbian will be coming up at 10.9.25.60 and 10.9.25.70 (standard pi/raspberry/sudo at the moment, no ssh keys installed yet). The lxc for debian9 will have to be created. Please make sure to use bridged mode on lxcbr0 with static IP of 10.9.25.61 and 10.9.25.71 for the deb9build lxc containers.
- Status changed from New to In Progress
- Assignee changed from roh to osmith
- % Done changed from 0 to 20
physical setup done.
the machines are now reachable.
rpi4-1 dc:a6:32:4a:4b:ba 25 10.9.25.50 raspberry pi buildhost for jenkins
rpi4-2 dc:a6:32:d6:76:5c 25 10.9.25.60 raspberry pi buildhost for jenkins
rpi4-3 dc:a6:32:d6:76:70 25 10.9.25.70 raspberry pi buildhost for jenkins
osmith please send me a sshkey (mail or jabber) to add to the old(first) host, so you have access there too.
ps: one micro-hdmi adapter is with the 3 rpi, the other one is in the hdmi slk in office1.
On Fri, Mar 05, 2021 at 03:52:29PM +0000, roh [REDMINE] wrote:
osmith please send me a sshkey (mail or jabber) to add to the old(first) host, so you have access there too.
I've added osmith' key to all three now.
SSH login works, I'm proceeding with set up.
- % Done changed from 20 to 50
- % Done changed from 50 to 80
The permission error is fixed now, it was caused by jenkins user not having UID=1000.
gerrit-osmo-pcu is working again.
- % Done changed from 80 to 90
- % Done changed from 90 to 80
master-osmo-bts and master-osmo-trx failures are a regression of the new raspberry pi setup. Both jobs were not building in docker yet. I'm migrating them to docker.
For master-osmo-bts, this works already (jenkins job adjusted, I'll push the config to gerrit once osmo-trx also works).
master-osmo-trx needs liblimesuite-dev to be added to the debian-stretch-jenkins docker image. I'm currently verifying that this makes the build pass.
- % Done changed from 80 to 90
master-osmo-{trx,bts} work again.
Related patches:
- Status changed from In Progress to Resolved
- % Done changed from 90 to 100
Also available in: Atom
PDF