[collectd] SNMPv3+DTLS support for collectd-snmp
mrunge at matthias-runge.de
Tue May 4 18:53:39 CEST 2021
On Tue, May 04, 2021 at 10:52:31AM +0200, Graham Leggett wrote:
> On 19 Mar 2021, at 15:33, Matthias Runge <mrunge at matthias-runge.de> wrote:
> >> On 12 Jan 2021, at 16:27, Graham Leggett <minfrin at sharp.fm> wrote:
> >>> As part of that work I have added the required support to collectd-snmp to support DTLS/TLS with SNMP. This involved teaching collectd how to pass the correct additional parameters.
> >>> Two PRs have been submitted:
> >>> https://github.com/collectd/collectd/pull/3803 - support DTLS parameters.
> >>> https://github.com/collectd/collectd/pull/3805 - support for SHA224/SHA256/SHA384/SHA512
> >> Another quick ping on this one, is someone able to take a look?
> >> Currently CI failures are due to EL6 support no longer being functional as I understand.
> > Unfortunately, that's not entirely true. There are two issues with CI currently: one because of CentOS 6 not being functional, the other one, because CI still relies on travis, and you apparently need admin access to remove travis, or to replace travis with something else.
> Another gentle ping on this one - the lack of standards compliant monitoring is really hurting us, people keep suggesting to us “install proprietary monitoring, it will all be fine *cough* solarwinds *cough*” and we’d like to avoid this.
> Is there a way I can help to move things forward?
I'm sorry about the delay.
Unfortunately, my hands are tied and I can not fix upstream CI as
I don't have access to the project settings to e.g disable travis,
which prevents us from merging anything.
This topic came up in the recent OpenStack project team gathering
and we decided to fork the project to be able to run a CI env.
You'll see, pull requests are disabled. While this is not intended
to replace collectd upstream, it can be used to pull in newer patches
like the ones linked.
However, my time is very limited these days, and I didn't get to any
more work there. I have asked a colleague to look at the CI in the fork
to get it going there. I would try to get CI in place first and then
pull in patches proposed to upstream into the fork.
If you want to help: I'd need a second pair of eyes to get
the github actions work properly.
Matthias Runge <mrunge at matthias-runge.de>
More information about the collectd