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
wget's Priority was downgraded from "important"
to "standard" in Debian, so it's no longer present
by default starting with Debian/buster.
Change-Id: I5dc822c33baa63423ac3b699e95ef0862edd8e70
Otherwise NGCP cannot be installed:
> (spce)root@spce:/# apt-get install ngcp-intel-i40e
> ...
> Package ngcp-intel-i40e is not available, but is referred to by another package.
> This may mean that the package is missing, has been obsoleted, or
> is only available from another source
>
> E: Package 'ngcp-intel-i40e' has no installation candidate
> ...
> (spce)root@spce:/# apt-cache search ngcp-intel-i40e
> ngcp-intel-i40e-dkms - dkms source for the intel i40e
Change-Id: I8959379fa4b51ceb3edf34477161a9a533f533ad
According to Volodymyr's comment in review
https://gerrit.mgm.sipwise.com/#/c/22904/1/debian/control@565
> ... all system that I saw have tg3 driver in use
> (except non supported UPCAT/UPCRO).
> So I think we do not need this package.
those drivers are no longer necessary and can be removed from NGCP.
Change-Id: I14c30f8bb45d6969be417fb44aed3680dd004318
We don't necessarily have the non-free section of Debian
repositories enabled everywhere (e.g. AWS EC2 builds, using
the official Debian AMIs). The firmware-bnx* packages,
which ngcp-hardware-support depends on, are available via
non-free only though.
Since we didn't ship those packages on CE systems in the
past, also don't depend on the new ngcp-hardware-support
package within ngcp-ngcp-ce.
Change-Id: I5f42b70dd5b38847f12101a9f2817910608c157d
We need script /usr/share/ngcp-deployment-scripts/includes/netcardconfig
from package ngcp-deployment-scripts on CE system to be able to use
modified netcardconfig during the network installation process.
Change-Id: Ic36b6591699d9a62f4528e6110daa264dd794654
'eject' is used into deployment.sh inside GRML and available there,
we do not use it into NGCP, no need to install it.
Change-Id: Iff49ab6e5054006b5d6e6e2ccca652cf28dcd8f0
The metapackages ngcp-services-* will have new dependecy on 'grub-pc'.
The metapackages ngcp-nth-* will have new dependecies on:
> eject, pciutils, usbutils
Change-Id: Ie8878e92455c12f04048dc63ee1f462ec4768680
PRO and Carrier depends on it since commit c27082ffb,
also deployment.sh installed it on CE in the past.
We need headers installed for proper dkms functionality
which is used by license client and rtpengine nowadays.
Change-Id: I0a2d9d0ced89782107254d721673ee215cb18729
(cherry picked from commit ea20bc6513f2c343ce8326ad1bc8be2da0ec1b75)
In the past those packages were installed on CE/PRO/Carrier by
deployment.sh on debootstrap process. Migrate them to metapackages
to ensure they are always available on NGCP.
P.S. Why do we need to install those firmwares:
> # required e.g. for "Broadcom NetXtreme II BCM5709S Gigabit Ethernet"
> # lacking the firmware will result in non-working network on
> # too many physical server systems, so just install it by default
Change-Id: I996e7745ad96c2742784dd633ffec919d647b320
In the past deployment.sh installed it during debootstrap.
We need to ensure it is installed on every NGCP system,
so adding it here.
Change-Id: Ic61a3d6af5f727ebf8f95c5fd5fb1d27c5951dca
In the past deployment.sh silently install the package on CE/PRO/Carrier
during Debian debootstrap stage and the package was missing on CE in
case of installation using plain debian+ngcp-installer.
ngcp-services-pro/carrier has dependency on ethtool already.
Change-Id: I8413e142159f0333178039f02d62213c8d07e90e
In the past the package was installed by deployment.sh on
CE/PRO/Carrier during debootstrap stage and was missing
in case of direct installation by ngcp-installer.
Move dependency here to support bridge / vlan on PRO/Carrier
systems installed without deployment.sh (like Amazon EC2 systems).
Change-Id: Ibe876159866735ffb4f58702b5f7da60a6e81fcc
The package lvm2 has been installed on Debian debootstrap stage,
so far NGCP had no direct dependency on it. Adding it here.
Change-Id: I99d1711fb46211f5765c048a132f416740051a1b
Since we started using systemd-coredump the core files are compressed with lz4.
So it's better to add liblz4-tool to the dependencies of meta-packages to have
"unlz4" available, to be able to uncompress and use the core files without
having to install the package manually.
Change-Id: I9167f1b664b84309015d5a63e1626b934d2881ba
We would have preferred a solution without depending on dbus, but
only with usage of dbus/libpam-systemd we can leverage full usage
of systemd, e.g.:
* usage of systemctl as user
* usage of systemd-run
* user sessions get moved into proper cgroups
* remote host usage (like `systemctl --host=sp2 status foo.service`)
* hanging ssh sessions (depending on systemd version in usage,
we ship a custom patch in our systemd backport for now which
tries to work around it)
* working shutdown (without requiring `-h now`, as it defaults
to '+1' by default, being a scheduled shutdown which works
only with dbus)
Change-Id: I06284a948fbcb428195929af9d626dc6f5e3345b
nano has better defaults for people not being used to it
than joe, whoever wants to switch the system editor can
run `sudo update-alternatives --config editor`.
Sorry, Victor :)
Change-Id: I8d203ac101ab3a7c5a8bf17848ece4aa9b854dcb
Noticed when running against recent versions of
Debian/stretch AMI on EC2 (e.g. ami-8a745cf3), failing with:
| The following packages have unmet dependencies:
|
| ngcp-services-ce : Depends: ntp but it is not going to be installed
Caused by:
| # sudo apt-get install ntp
| [...]
| The following packages will be REMOVED:
| chrony
| The following NEW packages will be installed:
| libopts25 ntp
Change-Id: I6216fe81f758eb536fe8a5e981c95a5f8f8ea7fe
The installer and other packages assumes a set of packages installed and others
removed.
Adding the relationships to the metapackages is a better/cleaner solution, and
in this way we can remove code from the installer.
Change-Id: I08f4e4a8a96f8ff4f4a3b7a6a68b7b078583e683
Use ngcp-ngcpcfg-ha package instead of ngcp-ngcpcfg-carrier as
a dependency of ngcp-config-carrier.
Our goal is to reduce the number of 'ngcp-*-carrier' packages as much
as possible so functionality of ngcp-ngcpcfg-carrier was added to
ngcp-ngcpcfg-ha and ngcp-ngcpcfg-carrier package isn't built anymore.
Change-Id: I45df7fd78490ae4176f3f09f282c85ec4146b0ac
- Bump debhelper compatibility version 10.
- Switch from Priority extra to optional.
- Update debian/.gitignore file.
Change-Id: I8a1b2f8a3c3f0a7638ce00a711d1d620286968b2
We are going to add new scripts into ngcp-upgrade-* packages to allow
the support team prepare upgrade better, like check list of supported release
and perform the pre-upgrade checks. It means the package must be installed out of the box.
Also good to ensure proper ngcp-installer-* is also installed as it is necessary for iPXE.
The package ngcp-installer was installed only because user/deployment.sh did it manually.
Maybe ngcp-nth-* is better place for such packages, but
we have to add them into ngcp-service-* as ngcp-nth-carrier doesn't
exist and list of added packages is different for PRO/Carrier.
+ wrap-and-sort -sat
Change-Id: I541a6f81e730327ef39913a00088eb052b5031ea
NGCP systems have Recommends disabled by default. So when we moved
this package from ngcp-panels Depends to Recommends, the system
stopped installing them when necessary, i.e. on PRO and CARRIER
where they are available and required.
Change-Id: I6828bb8af1900216cb20ccc6cd4967db208bf2c3
As discussed on the latest dev-meeting the current implementation
will NOT go into mr5.5 LTS and should NOT be installed since m5.5.
This reverts commit deb14b216d.
Change-Id: Iaa8fbb8feae0c6011a10c14a9098cfb2ed657d32
ngcp-panel-csc is new customer self-care extjs based interface,
which will be available nearby the current ngcp-panel csc interface
at least for the next LTS release and should replace it one day.
Change-Id: Ia01cf9cbedef20fd014e1c2f828260f0a46dbc0f
As a follow-up to Change-Id: I9829f5daa106f5c2288f48f8f45f10aceae5dddd
(commit 4899747a26) we still want to
have mytop on Debian/jessie systems, while mytop is provided
by mariadb-client-10.1 starting with Debian/stretch.
Change-Id: Ie5034007d591f7c6e5cafbfe843b238ed85fec33
mariadb-client-10.1 conflicts with the mytop package since
it ships the mytop binary as well.
Fixes:
| The following packages have unmet dependencies:
| ngcp-nth-ce : Depends: mytop but it is not going to be installed
| [...]
| The following packages have unmet dependencies:
| mariadb-client-10.1 : Conflicts: mytop but 1.9.1-4 is to be installed
This was introduced as of mariadb-10.1 v10.1.23-4, see
https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=861913
Change-Id: I9829f5daa106f5c2288f48f8f45f10aceae5dddd
man-db is no longer "Priority: important" on Debian/stretch,
therefore the man(1) tool is missing on stretch otherwise.
Change-Id: I880f4a545c7d6db1edf71dc123e3de0746f780e2
ifconfig is required for our heartbeat-2 package:
| Starting High-Availability services:
| /usr/lib/ocf/resource.d//heartbeat/IPaddr: 312: /usr/lib/ocf/resource.d//heartbeat/IPaddr: ifconfig: not found
The net-tools package became "Priority: optional"
with stretch, so it's no longer installed by default.
Change-Id: I451445897f8af66ace4b1bf24a93de1323909b4b
NGCP iptables templates need debian package "netfilter-persistent"
(formerly "iptables-persistent") installed.
Additionally package "iptables-persistent" has to be installed. This
package is now just providing iptables command line tools while the
service in init.d was moved to "netfilter-persistent". Package
"netfilter-persistent" alone will not load any rules, since it is
depending on the command line tools.
Removing package "netfilter-persistent" from dependency list. Package
"iptables-persistent" depends already on it.
Change-Id: I205a6d82f1f042d9cae2404893a45157a97b3471
The dependency on openjdk-7-jre-headless was needed for elasticsearch
(which depends on java stack but lacks an according dependency :-/).
So drop it, and if we should need it again then we should depend
on default-jre-headless instead.
Change-Id: I77cedf00b465795929c20d5fcae80a4901d0406b
telnet-ssl package doesn't exist in stretch,
see https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=828448
A better approach is to actually use something like
`openssl s_client -host ... -port 443`, socat or gnutls instead.
Change-Id: I7f9c9b9072d2fe2405462e92524cf63cfc5b4152
Guillem Jover
Michael Prokop
Richard Fuchs
Alexander Lutay
Kirill Solomko
Manuel Montecelo
Mykola Malkov
Andreas Granig
Roman Romanchenko
Gernot Fuchs
Victor Seva