Bug 1314290 - [RFE] mark default CPU profile with a flag
Summary: [RFE] mark default CPU profile with a flag
Keywords:
Status: CLOSED NOTABUG
Alias: None
Product: ovirt-engine
Classification: oVirt
Component: RFEs
Version: 3.6.3.3
Hardware: Unspecified
OS: Unspecified
unspecified
medium
Target Milestone: ---
: ---
Assignee: Rob Young
QA Contact: Gil Klein
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2016-03-03 10:33 UTC by Shira Maximov
Modified: 2018-07-04 14:57 UTC (History)
3 users (show)

Fixed In Version:
Clone Of:
Environment:
Last Closed: 2018-07-04 14:57:52 UTC
oVirt Team: SLA
Embargoed:
dfediuck: ovirt-future?
mshira: planning_ack?
mshira: devel_ack?
mshira: testing_ack?


Attachments (Terms of Use)
CPU profile print screen (197.58 KB, image/png)
2016-03-03 10:33 UTC, Shira Maximov
no flags Details

Description Shira Maximov 2016-03-03 10:33:58 UTC
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:

Comment 1 Andrej Krejcir 2018-07-04 14:57:52 UTC
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.


Note You need to log in before you can comment on or make changes to this bug.