2022-08-17 17:34 (UTC+0200), Morten Brørup: > > From: Dmitry Kozlyuk [mailto:dmitry.kozl...@gmail.com] > > Sent: Wednesday, 17 August 2022 17.15 > > > > 2022-08-16 19:08 (UTC-0700), Stephen Hemminger: > > > Not sure if turning telemetry into a do all control api makes sense. > > > > I'm sure it doesn't, for "do all". > > Controlling diagnostic collection and output, however, > > is directly related to the telemetry purpose. > > > > > This seems like a different API. > > I agree with Stephen regarding not making the telemetry library a "do all" > control API. A separate API would be preferable. > > And then, a wrapper through the telemetry interface can be provided to that > API. Best of both worlds. :-)
One of the reasons why I considered and suggested using the telemetry socket was that a new channel, protocol, and API would be an overkill for the task. It reminds me of an older "IF proxy library" proposal [1]. In the RFC discussion it was suggested that it could be a generic mechanism to deliver external events to DPDK, although, unlike events, commands need responses. I also found Thomas' message [2] that suggested log/trace control (never knew it was proposed already) but discouraged adding more interfaces. The final version of "IF proxy library" was nevertheless focused on netdev specifics and AFAICT never accepted because of questions from that side. So this RFC should be severely re-framed: 1) a generic event/command delivery mechanism is needed in principle, and 2) log/trace control can be the first usage of it, which may be easier to pull through than a complex interaction with OS networking stack. [1]: https://inbox.dpdk.org/dev/20200114142517.29522-1-aostrus...@marvell.com/ [2]: https://inbox.dpdk.org/dev/1734533.zqhfolzEdB@thomas/ > > > > Also, the default would have to be disabled for application safety > > reasons. > > > > This feature would be for collecting additional info > > in case the collection was not planned and a restart is not desired. > > If it is disabled by default, it is likely to be off when it's needed. > > All tracing, logging etc. MUST be disabled by default. You are suggesting the > opposite, which will definitely impact performance. > > And performance will become a valid argument for not adding more > trace/logging to libraries, if all of it is enabled by default. > > And my usual rant: I hope all of this can be disabled at build time - for > maximum performance. The feature is a dynamic equivalent of existing --log-level/--trace options. It doesn't affect performance until used to configure logs/traces that do. Other arguments to have it off by default are valid; just to clarify. > > > > > Let's consider how exactly can safety be compromised. > > > > 1. Securing telemetry socket access is out of scope for DPDK, > > that is, any successful access is considered trusted. > > > > 2. Even read-only telemetry still comes at cost, for example, > > memory telemetry takes a global lock that blocks all allocations, > > so affecting the app performance is already possible. > > > > 3. Important logs and traces enabled at startup may be disabled > > dynamically. > > If it's an issue, the API can refuse to disable them. > > > > 4. Bogus logs may flood the output and slow down the app. > > Bogus traces can exhaust disk space. > > Logs should be monitored automatically, so flooding is just an > > annoyance. > > Disk space can have a quota. > > Since the user is trusted (item 1), even if they do it by mistake, > > they can quickly correct themselves using the same API. > > > > Here's a thought: > > Add an API to set an "unlock key", so applications who don't want to allow > these features for unauthorized users can prevent them from enabling it. > Authorized users can use an API to unlock these features by providing the key. Let's keep delegating AAA to an external proxy if needed. Unlock key would not remove Stephen's concerns, because it would still be another interface to analyze and to protect. Worse, it's a home-grown security mechanism to consider.
