Branch: refs/heads/testing
Home: https://github.com/openSUSE/wicked
Commit: 5f5b266e3917aacd2fb2975e556df8e8805bdc5e
https://github.com/openSUSE/wicked/commit/5f5b266e3917aacd2fb2975e556df8e880...
Author: Karol Mroz
Date: 2015-07-31 (Fri, 31 Jul 2015)
Changed paths:
M client/compat.c
M client/suse/compat-suse.c
M include/wicked/bridge.h
M src/bridge.c
Log Message:
-----------
Merge pull request #575 from mtomaschewski/ifcfg-slaves-master
ifcfg: generate link master from master config, added MASTER_DEVICE variable
Commit: 056602c1a14b09b6eec65b374e85a377b0935949
https://github.com/openSUSE/wicked/commit/056602c1a14b09b6eec65b374e85a377b0...
Author: Karol Mroz
Date: 2015-07-31 (Fri, 31 Jul 2015)
Changed paths:
M src/ifconfig.c
Log Message:
-----------
ifconfig: handle link up of externally enslaved devices
In the case of standard openvswitch bridge ports, they are enslaved
by openvswitch itself to the ovs-master interface (kernel datapath
interface).
In such scenarios, we previously skipped the linkUp process, as Wicked
assumed that if a device was already enslaved, it was done via
ni_system_interface_enslave(), which generates a netlink message to
enslave and perform a link-up in bridge case, and a bonding master
manages the link state itself.
To get around this, if a device has a master, we should first check to
see if it's in link-up state. If yes, then it was enslaved by Wicked
and no furhter processing is needed. If not, then it was enslaved
externally and we need to perform the basic link-up.
Commit: b9cb2164b117371abb48c851c9c6765ba940a854
https://github.com/openSUSE/wicked/commit/b9cb2164b117371abb48c851c9c6765ba9...
Author: Marius Tomaschewski
Date: 2015-07-31 (Fri, 31 Jul 2015)
Changed paths:
M src/ifconfig.c
Log Message:
-----------
Merge pull request #577 from mtomaschewski/link-ovs-enslave
Compare: https://github.com/openSUSE/wicked/compare/136114d00de0...b9cb2164b117
