Add basic monitoring tools to the base image

[rtsisyk]

It would be nice to have some extra command-line monitoring tools in the base image.
My favourite list is:

rpm-ostree install \
    strace \
    nc \
    telnet \
    tcpdump \
    atop \
    iotop \
    ioping \
    iftop \
    htop \
    iperf \
    sysstat \
    dmidecode \
    smartmontools \
    numactl \
    lshw \
    pciutils \
    ipmitool \
    vim-enhanced

Some items can be controversial, but let's agree on some necessary minimum. Yes, I understand that it is possible to run a privileged container with required tools, but these tools are really necessary on the host system for troubleshooting, especially on the bare metal. AFAIK, all these packages consume less than 50Mb of space.

[dustymabe]

Thanks @rtsisyk. I added the meeting label so we'll discuss it in the next meeting (next Wednesday).

[jlebon]

Oh those, I think strace is a big one which could be worth shipping by default. It's easy to run in a --pid=host container, though it can help break the "debug bootstrapping problem". For comparison, note RHCOS does ship strace.

[rtsisyk]

I see that htop requires python, which should not be included.

Without htop:

Transaction Summary
=========================================================================================================================
Install  51 Packages

Total download size: 23 M
Installed size: 83 M

Without vim-enhanced:

Install  46 Packages

Total download size: 14 M
Installed size: 50 M

[travier]

To prepare for the meeting, I would recommend that you give at least one use case per tool that would benefit with the tool being installed on the host rather than used from a container.

[dustymabe]

We discussed this in last week's meeting.

We started to discuss each tool individually, but then took a step back and decided to define a set of questions to answer when we propose adding new packages to the base layer.

* ACTION: we'll file a tracker ticket to come up with rough criteria
    for adding packages  (dustymabe, 17:28:12)

The tracker ticket was created by micah at: #641

[dustymabe]

hey @rtsisyk do you mind creating a new ticket for each item you'd like to include in the host? We have a new issue template that you can select for proposing a new package for inclusion. The issue template has a lot of questions. Some will be relevant, some might not be. Either way, more information helps us make a decision about the qualifications of each package. Recently we went through this exercise with kexec-tools.

[travier]

As mentioned above, each tool would have to be considered independently to assess its usefulness and use cases for inclusion. This will be better done via independent issues for each tool so I'll close this issue.