Tue, Jul 16, 2013 at 04:32:10PM CEST, d...@redhat.com wrote:
>On Tue, 2013-07-16 at 10:53 +0200, Jiri Pirko wrote:
>> Mon, Jul 15, 2013 at 08:22:27PM CEST, d...@gnome.org wrote:
>> >On 07/14/2013 11:29 AM, Jiri Pirko wrote:
>> >> teamd config is non-trivial tree structure (JSON). At this point, the
On Tue, 2013-07-16 at 10:53 +0200, Jiri Pirko wrote:
> Mon, Jul 15, 2013 at 08:22:27PM CEST, d...@gnome.org wrote:
> >On 07/14/2013 11:29 AM, Jiri Pirko wrote:
> >> teamd config is non-trivial tree structure (JSON). At this point, there is
> >> really no point to have NM to be aware of the teamd co
Mon, Jul 15, 2013 at 08:22:27PM CEST, d...@gnome.org wrote:
>On 07/14/2013 11:29 AM, Jiri Pirko wrote:
>> teamd config is non-trivial tree structure (JSON). At this point, there is
>> really no point to have NM to be aware of the teamd config structure.
>> Once NM will need that, this can be change
On 07/14/2013 11:29 AM, Jiri Pirko wrote:
> teamd config is non-trivial tree structure (JSON). At this point, there is
> really no point to have NM to be aware of the teamd config structure.
> Once NM will need that, this can be changed.
NM will need to be aware of it once we want to add support f
> From: "Jiri Pirko"
>
> Fri, Jul 12, 2013 at 10:08:49PM CEST, d...@gnome.org wrote:
> >On 07/11/2013 11:31 AM, Jiri Pirko wrote:
> >> I heavily reused existing code, mainly bonding parts.
> >
> >Makes sense (and makes it easy to review...)
> >
> >> The only thing not
> >> implemented yet is dbus
Fri, Jul 12, 2013 at 10:08:49PM CEST, d...@gnome.org wrote:
>On 07/11/2013 11:31 AM, Jiri Pirko wrote:
>> I heavily reused existing code, mainly bonding parts.
>
>Makes sense (and makes it easy to review...)
>
>> The only thing not
>> implemented yet is dbus communication with teamd (used particula
On 07/11/2013 11:31 AM, Jiri Pirko wrote:
> I heavily reused existing code, mainly bonding parts.
Makes sense (and makes it easy to review...)
> The only thing not
> implemented yet is dbus communication with teamd (used particulary for
> port config setup).
Will that allow you to shut down team
I heavily reused existing code, mainly bonding parts. The only thing not
implemented yet is dbus communication with teamd (used particulary for
port config setup). That I want to add once this patchset gets applied.
Jiri Pirko (6):
add support for team device
add setting for team port
ifcfg: