Back to bug 1398925
| Who | When | What | Removed | Added |
|---|---|---|---|---|
| Francesco Giudici | 2016-12-14 17:22:56 UTC | Assignee | sukulkar | fgiudici |
| Aniss Loughlam | 2016-12-14 19:40:22 UTC | Priority | unspecified | medium |
| CC | aloughla | |||
| Rashid Khan | 2017-03-11 01:46:52 UTC | CC | mleitner | |
| sushil kulkarni | 2017-07-14 07:38:25 UTC | Blocks | 1470965 | |
| Vladimir Benes | 2017-08-02 09:34:48 UTC | CC | vbenes | |
| Ioanna Gkioka | 2017-09-13 13:52:38 UTC | Blocks | 1491315 | |
| Francesco Giudici | 2017-10-24 08:49:20 UTC | Status | NEW | ASSIGNED |
| Francesco Giudici | 2017-10-30 23:02:59 UTC | Status | ASSIGNED | POST |
| Francesco Giudici | 2017-10-30 23:13:04 UTC | Blocks | 1225471 | |
| Lenka Špačková | 2017-11-09 14:05:27 UTC | Docs Contact | igkioka | |
| Ioanna Gkioka | 2017-12-06 13:42:06 UTC | Flags | needinfo?(fgiudici) | |
| Francesco Giudici | 2017-12-06 23:03:43 UTC | Flags | needinfo?(fgiudici) | |
| Francesco Giudici | 2017-12-11 10:18:40 UTC | Status | POST | MODIFIED |
| Francesco Giudici | 2017-12-11 10:28:41 UTC | Doc Text | Connections of type "team" were allowed to set team properties through a json string put in the 'team.config' property. Now the 'team' setting exposes each single team property: team.notify-peers-count: team.notify-peers-interval: team.mcast-rejoin-count: team.mcast-rejoin-interval: team.runner: team.runner-hwaddr-policy: team.runner-tx-hash: team.runner-tx-balancer: team.runner-tx-balancer- interval: team.runner-active: team.runner-fast-rate: team.runner-sys-prio: team.runner-min-ports: team.runner-agg-select-policy: team.link-watchers: each single property is kept in sync with the 'team.config' one that will still carry the full config in json format. So, while the user may still use the old 'team.config' property to configure the team connection, the user may also leverage the new single properties that once changed will trigger the update of the 'team.config' json string. If instead the 'team.config' is set, all the exposed properties will be updated accordingly. Note that when changing the team.runner, all the properties related to specific runners will be reset to the default for the new selected runner. | |
| Doc Type | Enhancement | Release Note | ||
| errata-xmlrpc | 2017-12-12 02:58:18 UTC | Status | MODIFIED | ON_QA |
| Ioanna Gkioka | 2017-12-14 15:16:21 UTC | Doc Text | Connections of type "team" were allowed to set team properties through a json string put in the 'team.config' property. Now the 'team' setting exposes each single team property: team.notify-peers-count: team.notify-peers-interval: team.mcast-rejoin-count: team.mcast-rejoin-interval: team.runner: team.runner-hwaddr-policy: team.runner-tx-hash: team.runner-tx-balancer: team.runner-tx-balancer- interval: team.runner-active: team.runner-fast-rate: team.runner-sys-prio: team.runner-min-ports: team.runner-agg-select-policy: team.link-watchers: each single property is kept in sync with the 'team.config' one that will still carry the full config in json format. So, while the user may still use the old 'team.config' property to configure the team connection, the user may also leverage the new single properties that once changed will trigger the update of the 'team.config' json string. If instead the 'team.config' is set, all the exposed properties will be updated accordingly. Note that when changing the team.runner, all the properties related to specific runners will be reset to the default for the new selected runner. | Support for exposing all team properties through the team setting feature Previously, properties of the team connection were set using the "team.config" file. With this update, all properties can be exposed and configured through the team setting feature. As a result, both "team.config" and the input from the team setting feature are synchronized. This means that any configuration changed in "team.conf" is reflected to the team setting feature and all the exposed properties are updated accordingly. Note that when changing the `team.runner` property, all the properties related to specific runners are reset to default. |
| Flags | needinfo?(fgiudici) | |||
| Francesco Giudici | 2017-12-15 10:28:16 UTC | Doc Text | Support for exposing all team properties through the team setting feature Previously, properties of the team connection were set using the "team.config" file. With this update, all properties can be exposed and configured through the team setting feature. As a result, both "team.config" and the input from the team setting feature are synchronized. This means that any configuration changed in "team.conf" is reflected to the team setting feature and all the exposed properties are updated accordingly. Note that when changing the `team.runner` property, all the properties related to specific runners are reset to default. | Add new properties to expose all team options Previously, team configuration was applied to connections providing a json string to the only property available in the team setting: the "config" property. With this update, new properties have been added, matching one to one the team configuration options. As a result, configuration could be provided either via a unique json string in the "config" property either assigning values to the new team properties. Any configuration change applied in the "config" is reflected to the new team properties and vice versa. Note that when changing the brand new `runner` property, all the properties related to specific runners are reset to default. |
| Flags | needinfo?(fgiudici) | |||
| Ioanna Gkioka | 2017-12-18 10:12:20 UTC | Doc Text | Add new properties to expose all team options Previously, team configuration was applied to connections providing a json string to the only property available in the team setting: the "config" property. With this update, new properties have been added, matching one to one the team configuration options. As a result, configuration could be provided either via a unique json string in the "config" property either assigning values to the new team properties. Any configuration change applied in the "config" is reflected to the new team properties and vice versa. Note that when changing the brand new `runner` property, all the properties related to specific runners are reset to default. | New properties to expose all team options Previously, team configuration was applied to connections providing a JSON string to the `config` property which was the only property available in the team setting. This update adds new properties matching one to one the team configuration options. As a result, the configuration is provided either through a unique JSON string in the `config` property or assigning values to the new team properties. Any configuration change applied in `config` is reflected to the new team properties and vice versa. Note that when changing the brand new `runner` property, all the properties related to specific runners are reset to default. |
| Flags | needinfo?(fgiudici) | |||
| Francesco Giudici | 2017-12-18 10:25:54 UTC | Flags | needinfo?(fgiudici) | |
| Thomas Haller | 2017-12-20 16:51:49 UTC | Blocks | 1225471 | |
| Vladimir Benes | 2018-01-16 09:06:23 UTC | Status | ON_QA | VERIFIED |
| Pasi Karkkainen | 2018-01-24 20:28:44 UTC | CC | pasik | |
| Marcelo Ricardo Leitner | 2018-03-15 20:44:47 UTC | CC | igkioka | |
| Flags | needinfo?(igkioka) | |||
| Francesco Giudici | 2018-03-16 09:40:55 UTC | Doc Text | New properties to expose all team options Previously, team configuration was applied to connections providing a JSON string to the `config` property which was the only property available in the team setting. This update adds new properties matching one to one the team configuration options. As a result, the configuration is provided either through a unique JSON string in the `config` property or assigning values to the new team properties. Any configuration change applied in `config` is reflected to the new team properties and vice versa. Note that when changing the brand new `runner` property, all the properties related to specific runners are reset to default. | NetworkManager exposes new properties to expose team options Previously, NetworkManager applied team configuration to connections providing a JSON string to the `config` property, which was the only property available in the team setting. This update adds new properties in NetworkManager matching one to one the team configuration options. As a result, the configuration may be provided either through a unique JSON string in the NetworkManager `config` property or assigning values to the new team properties. Any configuration change applied in `config` is reflected to the new team properties and vice versa. Correct configuration of team link watchers and runner is now enforced in NetworkManager: wrong or unknown link watcher and runner configurations will result in the full team connection being rejected. Note that when changing the brand new `runner` property, all the properties related to specific runners are reset to default. |
| Ioanna Gkioka | 2018-03-16 12:13:26 UTC | Doc Text | NetworkManager exposes new properties to expose team options Previously, NetworkManager applied team configuration to connections providing a JSON string to the `config` property, which was the only property available in the team setting. This update adds new properties in NetworkManager matching one to one the team configuration options. As a result, the configuration may be provided either through a unique JSON string in the NetworkManager `config` property or assigning values to the new team properties. Any configuration change applied in `config` is reflected to the new team properties and vice versa. Correct configuration of team link watchers and runner is now enforced in NetworkManager: wrong or unknown link watcher and runner configurations will result in the full team connection being rejected. Note that when changing the brand new `runner` property, all the properties related to specific runners are reset to default. | `NetworkManager` exposes new properties to expose team options Previously, `NetworkManager` applied team configuration to connections providing a JSON string to the `config` property, which was the only property available in the team setting. This update adds new properties in `NetworkManager` matching one to one the team configuration options. As a result, the configuration may be provided either through a unique JSON string in the `NetworkManager` `config` property or assigning values to the new team properties. Any configuration change applied in `config` is reflected to the new team properties and vice versa. The correct configuration of team link-watchers and team.runner is now enforced in `NetworkManager`. Wrong or unknown link-watcher and team.runner configurations result in the full team connection being rejected. Note that when changing the brand new `runner` property, all the properties related to specific runners are reset to default. |
| Flags | needinfo?(igkioka) | needinfo?(fgiudici) | ||
| Francesco Giudici | 2018-03-16 12:38:29 UTC | Flags | needinfo?(fgiudici) | needinfo?(mleitner) |
| Lenka Špačková | 2018-03-19 14:10:17 UTC | Doc Text | `NetworkManager` exposes new properties to expose team options Previously, `NetworkManager` applied team configuration to connections providing a JSON string to the `config` property, which was the only property available in the team setting. This update adds new properties in `NetworkManager` matching one to one the team configuration options. As a result, the configuration may be provided either through a unique JSON string in the `NetworkManager` `config` property or assigning values to the new team properties. Any configuration change applied in `config` is reflected to the new team properties and vice versa. The correct configuration of team link-watchers and team.runner is now enforced in `NetworkManager`. Wrong or unknown link-watcher and team.runner configurations result in the full team connection being rejected. Note that when changing the brand new `runner` property, all the properties related to specific runners are reset to default. | `NetworkManager` exposes new properties to expose team options Previously, `NetworkManager` applied team configuration to connections providing a JSON string to the `config` property, which was the only property available in the team setting. This update adds new properties in `NetworkManager` matching one to one the team configuration options. As a result, the configuration may be provided either through a unique JSON string in the `NetworkManager config` property or assigning values to the new team properties. Any configuration change applied in `config` is reflected to the new team properties and vice versa. The correct configuration of team link-watchers and team.runner is now enforced in `NetworkManager`. Wrong or unknown link-watcher and team.runner configurations result in the full team connection being rejected. Note that when changing the brand new `runner` property, all the properties related to specific runners are reset to default. |
| Marcelo Ricardo Leitner | 2018-03-20 17:54:35 UTC | Flags | needinfo?(mleitner) | |
| errata-xmlrpc | 2018-04-10 01:18:25 UTC | Status | VERIFIED | RELEASE_PENDING |
| errata-xmlrpc | 2018-04-10 13:19:11 UTC | Status | RELEASE_PENDING | CLOSED |
| Resolution | --- | ERRATA | ||
| Last Closed | 2018-04-10 09:19:11 UTC | |||
| errata-xmlrpc | 2018-04-10 13:21:22 UTC | Link ID | Red Hat Product Errata RHBA-2018:0778 |
Back to bug 1398925