Hello Matthew, > Why is the exporter module being enabled now?
We didn't need the exporter until now, but some metrics that we look into were recently moved into it (Ceph daemon perf counters, to be more specific), and so some alert rules weren't working any more. Thus the need to re-enable the ceph-exporter. > Does the exporter module get packaged, and where? Not to my knowledge. There was never a *.install file for it under `debian/`. AFAIK, it's an internal binary not meant to be directly called by users. > Does the exporter module work, and what is the testcase? It's meant to expose performance counters via the Prometheus endpoint. We have tested that this works via the PPA, yes. > Does any other ceph components use the vendored boost library? No, only the ceph-exporter. > Does the Security Team know we are using the vendored boost library instead of the distro packaged one? We haven't notified them of this. Since Ceph vendors in the same libraries that are shipped with our distros, we didn't think it was necessary. > Can the exporter module be patched to build with the distro packaged boost library instead? Not on Jammy. The exporter uses Boost.JSON, which wasn't available back then (Hence why it was disabled in the first place). > When it gets linked, it gets linked to system boost libraries: Right, the only vendored library that it's using is Boost.JSON, which is a header-only library, so no linking. The rest of the Boost stuff comes from the system. Let me know if you need anything else, Luciano. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/2100625 Title: [SRU] ceph 17.2.9 To manage notifications about this bug go to: https://bugs.launchpad.net/cloud-archive/+bug/2100625/+subscriptions -- ubuntu-bugs mailing list [email protected] https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
