Bug 1028515 - Change label for Network profiles to be more specific to VMs
Summary: Change label for Network profiles to be more specific to VMs
Keywords:
Status: CLOSED CURRENTRELEASE
Alias: None
Product: oVirt
Classification: Retired
Component: ovirt-engine-webadmin
Version: 3.3
Hardware: Unspecified
OS: Unspecified
low
low
Target Milestone: ---
: 3.4.0
Assignee: Lior Vernia
QA Contact: bugs@ovirt.org
URL:
Whiteboard: network
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2013-11-08 16:00 UTC by mrao
Modified: 2015-05-05 01:44 UTC (History)
9 users (show)

Fixed In Version: ovirt-3.4.0-beta2
Doc Type: Bug Fix
Doc Text:
Clone Of:
Environment:
Last Closed: 2014-03-31 12:32:24 UTC
oVirt Team: ---

Attachments (Terms of Use)
Add an attachment (proposed patch, testcase, etc.)


Links
System ID Private Priority Status Summary Last Updated
oVirt gerrit 23485 0 None None None Never

Description mrao 2013-11-08 16:00:59 UTC 
Description of problem: Profiles for networks apply only in the context of QoS for VMs and not hosts ( which will be introduced soon). To eliminate any confusion, please change this subtab label to 'vNic Profiles'. ( Networks main tab >Profiles sub tab)

To be consistent, this label needs to be changed here as well - Networks main tab > Logical Network sub tab> Edit logical network dialog> Profiles left tab.- Rename this Profiles left tab to Vnic Profiles as well.


Version-Release number of selected component (if applicable):


How reproducible:


Steps to Reproduce:
1.
2.
3.

Actual results:


Expected results:


Additional info:
Comment 1 Itamar Heim 2014-01-12 08:43:05 UTC 
setting target release to current version for consideration and review. please do not push non-RFE bugs to an undefined target release to make sure bugs are reviewed for relevancy, fix, closure, etc.
Comment 2 Meni Yakove 2014-02-17 07:19:52 UTC 
ovirt-engine-3.4.0-0.7.beta2.el6.noarch
Comment 3 Sandro Bonazzola 2014-03-31 12:32:24 UTC 
this is an automated message: moving to Closed CURRENT RELEASE since oVirt 3.4.0 has been released
Note You need to log in before you can comment on or make changes to this bug.