We add optional support for ntpd, as some customers have demanded it
back. While preserving timesyncd as the default.
We need to add ntp as an alternative dependency to systemd-timesyncd,
although our policy is to install all services (even when disabled),
so that the service can be enabled or switched just via configuration
changes. But in this case all time-servers Conflicts/Replaces with each
other, so we cannot have them all installed, and that will require
administrator intervention.
Change-Id: I75c25010c3c12dfeda0c0297c7cea57076ae1bf5
(cherry picked from commit c750629785)
See https://metadata.ftp-master.debian.org/changelogs//main/s/systemd/systemd_247.3-7_changelog
> Demote systemd-timesyncd from Depends to Recommends.
>
> This avoids a dependency cycle between systemd and systemd-timesyncd and
> thus makes dist upgrades more predictable and robust.
> It also allows minimal, systemd based containers where no NTP client is
> strictly necessary.
> To ensure that systemd-timesyncd is installed in a default installation
> created by d-i, bump its priority to standard.
> (Closes: #986651, #993947)
Change-Id: I1db174936605fd1012ac54c7ee5f147e82daa619
(cherry picked from commit 18d2e57aaa)
We used to have it on our systems, though it was pulled in via
dependency of prometheus-node-exporter. Recent versions of
prometheus-node-exporter (as present in bullseye) no longer depend on
moreutils though, therefore explicitly add it to our package list.
Change-Id: Ic352fde5f82d7d04e070a7640129f7cbf3f741e8
The dependencies should be in the metapackage, as there's no dependency
at all for any of the Prometheus exporters, and there's just an indirect
dependency on the database services, but we do not usually list them as
dependencies anyway (f.ex. mariadb) in ngcp-check-tools. This also makes
it possible to not depend on PRO/Carrier specific packages on CE systems.
Change-Id: I68e0d3fc26753c629712d94c85fc3d76ed212ae7
systemd-coredump in systemd versions >=246 uses zstd as the default.
Now having 247.1-3 in current Debian/bullseye, we should have zstd
available out-of-the-box for dealing with compressed coredump files
(which are zstd by default). Given that zstd is available also in
Debian/buster, let's add it to ngcp-services-{ce,pro}.
Change-Id: I7fddd253c93f32ec7cb8f38900feab73218b2cf9
We depend on a working cron service in ngcp-installer:
| 2020-12-17 22:07:16 spce: Synchronizing current with expected services state
| Failed to start cron.service: Unit cron.service not found.
| +22:07:17 (cfg.inc:450): cfg_apply_configs_default(): log_die 'Can not apply configuration'
| +22:07:17 (log.inc:27): log_die(): echo 'ABORTED: Can not apply configuration'
| ABORTED: Can not apply configuration
We don't have an explicit dependency on cron though:
| $ aptitude why cron
| i ngcp-ngcp-ce Depends ngcp-services-ce
| i A ngcp-services-ce Depends logrotate
| i A logrotate Depends cron | anacron | cron-daemon | systemd-sysv
We have systemd-sysv present, so cron isn't necessarily pulled in any
longer automatically (at least with apt's resolver as present in current
Debian/bullseye). So explicitly depend on cron package.
Change-Id: I3a46f853dfcfca5a0737553eaa35ffbf8342a7cf
From the packages' deps and content POV Pro and Carrier packages are
equal to each other so get rid of this separation.
Change-Id: I99132cb979b33945ca19c27c34308d29573aaea8
Adding a Conflicts/Provides/Replaces on ngcp-addons makes these
metapackages not coinstallable, which is what we want here.
Change-Id: Ie6036b93929eed54a854d2e705f452a35316dcce
We have received a green light for ngcp-admin-ui from CTO,
we are going to make it reachable for mr8.5+ to gather the
very initial customer's feedback and correct our vision/plans if necessary.
ngcp-admin-ui will be disabled by default in mr8.5,
it will be enabled for the necessary installations only.
It is safe to install the package right now from the security point of view.
Also "wrap-and-sort -sat" list of dependencies here.
Change-Id: I9c69982799ed776eb8188bd0ea4d018441a34db6
The systemd-timesyncd is shipped in the systemd package in Debian
buster, but is being split into its own package in Debian bullseye.
So we prepare for the transition.
Change-Id: I73af67dc338a21a32ea3145e4f9ed280b7c8f3b0
We are switching to prometheus, so the influxdb packages are not needed
anymore. And this one is safe to remove anyway as ngcp-check-tools
already depends on it.
Change-Id: I999cb4327c02bcaaefaae0acd1ec254a777cbc15
The packages ngcp-service-pro and ngcp-service-carrier are equal so use
ngcp-service-pro for Carrier.
Remove ngcp-service-carrier package.
Change-Id: Iaa39e70c37e5dbb40b753e932baa6868da6a310f
This is just another part of our monitoring, so let's make it easy to
use after installation and in production environments.
Change-Id: Ie30680e2dd48c9b5cf6419a5cf770c253b3d8cf9
We need to add a metapackage indirection so that we can select the image
and headers packages that match.
This is a problem on cloud systems, where the installed and running
kernel is a cloud variant, but we are pulling in a non-cloud image and
headers, which will be used by dkms when building kernel modules, but
not for the running one.
By adding this indirection we specify that we need both the image and
the headers to match, preferring the stock versions, but selecting the
cloud headers if such kernel image is already installed.
Change-Id: I85e76ff56e6796c4315ebe6bef2e19e63cb7b362
This module got split out from libngcp-bulkprocessor-perl, as some of
the actual project implementation modules, with tools, which act as
the frontend.
Eventually the tools might get split out into their own package, but
for now we should depend on the new package on PRO which is the one
that provides some of the actual end-user functionality.
Change-Id: I54bbb9ac22a306c2da2040badee4bdecfc966257
Sipwise Jenkins Builder
Guillem Jover
Alexander Lutay
Michael Prokop
Victor Seva
Mykola Malkov