Atlassian uses cookies to improve your browsing experience, perform analytics and research, and conduct advertising. Accept all cookies to indicate that you agree to our use of cookies on your device. Atlassian cookies and tracking notice, (opens new window)
Maybe it is easier to just add the flow configuration that will automatically be part of the rpm and deb packages. When building the minion image that file would be excluded.
Benjamin Reed June 30, 2021 at 2:25 PM
I would say just put the "recommended" config in opennms-assemblies/minion/src/main/filtered/etc/ but add .example to the end of the filenames. Then we can make the Debian and RPM packages just rename those files from .example in their setup.
Chandra Gorantla June 23, 2021 at 1:57 PM
@Stefan Wachter
Note that we use etc/telemetryd-configuration.xml only on OpenNMS. This problem is relevant only on Minion since we use .cfg files to configure listeners only on Minion.
Goal for confd is to emit config that is compatible with whenever user is going to change. Currently, it installs configuration through features. It works as long as user doesn't attempt to change anything at runtime. May be users doesn't usually change configuration at runtime for containers.
Updating flow listener configurations just on RPM distribution is not a bad idea. Let's check with @Benjamin Reed.
Stefan Wachter June 23, 2021 at 6:25 AM
I wonder if the RPM distribution of Minion could simply contain default flow listener configurations (in form of files etc/org.opennms.features.telemetry.listeners-*.cfg) whereas in the Minion image no such files are included.
Telemetryd config on minion is usually placed in
org.opennms.features.telemetry.listeners.*.cfginetcfolder.Any updates through karaf shell gets updated in the config as well.
Confd takes a different route and configures telemetryd config through karaf features deployed in
deployfolder.Ideally it would be good just to replace the existing config in etc folder.