Bug 1016954 - [Admin] [Docs] VNIC Profiles
[Admin] [Docs] VNIC Profiles
Product: Red Hat Enterprise Virtualization Manager
Classification: Red Hat
Component: Documentation (Show other bugs)
Unspecified Unspecified
unspecified Severity unspecified
: ---
: ---
Assigned To: Andrew Burden
Depends On: 1015417
  Show dependency treegraph
Reported: 2013-10-08 23:28 EDT by Andrew Burden
Modified: 2014-04-06 23:09 EDT (History)
4 users (show)

See Also:
Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of: 1015417
Last Closed:
Type: Bug
Regression: ---
Mount Type: ---
Documentation: ---
Verified Versions:
Category: ---
oVirt Team: ---
RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: ---

Attachments (Terms of Use)

  None (edit)
Description Andrew Burden 2013-10-08 23:28:34 EDT
+++ This bug was initially created as a clone of Bug #1015417 +++


In short: Network Admin can create VNIC profiles for each network. Users are granted permission to use a profile, limiting their bandwith on the network.

* GUI - new tab in Details pane for 'Network' resource
      - new window (VM Interface Profile)
      - new 'Profiles' tab in New/Edit Logical Network window
* New permissions - groups and users 
* CLI (show vnicprofile --name <name>

Related to: Network QoS

"In order to define more natural coupling of the QoS to a VNIC we define a new concept called VNIC Profile. The VNIC profile will be introduced in oVirt 3.3 to all clusters and will wrap few of the properties currently defined directly on the VNIC" (from ovirt wiki: Network QoS)",

and (it appears)

custom properties per vnic
"Previously you could only set custom properties for VMs, now you can custom properties for virtual NICs. These custom properties are then sent for each operation related to vNICs: hotplug nic, hot unplug nic, update device, VM creation (Via before_device_create, after_device_create), VM destroy (before_device_destroy, after_device_destroy) and migration verbs (The full list is below).

For example, previously if you wanted to do some operation on a VM's vNICs you could pass a custom property to the VM and before_vm_start would have the custom property exposed. However, you had no way to get down to a specific vNIC, you could only target all of them. Now you can add a custom property to a specific vNIC (Via the new vNIC profiles feature) and the custom property would only be sent to vNICs under that profile.
Section "B.8. Setting Virtual Machine Custom Properties" needs to be updated with instructions regarding vNIC profiles and vNIC custom properties."
Comment 1 Andrew Burden 2013-10-09 19:43:41 EDT
Topic created:
Network VNIC Profile Sub-Collection [23742]
Comment 2 Andrew Burden 2013-10-09 21:13:52 EDT
Sorry, wrong bug: That was for Dev Guide (must be time for tea).

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