update network section

[phillxnet]

We now have roles for interfaces so we need to add this.

io - general use ie all of the following 3 (default)
management - Web-UI only
Replication - replication only
unassigned - not to be used

Please update the following forum thread with progress on this doc:-
http://forum.rockstor.com/t/network-interface-role-info-and-quirks/997/1

N.B. there may be a need to update / improve mouse over info on these roles in rockstor-core.

And we also have teaming and bonding capability now. Perhaps, given at least 802.3ad also requires switch configuration, a concrete example covering the switch config would be good as a separate howto.
Linking to a recent forum post on bonding/teaming where I have produced some required images for this howto:
https://forum.rockstor.com/t/network-port-bonding/3517/2

[phillxnet]

Connecting with existing open issue in rockstor-core relating to network tooltips:-
rockstor/rockstor-core#1146

[FroggyFlox]

Hi @phillxnet,

I don't think the first part of this issue still applies as interface roles have changed (rockstor/rockstor-core#1146 (comment) and https://forum.rockstor.com/t/network-interface-role-info-and-quirks/997/5?u=flox), but the second part related to the description of teaming and bonding capabilities is still valid.

As I have added to the Network sections in my current rock-on networking work, I can update screenshots and add more details re-network creation and editing if you still see some use for this. I won't be able to write the documentation on teaming and bonding, however, but I can at least correct the mention that Rockstor does not support it.

I was thinking of creating a dedicated issue for the documentation on my upcoming rock-on related modifications as I will not be able to fully address this issue, but let me know if you prefer me to simply update this issue instead.

[phillxnet]

@FroggyFlox Thanks for this. I've now created the linked and more focused issue. It may be that this issue was simply too broad in the first place. Feel free to close this issue and open a more up-to-date companion issue as I know you are panning on adding some network changes soon anyway. So it may be we can tackle this one once those changes are merged.

[FroggyFlox]

Thanks a lot for creating that issue with its additional details. I agree with you and am thus closing this issue. Once I have the docker networking PR submitted and merged, I'll go ahead and create an issue here to update the Network section of our docs accordingly.