Bug 1466465
Summary: | [RFE] Management UI can tell the user which CPU models are usable | ||
---|---|---|---|
Product: | [oVirt] ovirt-engine | Reporter: | Eduardo Habkost <ehabkost> |
Component: | Frontend.Core | Assignee: | bugs <bugs> |
Status: | CLOSED DEFERRED | QA Contact: | Lukas Svaty <lsvaty> |
Severity: | medium | Docs Contact: | |
Priority: | unspecified | ||
Version: | future | CC: | bugs, ehabkost, tjelinek |
Target Milestone: | --- | Keywords: | FutureFeature |
Target Release: | --- | Flags: | tjelinek:
ovirt-future?
rule-engine: planning_ack? rule-engine: devel_ack? rule-engine: testing_ack? |
Hardware: | Unspecified | ||
OS: | Unspecified | ||
Whiteboard: | |||
Fixed In Version: | Doc Type: | If docs needed, set a value | |
Doc Text: | Story Points: | --- | |
Clone Of: | Environment: | ||
Last Closed: | 2020-04-01 14:47:29 UTC | Type: | Bug |
Regression: | --- | Mount Type: | --- |
Documentation: | --- | CRM: | |
Verified Versions: | Category: | --- | |
oVirt Team: | Virt | RHEL 7.3 requirements from Atomic Host: | |
Cloudforms Team: | --- | Target Upstream Version: | |
Embargoed: |
Description
Eduardo Habkost
2017-06-29 17:33:30 UTC
Im not really sure what flow you refer to. - When you create a new cluster you have to provide a CPU while there are no hosts in it yet so the user can not be warned. - When you add the first host to the default cluster the CPU is autodetected from this host. - The only case I can think of is to edit the cluster? Or are you referring to some other flow? I opened this BZ just to to make sure the oVirt team is aware of the new mechanisms, but I don't know the details of all flows in oVirt, so I can't answer which ones could benefit from it, exactly. I can think of two possible cases, but I didn't test them with a more recent libvirt version: 1) The user is going to pick a CPU model, the system already knows which hosts are part of the cluster, and the CPU model is unusable on some (or all) of those hosts. 2) The user is going to add a host to a cluster, the CPU model was already configured for the cluster, and the host can't run that CPU model. I see. So the place for oVirt to use it is when configuring the custom CPU type of the VM to make sure the VM will be runnable somewhere on the cluster. Turning this to an RFE. This bug didn't get any attention for a while, we didn't have the capacity to make any progress. If you deeply care about it or want to work on it please assign/target accordingly This bug didn't get any attention for a while, we didn't have the capacity to make any progress. If you deeply care about it or want to work on it please assign/target accordingly ok, closing. Please reopen if still relevant/you want to work on it. ok, closing. Please reopen if still relevant/you want to work on it. |