Network UI mockups

[Andreas Nilsson]

Hi everyone!
I spoke to Colin (since he wanted to look at that this week) and Patrick 
earlier today about what we need to do for Networks in the immediate 
future, based on the feedback from Russ:
* Regular connections (and changing the details of those)
* Bridging
* Bonding
* See how the connection is doing (performance+errors)

It's also important that the design supports at least 4 ports or more 
(as in 4 cards or a card with 4 ports).

I've put some initial designs up here:
https://github.com/cockpit-project/cockpit/wiki/Network

Let me know what you think, if there is anything missing, if something 
that is unclear, or just plain wrong.
- Andreas

[Stephen Gallagher]

-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1

On Mon 20 Jan 2014 02:43:43 PM EST, Andreas Nilsson wrote:
>  Hi everyone! I spoke to Colin (since he wanted to look at that this
>  week) and Patrick earlier today about what we need to do for
>  Networks in the immediate future, based on the feedback from Russ: 
>  * Regular connections (and changing the details of those) *
>  Bridging * Bonding * See how the connection is doing
>  (performance+errors)
>  
>  It's also important that the design supports at least 4 ports or
>  more (as in 4 cards or a card with 4 ports).
>  
>  I've put some initial designs up here: 
>  https://github.com/cockpit-project/cockpit/wiki/Network
>  
>  Let me know what you think, if there is anything missing, if
>  something that is unclear, or just plain wrong. 
Just as a general warning, please do not use "master/slave"
terminology when describing the bridge relationship. That's becoming
quite culturally unacceptable these days. Maybe "external/internal" or
"public/private" when talking about bridges? Or even "Bridge ____ to
____"
> -----BEGIN PGP SIGNATURE-----
> Version: GnuPG v1
> Comment: Using GnuPG with Thunderbird - http://www.enigmail.net/
>
> iEYEARECAAYFAlLehmQACgkQeiVVYja6o6NFxwCfcewMlaYIrz/gSIi6DBOlVefu
> 8XEAn01WumMOIzXZnPbVioqJWn3YKT+K
> =8+/F
> -----END PGP SIGNATURE-----

[Andreas Nilsson]

On 01/21/2014 12:38 PM, Stephen Gallagher wrote:
>  Just as a general warning, please do not use
> "master/slave"
>  terminology when describing the bridge relationship. That's becoming
>  quite culturally unacceptable these days. Maybe "external/internal" or
>  "public/private" when talking about bridges? Or even "Bridge ____ to
> ____" 
Good point. I think I took that from a piece of documentation on Linux 
network in the belief that it was a established term.
I like your last proposal of Bridge _______ to _______
Thanks!
- Andreas