Back to bug 1044033
| Who | When | What | Removed | Added |
|---|---|---|---|---|
| Nir Yechiel | 2013-12-17 18:34:21 UTC | CC | nyechiel | |
| Summary | Support ethtool_opts functionality within RHEV | [RFE] Support ethtool_opts functionality within RHEV | ||
| Whiteboard | network | |||
| RHEL Program Management | 2014-01-09 13:51:37 UTC | Target Release | --- | 3.5.0 |
| RHEL Program Management | 2014-01-09 14:24:47 UTC | Target Release | 3.5.0 | --- |
| Meni Yakove | 2014-01-28 08:35:44 UTC | CC | myakove | |
| Dan Kenigsberg | 2014-01-30 10:56:29 UTC | Blocks | 1059680 | |
| John Skeoch | 2014-03-17 02:03:13 UTC | CC | abaron | |
| Dan Kenigsberg | 2014-03-26 12:44:27 UTC | Blocks | 1080987 | |
| Nir Yechiel | 2014-04-03 12:59:40 UTC | Target Release | --- | 3.5.0 |
| QA Contact | srevivo | myakove | ||
| Nir Yechiel | 2014-04-07 07:21:55 UTC | URL | http://www.ovirt.org/Features/Network_Custom_Properties | |
| Nir Yechiel | 2014-04-29 09:56:20 UTC | URL | http://www.ovirt.org/Features/Network_Custom_Properties | http://www.ovirt.org/Features/Ethtool_options |
| lpeer | 2014-04-29 12:16:32 UTC | Status | NEW | ASSIGNED |
| CC | gklein, Rhev-m-bugs | |||
| Component | RFEs | ovirt-engine-backend | ||
| Assignee | acathrow | nobody | ||
| lpeer | 2014-04-29 17:48:53 UTC | Assignee | nobody | lvernia |
| Lior Vernia | 2014-05-22 08:58:14 UTC | Status | ASSIGNED | MODIFIED |
| Itamar Heim | 2014-06-12 17:29:50 UTC | Summary | [RFE] Support ethtool_opts functionality within RHEV | PRD35 - [RFE] Support ethtool_opts functionality within RHEV |
| Nir Yechiel | 2014-07-07 08:59:36 UTC | CC | lvernia | |
| Flags | needinfo?(lvernia) | |||
| Dave Sullivan | 2014-07-07 21:30:48 UTC | Group | cme | |
| Red Hat Bugzilla | 2014-07-07 21:30:48 UTC | Group | devel, qa | |
| Lior Vernia | 2014-07-13 12:54:36 UTC | Doc Text | 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. 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). | |
| Flags | needinfo?(lvernia) | |||
| Nir Yechiel | 2014-07-16 14:13:43 UTC | Flags | needinfo?(myakove) | |
| GenadiC | 2014-07-24 14:01:53 UTC | CC | gcheresh | |
| Flags | needinfo?(myakove) | |||
| Nir Yechiel | 2014-07-24 14:30:14 UTC | Flags | needinfo?(lvernia) | |
| Sandro Bonazzola | 2014-07-25 08:36:19 UTC | CC | sbonazzo | |
| Flags | needinfo?(lvernia) | |||
| Lior Vernia | 2014-07-27 07:42:00 UTC | Status | MODIFIED | ON_QA |
| Doc Text | 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. 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). | 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). | ||
| Flags | needinfo?(lvernia) needinfo?(lvernia) | |||
| Ofer Blaut | 2014-07-28 07:38:07 UTC | CC | oblaut | |
| Meni Yakove | 2014-07-29 09:44:33 UTC | QA Contact | myakove | gcheresh |
| GenadiC | 2014-07-29 09:56:20 UTC | Status | ON_QA | VERIFIED |
| John Skeoch | 2014-09-07 23:16:24 UTC | CC | acathrow | rbalakri |
| Joe Donohue | 2014-09-18 12:42:39 UTC | Blocks | 1142923 | |
| Julie | 2014-10-07 07:22:42 UTC | Blocks | 1123924 | |
| Joe Donohue | 2014-10-23 17:36:46 UTC | Blocks | 1156162 | |
| Joe Donohue | 2014-10-23 17:39:55 UTC | Blocks | 1156165 | |
| Joe Donohue | 2014-10-23 17:42:09 UTC | Blocks | 1156162 | |
| Julie | 2014-12-02 06:08:41 UTC | CC | juwu | |
| Doc Text | 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). | With this feature, you can now configure ethtool options from from Red Hat Enterprise Virtualization Manager. Previously, the Manager only configures a small subset of the values of a network interface. Users now have the option to use the ethtool utility to customize their usage of network interface. Ethtool options can 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. The engine-config tool 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' The hook corresponding to the pre-defined custom property - vdsm-hook-ethtool-options - should be installed on the relevant hosts (via yum). These custom properties are accessible through the Administration Portal, REST API, and software development kits. |
||
| Julie | 2014-12-04 00:08:46 UTC | Doc Text | With this feature, you can now configure ethtool options from from Red Hat Enterprise Virtualization Manager. Previously, the Manager only configures a small subset of the values of a network interface. Users now have the option to use the ethtool utility to customize their usage of network interface. Ethtool options can 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. The engine-config tool 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' The hook corresponding to the pre-defined custom property - vdsm-hook-ethtool-options - should be installed on the relevant hosts (via yum). These custom properties are accessible through the Administration Portal, REST API, and software development kits. | With this feature, you can now configure ethtool options from from Red Hat Enterprise Virtualization Manager. Previously, the Manager only configures a small subset of the values of a network interface. Users now have the option to use the ethtool utility to customize their usage of network interface. The engine-config tool has to be used initially for the "ethtool_opts" key to be made available. These custom properties are accessible through the Administration Portal, REST API, and software development kits. |
| Yaniv Lavi | 2014-12-08 15:24:58 UTC | Group | qa, devel | redhat |
| Marina Kalinin | 2014-12-30 20:18:05 UTC | CC | mkalinin | |
| Dan Kenigsberg | 2015-01-19 14:19:50 UTC | Depends On | 1183626 | |
| Yaniv Lavi | 2015-01-19 17:04:33 UTC | Group | redhat | |
| CC | dsulliva, ydary | |||
| Flags | needinfo?(dsulliva) | |||
| Red Hat Bugzilla | 2015-01-19 17:04:33 UTC | Group | devel, qa | |
| Itamar Heim | 2015-01-22 08:38:46 UTC | Group | qa, cme, devel | |
| Andrew Dahms | 2015-02-10 12:15:46 UTC | CC | adahms | |
| Doc Text | With this feature, you can now configure ethtool options from from Red Hat Enterprise Virtualization Manager. Previously, the Manager only configures a small subset of the values of a network interface. Users now have the option to use the ethtool utility to customize their usage of network interface. The engine-config tool has to be used initially for the "ethtool_opts" key to be made available. These custom properties are accessible through the Administration Portal, REST API, and software development kits. | With this feature, you can now configure ethtool options from Red Hat Enterprise Virtualization Manager. Previously, the Manager only configures a small subset of the values of a network interface. Users now have the option to use the ethtool utility to customize their usage of network interface. The engine-config tool has to be used initially for the "ethtool_opts" key to be made available. These custom properties are accessible through the Administration Portal, REST API, and software development kits. | ||
| errata-xmlrpc | 2015-02-11 15:36:02 UTC | Status | VERIFIED | RELEASE_PENDING |
| errata-xmlrpc | 2015-02-11 17:56:57 UTC | Status | RELEASE_PENDING | CLOSED |
| Resolution | --- | ERRATA | ||
| Last Closed | 2015-02-11 12:56:57 UTC | |||
| John Skeoch | 2015-05-05 01:44:19 UTC | CC | bazulay | |
| Lucy Bopf | 2016-01-28 03:48:52 UTC | Blocks | 1250877 | |
| Yaniv Lavi | 2016-02-10 19:57:51 UTC | oVirt Team | --- | Network |
Back to bug 1044033