2020.08.04

Topics for further discussion

Packaging - 8/6

Omar - TopDown Micro Architecture - 8/6

Analyzing ldms data

Stream security

All LDMSD Streams data is conveyed over an LDMS Transport. LDMS Transports are authenticated in one of three ways: "none", "ovis", and "munge".

• "none" : No authentication is done. This should only be used when all users are trusted.
• "ovis" : Secret word authentication. The remote peer is known to know the secret word; effectively every user is trusted as root.
• "munge" : The uid/gid of the remote peer is trusted by virtue of being verified through a third party

The trust level of data published through the stream service is known, however, the subscribing client does not have direct access to this information. We should consider adding API/Event data updates to convey this information so that subscribers can make decisions about how and to what extent to trust this data.

Visualizing ldms data

NERSC -- LDMS - VictoriaMetrics integration.

Topics in discussion:

-- Big DB chat.

-- Handling multiple systems data, Kafka etc....

• Mark S: understanding and advertising the data sizes and the computation (from the set data size). Especially for multiple feeds going from the aggregators off to the monitoring cluster.
• Phil R: ....and measuring it live. (Ben's dstat sampler and then v4-5 tracking if ldmsd's aren't keeping up)
• Chris M: holding data at the aggregator because of connecting to Kafka etc.
• Melissa A and Chris: getting rid of Kafka.

-- Security within LDMS, steams

• carried in the meta data, but we are ignoring it at the store
• what would have to change (if anything) at intermediate LDMS for apps to get access to some data for response (security limitations)
• changing the rwx model to enable more fined grained access control
• if you don't have permissions, you can't get the handle to get the set. You also cannot push changes to that set. You can change your own local copy, of course, but then you would have to have been authenticated to be in the ldms ecosystem.
• TODO: big security review and understanding. will take it to GitHub issues.