The idea behind this is that some of the hard-coded and _usually_ widely known information could be put into data. And libosinfo is a perfect place for this because all the metadata and pairing algorithms already exist there. This example shows multiple different ideas in parallel, so I would like to ask you to comment on each part individually rather than the files as a whole. Of course feel free to comment on the general idea as well. Also these are just ideas, not necessarily "this is the only way this can be done" thing. I'd appreciate any input on any part of this. I figured the workloads could actually be referenced from the deployments as well, that is if I understand deployments correctly. Martin Kletzander (3): workload: Add high performance workload: Example of restricted high-perf workload: Example for particular use case - SAP HANA data/workload/example.com/high-perf.xml.in | 38 ++++++++++++++++++ data/workload/example.com/sap-hana.xml.in | 29 ++++++++++++++ .../example.com/super-high-perf.xml.in | 39 +++++++++++++++++++ 3 files changed, 106 insertions(+) create mode 100644 data/workload/example.com/high-perf.xml.in create mode 100644 data/workload/example.com/sap-hana.xml.in create mode 100644 data/workload/example.com/super-high-perf.xml.in -- 2.19.1 _______________________________________________ Libosinfo mailing list Libosinfo@xxxxxxxxxx https://www.redhat.com/mailman/listinfo/libosinfo
