-
Notifications
You must be signed in to change notification settings - Fork 7
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
Misc. minor corrections, including: #39
Conversation
Fredi-raspall
commented
Sep 30, 2024
- Unified some formatting.
- removed spurious ```yaml that was being rendered.
- Fixed the definitions for VLANNamespace and IPv4Namespace, which were swapped.
🚀 Deployed on https://preview-39--hedgehog-docs.netlify.app |
I also found the definition of isolated and restricted subnets a bit confusing, esp. in some comments where it says that |
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.
Couple of small changes
docs/concepts/overview.md
Outdated
@@ -41,8 +41,8 @@ Wiring Diagram consists of the following resources: | |||
### User-facing API | |||
|
|||
* VPC API | |||
* __VPC__: Virtual Private Cloud, similar to the public cloud VPC it provides an isolated private network for the | |||
resources, with support for multiple subnets, each with user-provided VLANs and on-demand DHCP | |||
* __VPC__: Virtual Private Cloud, similar a the public cloud VPC, provides an isolated private network for the |
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.
"similar a" - typo?
docs/concepts/overview.md
Outdated
@@ -86,15 +86,15 @@ Switch boot and installation. | |||
* Actual SONiC installers | |||
* Miscellaneous: rsyslog/ntp | |||
|
|||
## Fabric | |||
## Fabric Agent |
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.
It's "Fabric"
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.
Yes, I know the agent is called Fabric. However, on my first read, I thought it would have been clearer to stress that it is an agent, since "fabric" could refer to the HH Fabric. Removing it ...
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.
IMO it refers to the HH Fabric here
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.
Does it? When I said "HH Fabric" I meant the switches + control nodes ...
docs/concepts/overview.md
Outdated
|
||
Control plane and switch agent. | ||
Control-plane and switch agent. |
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.
No hyphen needed
docs/user-guide/vpcs.md
Outdated
|
||
```yaml | ||
apiVersion: wiring.githedgehog.com/v1alpha2 | ||
kind: VLANNamespace | ||
kind: VLANNamespac` |
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.
typo
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.
Oh boy. I was hoping to fix typos on my way through the documentation.... not meaning to add new ...
Yeah, isolated/resitricted/permit (in the VPC spec) are little bit tricky. Using any of them only affects access between the subnets within a VPC and doesn't affect VPC peering which has its own controls. Permit lists are "Overrides" on top of having defaultIsolated/defaultRestricted and/or isolated/restircted set on the specific subnets. Example would be setting defaultIsolated to true (no subnets in VPC can talk to each other) and explicitly listing subnets that should be able to talk in the permit list. |
Thanks for the explanation @Frostman . Does this mean that if subnets are defined with isolated = False, then no permit list is needed and they can freely communicate (there's no deny-list, right?). |
635081a
to
0d5e32d
Compare
0d5e32d
to
01349f5
Compare
@Fredi-raspall correct, by default both isolated and restricted are false and so all subnets within a VPC can talk to each other as well as all hosts within every subnet can talk to each other too |
Understood @Frostman . Thanks! |
01349f5
to
66be916
Compare
@Frostman , @mrbojangles3 I think I've gone through most of the documentation now and believe to have corrected existing minor things (plus my personal contributions ;-) ). I've also added a table to ease the access to the supported platforms. I don't plan to work more on this branch, so a quick review from either of you would be great. Thx! |
docs/reference/profiles.md
Outdated
@@ -3,6 +3,19 @@ | |||
The following is a list of all supported switches. Please, make sure to use the version of documentation that matches your environment to get an | |||
up-to-date list of supported switches, their features and port naming scheme. | |||
|
|||
| Switch Platforms | |
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 file is generated from fabric repo, so, shouldn't be edited directly.
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'm fine removing the table. Maybe one could be auto-generated then?
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've removed it.
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.
Yes, we can gen it, it's a good idea. It's done in https://github.com/githedgehog/fabric/blob/master/pkg/gen/profilesref/profilesref.go
docs/user-guide/connections.md
Outdated
|
||
## Server connections (user-facing) | ||
|
||
Server connections are used to connect workload servers to the switches. | ||
Server connections are used to connect workload (or control) servers to switches. |
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.
Those connections are only used for workload servers
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've removed it and changed section name to "Workload server connections"
docs/concepts/overview.md
Outdated
@@ -29,9 +29,9 @@ systems. | |||
|
|||
Wiring Diagram consists of the following resources: | |||
|
|||
* "Devices": describes any device in the Fabric | |||
* __Devices__: describes *any* device in the Fabric |
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.
There is no such object named Device, so I was trying to separate it somehow from Switches and Servers. What do you think? I'm ok both ways.
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've reverted it to quotes and rephrased as:
"Devices": describe any device in the Fabric and can be of two types:
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.
@Frostman I think I've addressed all the comments and believe this is good to go.
Including: * Unified some formatting. * removed spurious ```yaml that was being rendered. * Fixed the definitions for VLANNamespace and IPv4Namespace, which were swapped.
66be916
to
143e173
Compare
@Fredi-raspall thank you! |