dustin/metricspi/pipeline/head This commit looks goodDetails
When I originally added the *victoriametrics* user to the `users` file,
I did not realize that it was possible for a package to define a user.
It makes much more sense to define it there.
There's no reason for these to be separate packages. They come from the
same source tree, so having a single package makes more sense. I only
separated them originally because I wasn't sure exactly how to express
the proper options in the kconfig language.
I think it makes the most sense to install the systemd unit files for
services along with their binaries. This is how most software provided
by Linux distribution package manager works. Providing the systemd unit
with the package eliminates the need for variability, since the paths to
the executable and other files are well defined.
In order to ensure that network interfaces are active, but not
necessarily fully configured, before *network.target* is reached, the
*dhcpcd.service* unit now waits until at least one interface has
processed the `CARRIER` event before being marked as active. This is
accomplished using the *sd_notify* infrastructure, via the
`systemd-notify` command, executed in a client configuration hook
script.
dustin/metricspi/pipeline/head This commit looks goodDetails
Now that *dhcpcd.service* and *dhcpcd-wait-online.service* correctly
activate *network.target* and *network-online.target*, respectively, the
hack to fix the *collectd* *wait_prometheus* plugin binding to the TCP
socket is no longer needed.
The *dhcpcd.service* systemd unit file that ships with Buildroot is
broken. It orders the unit after *network.target*, which makes no
sense. It also configures the process to fork, but incorrectly
configures the PID file. Finally, by relying on the fork to indicate
that the network is "online," it does not distinguish between "an
interface is up" and "the network is reachable." As most daemons only
need the former, they only rely on *network.target*, and thus can fail
to start correctly.
To correct this brokenness, we provide our own unit file for
*dhcpcd.service*, based on the one included in the Fedora *dhcpcd* RPM
package. For "online" signalling, we provide a pair of shell scripts:
one reads from a named pipe waiting for a message and the other sends a
message to the pipe when configuration is complete.
The *vmutils* package can be built from source easily, as its just a
collection of Go applications. Grafana and Alertmanager are quite a bit
more complicated because of their respective browser applications. In
the interest of getting this project actually going, we'll just install
the official binary releases of these (for now?).
Ansible's `user` module *requires* that the `usermod` command be
present, even if it would not actually create or modify the specified
user. It does not actually execute it unless it needs to, so we can
stub it out. Making it a symlink to `false` ensures that it will never
do anything, and will fail if its actually run.
dustin/metricspi/pipeline/head This commit looks goodDetails
Victoria Metrics is not available by default with Buildroot, but adding
a package description for it is very straightforward. The flags and
tags are specified within Victoria Metrics's own Makefile.
The *systemd* package provides the `systemd-hwdb` command, which is used
during the build to generate `/usr/lib/udev/hwdb.bin` in the target
filesystem.
dustin/metricspi/pipeline/head This commit looks goodDetails
Raspberry Pi firmware files are now included in the root of the
distribution archive, insteaad of in an `rpi-firmware` subdirectory.
This will make it easier to extract them to the FAT32 partition on the
SD card, along with the kernel and initramfs images files.
Dustin