This should be the final major revision for this. After more discussion
with Aline, it seems we've moved very far from "no input from users" to
"let users input the numbers, with some small restrctions."
Aline said she would talk with the UI team, but I'll still put a small
description here:
1. UI adds a new section on the template panel near vcpus. There's a
checkbox with the text, "Manually configure guest CPU topology." If
the users checks it
- The UI calls GET /host/cpuinfo
- The CPUs field becomes inactive, and will now be populated by
the UI based on the sockets & cores (next item):
CPUS = cores * threads
- Two fields appear: A selection field for threads (powers of 2
: 0...log(threads_per_core, 2)). This section should be
called either SMT (Power), or Threads (x86). The 2nd field is
a plain text box titled Cores that takes any integer.
Note: no 'automatic' option for threads/SMT.
- The UI calls POST template with the topology.
2. If the user doesn't check the checkbox, there's nothing new
to pass in for the template create.
Note: Currently there is a failing test in mockmodel, due to the nature
of the libvirt test driver. I'm looking into a workaround for the
getCapabilities function.
Christy Perez (1):
Parts to allow Kimchi to configure the cpu topology.
docs/API.md | 24 ++++++++
src/kimchi/control/cpuinfo.py | 37 ++++++++++++
src/kimchi/control/host.py | 2 +
src/kimchi/i18n.py | 5 ++
src/kimchi/model/cpuinfo.py | 128 ++++++++++++++++++++++++++++++++++++++++++
src/kimchi/model/templates.py | 10 ++--
6 files changed, 202 insertions(+), 4 deletions(-)
create mode 100644 src/kimchi/control/cpuinfo.py
create mode 100644 src/kimchi/model/cpuinfo.py
--
1.9.3