It's not actually being built by any job, and its contents are anyway
wrong since it basically pulls in the same as the sysmocom-nitb-image.
Initially it made sense to have these 2 images because we either
connected the BTS to osmo-bsc or osmo-nitb. This is no longer the case
since we deprecated osmo-nitb, and now it always connects to osmo-bsc.
The initiall idea after osmo-nitb split was to have a sysmo-bsc-image
containing only osmo-bsc, and then a sysmocom-nitb-image superseeding
it by installing all other core network components such as hlr, msc, etc.
Since there's no real need for that now, and in any case we can just
duse the nitb one and disable the extra services, let's drop the bsc
one.
This way we have it too in sysmocom-nitb-image, but only when needed,
that is: when we build for a machine inheritinh from sysmocom-bsc, which
is a machine not containing any BTS HW and thus requires a BTS connected
to it, so it needs a DNS server to serve it.
Since osmo-msc a2353c69cc3d2ccc7caee4571b3b8d2a98961150 and
osmo-bsc 3561bd48976dbee8dbd4659dad15be85a3e79ace osmo-bsc-mgcp support
is dropped in favour of osmo-mgw and one instance of osmo-mgw can be
shared between osmo-msc and osmo-bsc.
osmo-mgw recipe in meta-telephony has been updated to generate several
packages. Right now, osmo-bsc requires osmo-mgw service, but osmo-msc
still requires osmo-bsc-mgcp, so let's add both to the image.
This new package group contains what used to be the "task-sysmocom"
group, with an osmo-nitb. In turn, task-sysmocom.bb will be changed to
use new git repositories.
When restoring the backup the rootfs is mounted in /rootfs/data
and the symlink to the real file would then not work. Attempt to
change the directory first to get a relative symlink.
Untested change and needed for rauc
The configuration scripts are named for the systemd units for which they
generate configuration files. The generator causes them to run before
those units are started.
* use printf instead of echo
* add missing /etc/ for the udhcpc-default file
* add log-entries for all shell actions in the
post image setup
* generate comments in all files which are touched
Related: SYS#1774
We can not have sysmocom-backup-default and sysmocom-backup-data-default
installed at the same time. I don't want to play games with RREPLACE and
RPROVIDES either. So simply use one of the two files. Copy the two more
default values over to the other recipe.
Create a sysmocom-nitb-rauc-image and create a rauc packagegroup
with the default depdencies and an include file to be used by
other images. This assumes that sysmocom-image.inc has been
included first.
With the ro image we have a cheap way to figure out which
files were changed. We can run cmp between the to be backed
up file. This way the stored data will be minimal in the
sense of changed files.
Pau Espin
Harald Welte
Holger Hans Peter Freyther
Max
Daniel Willmann
Jan Luebbe
Henning Heinold