Bug 1314290 - [RFE] mark default CPU profile with a flag
[RFE] mark default CPU profile with a flag
Status: NEW
Product: ovirt-engine
Classification: oVirt
Component: RFEs (Show other bugs)
Unspecified Unspecified
unspecified Severity medium (vote)
: ---
: ---
Assigned To: Rob Young
Gil Klein
: FutureFeature
Depends On:
  Show dependency treegraph
Reported: 2016-03-03 05:33 EST by Shira Maximov
Modified: 2017-09-28 04:26 EDT (History)
2 users (show)

See Also:
Fixed In Version:
Doc Type: Enhancement
Doc Text:
Story Points: ---
Clone Of:
Last Closed:
Type: Bug
Regression: ---
Mount Type: ---
Documentation: ---
Verified Versions:
Category: ---
oVirt Team: SLA
RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: ---
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 05:33 EST, Shira Maximov
no flags Details

  None (edit)
Description Shira Maximov 2016-03-03 05:33:58 EST
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: 

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:

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