-
Notifications
You must be signed in to change notification settings - Fork 19
Network revisited docs #325
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Conversation
Codecov Report
@@ Coverage Diff @@
## master #325 +/- ##
==========================================
+ Coverage 39.17% 49.6% +10.42%
==========================================
Files 58 26 -32
Lines 3602 1252 -2350
==========================================
- Hits 1411 621 -790
+ Misses 1999 578 -1421
+ Partials 192 53 -139
Continue to review full report at Codecov.
|
zaibon
left a comment
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Added some inline comments and typo fixes.
I also don't see the point of the setup directory being added in this PR.
Also this PR should push the documentation into /docs/network and not /docs/network_new
old /docs can be totally deleted since not relevant anymore
| @@ -0,0 +1,122 @@ | |||
| # Zero-Mesh | |||
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
I don't think this field is linked from anywhere. We should have an Index page for all the network docs an referring this file from it
docs/network_new/README.md
Outdated
| - **CNI** | ||
| ZOS and it's Wireguard mesh per user is a quite novel way to do things, but there are many overlay networks that are built to solve other network requirements in very different ways, and these solutions could be intagrated in a later phase, through the use of `CNI`, a common way to request a network for a user, or for a specific workload. | ||
|
|
||
| - **automated provisioning** |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
As far as I know this is not on the roadmap at all. So I would remove this paragraph altogether
docs/network_new/README.md
Outdated
| As such, these nodes can only partake in a network as client-only towards publicly reachable peers, and can only initiate the connections themselves. (ref previous drawing). | ||
| To make sure connectivity stays up, the clients (all) have a keepalive towards all their peers so that communications towards network resources in hidden nodes can be established. | ||
|
|
||
| ## caveats |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
This caveats paragraph is actually what the farmer needs to be aware of when configuring their farm network.
@andhartl can you check if this is enough for them or should we add more detail ?
We should also reference this paragraph from the index of the network documentation as Farm network consideration
docs/network_new/network_module.md
Outdated
|
|
||
| ```go | ||
| //Networker is the interface for the network module | ||
| type Networker interface { |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
| type Networker interface { | |
| type Networker interface { | |
| // Create a new network resource | |
| CreateNR(Network) (string, error) | |
| // Delete a network resource | |
| DeleteNR(Network) error | |
| // Join a network (with network id) will create a new isolated namespace | |
| // that is hooked to the network bridge with a veth pair, and assign it a | |
| // new IP from the network resource range. The method return the new namespace | |
| // name. | |
| // The member name specifies the name of the member, and must be unique | |
| // The NetID is the network id to join | |
| Join(networkdID NetID, containerID string, addrs []string) (join Member, err error) | |
| // Leave delete a container nameapce created by Join | |
| Leave(networkdID NetID, containerID string) (err error) | |
| // ZDBPrepare creates a network namespace with a macvlan interface into it | |
| // to allow the 0-db container to be publicly accessible | |
| // it retusn the name of the network namespace created | |
| ZDBPrepare() (string, error) | |
| // Addrs return the IP addresses of interface | |
| // if the interface is in a network namespace netns needs to be not empty | |
| Addrs(iface string, netns string) ([]net.IP, error) | |
| } |
docs/network_new/network_module.md
Outdated
|
|
||
| ## Zero-OS networking | ||
|
|
||
| ### Some First Explanations |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
This sounds like redundant with the rest of the documentation. Let's get rid of this.
docs/network_new/network_module.md
Outdated
|
|
||
| [Here some thought dumps from where we started working this out](../../specs/network/Requirements.md) | ||
|
|
||
| ### Jargon |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Let's convert this paragraph into a proper glossary page that we can reference throughout the all network documentation.
Co-Authored-By: Christophe de Carvalho <zaibon@users.noreply.github.com>
Co-Authored-By: Christophe de Carvalho <zaibon@users.noreply.github.com>
Co-Authored-By: Christophe de Carvalho <zaibon@users.noreply.github.com>
Co-Authored-By: Christophe de Carvalho <zaibon@users.noreply.github.com>
9d0924d to
9eae78e
Compare
No description provided.