Closed dustinblack closed 2 years ago
I will be working on this issue as per the conversation with Dustin. Kindly assign this issue to me.
This week we discussed minimizing the MVP to simply to an ansible facts gathering and output it in whole as a dict.
We have this with the pbench-agent tool meister sub-system collecting the system information. Integration with that sub-system would bring that capability along with it.
@portante correct me if I'm wrong, but wouldn't that take a little longer time? We want to hit our target of making a workable workflow in ~6 weeks.
What is the determining factor that makes it longer or shorter?
I assumed that pbench-agent would have a slightly harder time defining a schema as it is a more complex tool? Maybe I'm wrong about that.
It is probably worth the effort to find out.
Closing with https://github.com/arcalot/arcaflow-plugin-metadata as an initial solution, though we will likely revisit this in the future for more explicit needs.
Please describe what you would like to see in this project
This is inspired by and should be index-compatible with the cloud-bulldozer metadata-collector and stockpile tools.
Please describe your use case
SUT (system under test) metadata is collected with stockpile using ansible facts. Collected metadata is formatted to be indexed alongside benchmark data from other plugins.
Additional context
This plugin work will need to coordinate with #12 and #13 to handle the ES indexing and compatibility.