Cellular Network Infrastructure » Radio Access Network » OsmoTRX

some network relatd problems came up, expect to deploy the units tomorrow.

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.

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.

SSH login works, I'm proceeding with set up.

I've missed the lxc container part and directly set up the raspian10 hosts as jenkins nodes.

Most of the jenkins jobs utilize docker, so for the original plan we would need to get docker in deb9 in lxc on raspian 10 running. But Harald told me he already tried it, and it doesn't work out of the box because of kernel incompatibilities, and that he already spent four hours on it. Since most jobs run in docker anyway, we decided to keep the setup with having raspbian10 configured as jenkins node without the lxc in-between.

• 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

All done. New label:
https://jenkins.osmocom.org/jenkins/label/rpi4-raspbian10/

Related patches:
https://gerrit.osmocom.org/q/topic:new-raspberries

I'm fixing up permission errors now:
https://jenkins.osmocom.org/jenkins/job/gerrit-osmo-pcu/1818/FIRMWARE_VERSION=master,WITH_MANUALS=0,label=rpi4-raspbian10,with_dsp=none,with_vty=False/console

The permission error is fixed now, it was caused by jenkins user not having UID=1000.

• https://gerrit.osmocom.org/c/osmo-ci/+/23274 ansible: explicitly give jenkins user UID=1000
• https://gerrit.osmocom.org/c/osmo-ci/+/23275 ansible: remove raspbian default user "pi"

gerrit-osmo-pcu is working again.

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.

master-osmo-{trx,bts} work again.

• https://gerrit.osmocom.org/c/osmo-ci/+/23283
• https://gerrit.osmocom.org/c/docker-playground/+/23280