Bug 1015417

http://www.ovirt.org/Features/Vnic_Profiles

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.

Changes:
* 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 
* REST API 
(https://<domain.example.com>/api/networks/<id>/vnicprofiles)
* CLI (show vnicprofile --name <name>

Related to: Network QoS
https://bugzilla.redhat.com/show_bug.cgi?id=976160

"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
https://bugzilla.redhat.com/show_bug.cgi?id=976570
"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."