This patchset is not completely tested, but I'd like feedback on broad concepts, and also to share my methodology with the UI team. If you read the comments (which I'lld delete in the final version), there are some suggestions for how I intend this to interoperate with the UI. In the future, I'd also like to combine the rest of the CPU info scattered across at least the host class and use this new CPUInfoModel instead. But for now, I'd like to focus on getting the backend logic working so that the user can create a template that has an auto-created topology. Christy Perez (1): Parts to allow Kimchi to configure the cpu topology. docs/API.md | 2 + src/kimchi/API.json | 6 ++ src/kimchi/control/cpuinfo.py | 37 +++++++++ src/kimchi/i18n.py | 2 + src/kimchi/model/cpuinfo.py | 176 ++++++++++++++++++++++++++++++++++++++++++ src/kimchi/model/host.py | 1 + src/kimchi/model/templates.py | 13 +++- 7 files changed, 236 insertions(+), 1 deletion(-) create mode 100644 src/kimchi/control/cpuinfo.py create mode 100644 src/kimchi/model/cpuinfo.py -- 1.9.3