Bug 1428232 - [Docs] [Admin] Add a note that traffic shaping is now applied to the ovirtmgmt network by default
Summary: [Docs] [Admin] Add a note that traffic shaping is now applied to the ovirtmgm...
Status: CLOSED NEXTRELEASE
Alias: None
Product: Red Hat Enterprise Virtualization Manager
Classification: Red Hat
Component: Documentation (Show other bugs)
(Show other bugs)
Version: 4.1.0
Hardware: Unspecified Unspecified
medium
medium
Target Milestone: ovirt-4.1.1
: ---
Assignee: rhev-docs@redhat.com
QA Contact: rhev-docs@redhat.com
URL:
Whiteboard:
Keywords:
Depends On: 1255474
Blocks:
TreeView+ depends on / blocked
 
Reported: 2017-03-02 05:44 UTC by Andrew Dahms
Modified: 2017-03-02 14:20 UTC (History)
7 users (show)

Fixed In Version:
Doc Type: If docs needed, set a value
Doc Text:
Story Points: ---
Clone Of:
Environment:
Last Closed: 2017-03-02 14:20:51 UTC
Type: Bug
Regression: ---
Mount Type: ---
Documentation: ---
CRM:
Verified Versions:
Category: ---
oVirt Team: Docs
RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: ---


Attachments (Terms of Use)

Description Andrew Dahms 2017-03-02 05:44:18 UTC
In Red Hat Virtualization 4.1, traffic shaping is now applied to the ovirtmgmt network by default. When a new data center object is created, a default host QoS profile by the name of 'Default-Mgmt-Net-QoS' is applied.

A note should be added to the introduction to 'Host Network Quality of Service' in the Administration Guide that calls out this behaviour, that the ovirtmgmt network is the only one to which default QoS is applied, and that provides a short note on the context as to why this is helpful (i.e. prevents network overloading for this very important network).

Comment 1 Yaniv Lavi 2017-03-02 13:39:07 UTC
This feature was deferred to 4.2. Shall we move it to 4.2 or close?

Comment 2 Andrew Dahms 2017-03-02 14:20:51 UTC
Hi Yaniv,

Why don't we just close this one for now, then - the bug does not contain a great deal of information at this stage, and we can always create a new tracker when we are ready to look at this feature more actively.

Closing for now, but feel free to re-open it if you feel it is best kept open for now.

Kind regards,

Andrew


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