public inbox for development@lists.ipfire.org
 help / color / mirror / Atom feed
From: Adolf Belka <adolf.belka@ipfire.org>
To: development@lists.ipfire.org
Subject: Re: [PATCH 0/2] Added new Package node_exporter
Date: Thu, 06 May 2021 22:43:53 +0200	[thread overview]
Message-ID: <c874d8db-f07a-5acf-77db-6ba0e73d9e37@ipfire.org> (raw)
In-Reply-To: <20210506194616.2972714-1-holger.sunke@posteo.de>

[-- Attachment #1: Type: text/plain, Size: 2640 bytes --]

Hi Holger,

Welcome to the development team and thanks for your patch submission.

I think that there is some additional information required in this covering note.

I think that it would be good to have some additional information about the use case for node_exporter compared to icinga, monit, zabbix_agentd, nagios, etc that already exist as addons in IPFire. What is it that node_exporter brings that cannot be accomplished by those other packages and warrants it being added to the list.

Historically many addons have been launched and then shortly afterwards the person who introduced the addon has stopped supporting the maintenance of it with updates, fixes etc. Typically then the package has ended up getting out of date.

I believe that the core devs will expect, if the addon is agreed to be a valuable additional package, a longer term commitment from yourself to take on the role of maintainer for the package. It would be good to have that commitment in this covering note.

Regards,

Adolf.

On 06/05/2021 21:46, Holger Sunke wrote:
> These patches add the new package node_exporter as discussed in the form thread:
> https://community.ipfire.org/t/please-add-prometheus-exporter/3555
>
> GO language is required to compile node_exporter. In order to compile
> node_exporter for i586 arch, "go" package supported architecture
> must be extended for this.
> You'll likely want to download packages and adjust DL_FROM variables
> in "go" and "node_exporter" LFS scripts.
>
> Holger Sunke (2):
>    Added i586/386 support for GO language required for node_exporter.
>    Added new node_exporter package.
>
>   config/rootfiles/packages/node_exporter       |  3 +
>   lfs/Config                                    |  4 +
>   lfs/go                                        |  6 +-
>   lfs/node_exporter                             | 88 +++++++++++++++++++
>   make.sh                                       |  1 +
>   src/paks/node_exporter/install.sh             | 31 +++++++
>   src/paks/node_exporter/uninstall.sh           | 30 +++++++
>   src/paks/node_exporter/update.sh              | 27 ++++++
>   ..._exporter-configurable-initd-options.patch | 48 ++++++++++
>   9 files changed, 235 insertions(+), 3 deletions(-)
>   create mode 100644 config/rootfiles/packages/node_exporter
>   create mode 100644 lfs/node_exporter
>   create mode 100644 src/paks/node_exporter/install.sh
>   create mode 100644 src/paks/node_exporter/uninstall.sh
>   create mode 100644 src/paks/node_exporter/update.sh
>   create mode 100644 src/patches/node_exporter-configurable-initd-options.patch
>

  parent reply	other threads:[~2021-05-06 20:43 UTC|newest]

Thread overview: 13+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-05-06 19:46 Holger Sunke
2021-05-06 19:46 ` [PATCH 1/2] Added i586/386 support for GO language required for node_exporter Holger Sunke
2021-05-06 20:26   ` Adolf Belka
2021-05-07 11:28   ` Michael Tremer
2021-05-07 18:19     ` Holger Sunke
2021-05-11  9:53       ` Michael Tremer
2021-05-21  8:56         ` Holger Sunke
2021-05-21  8:59           ` Michael Tremer
2021-05-06 19:46 ` [PATCH 2/2] Added new node_exporter package Holger Sunke
2021-05-06 20:58   ` Adolf Belka
2021-05-06 20:43 ` Adolf Belka [this message]
2021-05-07 18:05   ` [PATCH 0/2] Added new Package node_exporter Holger Sunke
2021-05-24 20:45     ` Robin Roevens

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=c874d8db-f07a-5acf-77db-6ba0e73d9e37@ipfire.org \
    --to=adolf.belka@ipfire.org \
    --cc=development@lists.ipfire.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox