Bug 1123924

Feature: 

Ability to configure ethtool options from within RHEV-M.

Reason: 

RHEV-M by default only configures a small subset of the configurable values of a network interface.

However, some users would like to use the ethtool utility to customize their usage of network interface, e.g. to prevent a faulty interface driver from performing hardware offloading.

Result: 

Any ethtool options can now be supplied when provisioning a network on a host via a "custom properties" mechanism, similar to others in RHEV-M, using the key "ethtool_opts" of a network that is to reside on the physical interface.

Note that the engine-config has to be used initially for the "ethtool_opts" key to be made available. If no validation of the supplied ethtool arguments is required, the following command will achieve this:

engine-config -s 'UserDefinedNetworkCustomProperties=ethtool_opts=.*' --cver='3.5'

Moreover, the hook corresponding to this pre-defined custom property - vdsm-hook-ethtool-options - should be installed on the relevant hosts (via yum).

These properties are accessible both via the Setup Host Networks dialog in the webadmin console (when configuring a specific network), and via the Setup Networks action in the RESTful API (and derived SDKs).

Install/ Admin Guide shared topic:
https://access.redhat.com/documentation/en-US/Red_Hat_Enterprise_Virtualization/3.4/html-single/Installation_Guide/index.html#Editing_host_network_interfaces
Technical Guide may require new topic.

PRD: https://bugzilla.redhat.com/show_bug.cgi?id=1044033

Additional Info: http://www.ovirt.org/Features/Network_Custom_Properties#Ethtool_options

SME Contact: Lior (lvernia)