...
- Update from collectd bi-weekly
- python-plugins update
- repo created; questions regarding licence
- open for contribution
- some questions around licensing for go-collectd plugins
- List of work items to be created for go-collectd and published so community can contribute
- link: https://collectd.org/wiki/index.php/Minutes_from_2020-06-12
- python-plugins update
- CI updates
- test development
- infra tickets
- nightly builds
- Request for list of collectd metrics (Collectd docs)
- There is no list of metrics for plugins in general in collectd
- We have some lists in Barometer, but the list doesn't reflect the latest
- We should take a divide and conquer approach and split the tasks up.
- TODO(Emma): add a Jira item and add a bunch of sub-tasks.
- Define a master location: aim to write info in the wiki, and periodically sync to collectd source
- Proposal to do bug triage in the weekly call
- TODO(Emma): Add standing item to meetings
June 09th, 2020, 4pm UTC
- Collectd bi-weekly meeting this week
- Topics for discussion: collectd-python repo, and questions regarding downstreaming of those plugins
- Updates from Closed Loop automation group
- highlighted discussions on Zabbix and prom for closed loop, with focus on observability as opposed to automated remediation
- Feedback welcome on direction, e.g. focus on analytics, etc
- POD13 assignments
- Node 3&4 for a demo
- Node 5 will be Jenkins slave
- CI updates
...