| Summary: | [RFE] mark default CPU profile with a flag | ||||||
|---|---|---|---|---|---|---|---|
| Product: | [oVirt] ovirt-engine | Reporter: | Shira Maximov <mshira> | ||||
| Component: | RFEs | Assignee: | Rob Young <royoung> | ||||
| Status: | CLOSED NOTABUG | QA Contact: | Gil Klein <gklein> | ||||
| Severity: | medium | Docs Contact: | |||||
| Priority: | unspecified | ||||||
| Version: | 3.6.3.3 | CC: | akrejcir, bugs, dfediuck | ||||
| Target Milestone: | --- | Keywords: | FutureFeature | ||||
| Target Release: | --- | Flags: | dfediuck:
ovirt-future?
mshira: planning_ack? mshira: devel_ack? mshira: testing_ack? |
||||
| Hardware: | Unspecified | ||||||
| OS: | Unspecified | ||||||
| Whiteboard: | |||||||
| Fixed In Version: | Doc Type: | Enhancement | |||||
| Doc Text: | Story Points: | --- | |||||
| Clone Of: | Environment: | ||||||
| Last Closed: | 2018-07-04 14:57:52 UTC | Type: | Bug | ||||
| Regression: | --- | Mount Type: | --- | ||||
| Documentation: | --- | CRM: | |||||
| Verified Versions: | Category: | --- | |||||
| oVirt Team: | SLA | RHEL 7.3 requirements from Atomic Host: | |||||
| Cloudforms Team: | --- | Target Upstream Version: | |||||
| Attachments: |
|
||||||
There is no "default" CPU profile. When a new cluster is created, it creates its own CPU profile. This profile has the same name as the cluster, but it is not different from any other profile. It can be edited and removed. The same also applies to disk profiles. |
Created attachment 1132723 [details] CPU profile print screen Description of problem: The Default CPU profile called after the cluster usually, and this is inconvenient because you can't always tell which of the CPU profiles is the default one, from two reasons: 1. when changing the cluster name, the default CPU profile will still be called after the cluster first name. 2. It is possible to change the default name of the CPU Profile. my suggestion is to add a flag to the default CPU profile, and also to get the default CPU profile from REST API. Version-Release number of selected component (if applicable): Red Hat Enterprise Virtualization Manager Version: 3.6.3.2-0.1.el6 How reproducible: Steps to Reproduce: 1.add cluster called '1' 2.change the cluster name to something else 3.the CPU profile will be named '1' print screen attached. Actual results: Expected results: Additional info: