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
The package needs to be installed to avoid the following message in installation
logs, which if nothing else, is noisy:
debconf: delaying package configuration, since apt-utils is not installed
Change-Id: I692b5ea618ce27e58a8d085630a64166b2441198
It was added to CE and PRO, but missed to Carrier case.
We still have ngcp-services-carrier because ngcp-installer
is not yet merged. I have compared ngcp-services-pro and
ngcp-services-carrier and difference there is only ngcp-installer.
Change-Id: I74b078b242741203c90b57ac1e6d349420d1430f
The metapackage depends on ngcp-prosody-modules and this one already depends on
prosody, so while reviewing the changes necessary for the task we stumbled upon
these explicit dependencies on prosody and thought that it was better to remove
them (and the versions mentioned are out of date, in any case).
Change-Id: I72b70e4106c4def20fbffbb638bbe7f58eacce91
[gjover@sipwise.com:
- Use alternative dependencies to heartbeat-2. ]
Change-Id: I072cd2fb1e698f4aa9b6206bc06d09240b12bdd3
Signed-off-by: Guillem Jover <gjover@sipwise.com>
This expresses more correctly the purpose of the packages. We do not
create transitional packages, because they fail piuparts, and are not
needed for smooth upgrades, as our main metapackages already depend
on every subpackage. And extend the description to make the purpose
of the packages more clear.
Change-Id: Id9dc574855ad683057aca67e37145c121123c6e1
logrotate has Priority important, but doesn't need to exist on a
Debian system, so ensure it's there, since we rely on it.
Change-Id: I283096532efe3ad5bcf35fe506f3c8d099635b39
Remove etckeeper, which is required already by ngcpcfg.
Remove libtemplate-perl, which is required already by its users.
Change-Id: I33b9bcc283ca677a6b39280675551054679e48ff
Move apt-transport-https from nth to services, as this packages is
always required to be able to use HTTPS connections. We also switch
the dependency to have apt (>= 1.5) as alternative so that the package
is not pulled in anymore in newer releases where it is a transitional
dummy package.
Change-Id: I612ea202e4fbc17f9dbb9ac7046d152bca94bf88
We move them from ngcp-status, which is a package that gets installed on
all NGCP variants, into the PRO/CARRIER specifig nth metapackage.
Change-Id: I89b4cb00ff83af6b6c5b3f120ba85680c96989ff
Current Debian/buster provides mariadb-client-10.3.
There's no need to depend on a specific version,
as there's a metapackage depending on the latest version:
| % apt-cache show mariadb-client | grep Depends
| Depends: mariadb-client-10.3 (>= 1:10.3.13-1)
Change-Id: Ib13bbc7e004f9eb7f233235a362415c698e789b5
This package should be a dependency of the code actually using it. And
this is not a case of the code being optionally used when available, so
we should not be depending explicitly on it here.
Change-Id: I6f0fd555c46572a6724c2bc94498cd1d19a08fda
We have configuration setup for snmptrapd to help debugging or for local
triggers. But if the local admin enables it, the package will be missing.
Let's install it by default, because it's a very tiny binary, which will
not be started as long as it's not enabled.
Change-Id: Ibe3952d9b017637cf7bd05a51558d6922ba74f78
We need tool 'sgdisk' to restore software RAID in case one disk
has been replaced. See the ticket for SW-RAID recovery steps.
Change-Id: I67393ef1e66b45011092c932ee6663bad2445e8b
This is https://bugs.debian.org/875708 in Debian and fixed for unstable/testing
("buster"), but that's in stable and unfixed for 1+ years there, so it's even
likely that it will not be fixed for stretch.
Change-Id: Idd5258176e19929a182d12d479189cbed5a81e3c
PRO/Carrer mr6.5+ are based on software RAID,
we need to provide ability to match Linux disk
to the real hardware by blinking the LED indicator.
Change-Id: I21c071c73277c467ed707f59302cab05d857b1f5
Otherwise when deploying to a system with EFI support
grub-efi-amd64 gets removed and leaves an unbootable system
behind.
Change-Id: Idd359a2916369e75598ec18b01ce40582ac061a4
On Debian/buster we don't need ngcp-intel-i40e-dkms,
so if linux-image-amd64 >= 4.17 is present then
don't depend on ngcp-intel-i40e-dkms.
Change-Id: Ia406c7807c66566f06d3e86aa821641301e2f750
Guillem Jover
Mykola Malkov
Victor Seva
Sipwise Jenkins Builder
Manuel Montecelo
Alexander Lutay
Andreas Granig
Michael Prokop
Richard Fuchs
Kirill Solomko