We are introducing support for Valkey as an alternative to KeyDB (in
itself an alternative to Redis, which now has the additional problem
of its non-free license), which we are intending to switch on all
installations that do not rely on KeyDB specific features currently
not present in Valkey.
KeyDB has an uncertain future, being managed and developer by a single
vendor (Snapchat) who has stopped interacting publicly on its GitHub
project, where its primary public face developers has quit the company,
and where Snapchat is part of the corporate supporters for Valkey.
So we better start planning our escape route, before we are left with
a potentially unmaintained project that no one else is using or
supporting.
Change-Id: Idf5ab9dac4e085070dbdc6d63cddfeeaf495ca9f
(cherry picked from commit fd309a02bc)
This includes the upstream FreeSWITCH package and required modules, and
the NGCP FreeSWITCH application server.
Change-Id: I46e9684b05d767b0d80ca49c661c64775ba62d22
We only support keydb now, so we should not be installing the redis
server anymore. We add explicit dependencies on redis-tools as those
work against keydb servers too, for a smooth transition, while admins
train their muscle memory with keydb-tools.
Change-Id: I17742249462f069cb57b786884aa234765350774
1. There is no problem if the package is installed on a system which
doesn't use it.
2. It's better to install it so all the systems are equal from the
packages POV and if there is any problem - we see it on our test
systems.
Change-Id: If5b77b4f49fe95907cc9baa46ea24f8f64aa2f0b
* ngcp-task-agent is a new CE/PRO/CARRIER service
that is required to be installed on all NGCP nodes
Change-Id: I70244cb1ed752415615051635b7756d7e1b1c843
The former has been removed from Debian bookworm and replaced with a
transitional package that depends on ntpsec. Depend on the latter
directly to cover the case when the transitional package disappears
in the future.
Change-Id: Idc0f07fbad641e6904616d9e7ceff8efbe6222e6
yq is a jq wrapper for YAML documents and is useful when having to deal
with YAML files as used e.g. in cfg-schema. As of bookworm, this package
is provided by Debian.
FTR: the tool requires 854 kB of additional disk space on CE and 349 kB
of additional disk space on PRO.
Change-Id: Ifbbe61186effca008d02f477c509d9900eb7a678
The former is now in Debian bookworm a transitional package depending
on the latter. Switch the dependencies to prepare for when the package
gets removed.
Change-Id: Ic33a930b6da3071bbd3ee5a2f8ec2d7a63cbbbf4
bootlogd is a daemon to log boot messages. We introduced this back in
2014 when systemd wasn't available yet (see git rev 5340c05 + MT#6507).
Nowadays there's no need for bootlogd any longer, so let's drop it.
Noted while reviewing the lsb-base/sysvinit-utils situation for
Debian/bookworm.
Change-Id: I237a1e9cfde11923f53190d236372afb2e122521
This was an experiment to provide a CISCO-like interface for the
platform, but it does not appear to be used, and it's thus a waste of
effort, not to mention this is barely maintained right now, so there is
little point in maintaining this under life support. Remove it.
Change-Id: Id8683c8133c615292f9f47b1994842064c1cebbb
In Debian/bookworm, the glusterfs-server package got split into
glusterfs-cli package, which now provides the gluster binary, while the
glusterfs-cli is only a Recommends, therefore failing for us with:
| +23:22:28 (system_pro.inc:130): system_init_gluster_vol(): log_info 'Current node status /usr/share/ngcp-installer//system_pro.inc: line 129: gluster: command not found'
| +23:22:28 (log.inc:5): log_info(): echo 'Current node status /usr/share/ngcp-installer//system_pro.inc: line 129: gluster: command not found'
| Current node status /usr/share/ngcp-installer//system_pro.inc: line 129: gluster: command not found
This is known as https://bugs.debian.org/1023622. Until that's fixed
let's make sure we have the glusterfs-cli package, providing the gluster
binary.
FTR, in Debian/bullseye there's glusterfs-server v9.2-1, while in
Debian/bookworm we currently have glusterfs-server v10.3-1+b1, while the
glusterfs-cli is only available in bullseye-backports, bookworm +
unstable.
Change-Id: Iaec92bac0d6c2d0e388d34f278fdc32100ac0edf
This packages provides /etc/ldap/ldap.conf and ldap.conf(5), for clients
using the LDAP library. This is a Recommends from the libldap shared
library, and as such we do not automatically get it installed as we have
installation of Recommends disabled by default.
Change-Id: I32866046289a4dce3eb0911140adb03a5fa2fd03
NOTE: this is only needed for bullseye
asterisk version at bookworm 18.12.0 has opus integrated at
asterisk-modules already
Change-Id: I9b410fbc1fd93ed41199bcbfe3fbbe3d823fc807
We have to remove dependency on the 'sems-modules' package for the
cloudpbx-pro, since from now on the 'sems-modules' repo is
deprecated and all plug-in's are being built using sems-pbx
repository.
Change-Id: I4a32bddde735dce7234bd4fed0812c6de12dce70
This was being pulled in transitively by ngcp-rtcengine, which we no
longer install. Add an explicit dependency on coturn to avoid losing
wanted packages on the platform.
Change-Id: I723581508cde9ea76cd95b6d9817d4908e42bc74
Starting with mr10.5 the rtcengine and janus support is obsolete and no
longer available. NGCP already has WebRTC support for video calls on CSC.
Change-Id: I974147560d03f1652cbec9936c4f458b89f0db60
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
We depended on this from the ngcp-check-tools package, as that was a
direct user of these tools. But since we have removed explicit checks
for database replication discrepancies, there's no use for that there
anymore. But these tools are useful for diagnosing database problems,
so let's move the dependencies into the addons packages.
Change-Id: Id6d66330424cd24d3e199afc2d8955e8c1ba3ba3
In commit 678ec8e272 execution of wrap-and-sort was skipped,
so nowadays we get those re-orderings whenever we modify the file.
Fix this, by execution of `wrap-and-sort -tas`, to look as expected.
Change-Id: I999834d2ab323bfe4c80cc76e309f020c3593f4e
We want to run smartd AKA smartmontools service on our physical
installations (it is running only outside of virtual environments) and
want to be able to execute smartctl on our systems, so ship
smartmontools through our ngcp-services-* meta packages.
Change-Id: I215dc89c148cb10d3830c289293e67e36f840427
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
We use ffproxy to provide HTTPS connectivity to the license server for
all nodes of a carrier via one of the internet-connected nodes.
Change-Id: I84976375943962adf795a02f47f9303927d2e694
Starting with mr10.0 the default is going to be Corosync/Pacemaker, with
the expectation that previous versions will already upgrade after having
been migrated.
Change-Id: Icb1fbaa62f95de64651f139629e45fe7445c3dd8
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
Guillem Jover
Mykola Malkov
Kirill Solomko
Michael Prokop
Victor Seva
Marco Capetta
Donat Zenichev
Alexander Lutay
Richard Fuchs