Skip to content
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

Merged
merged 1 commit into from
Oct 8, 2024
Merged

Conversation

Fredi-raspall
Copy link
Contributor

  • Unified some formatting.
  • removed spurious ```yaml that was being rendered.
  • Fixed the definitions for VLANNamespace and IPv4Namespace, which were swapped.

Copy link

github-actions bot commented Sep 30, 2024

🚀 Deployed on https://preview-39--hedgehog-docs.netlify.app

@github-actions github-actions bot temporarily deployed to pull request September 30, 2024 07:56 Inactive
@Fredi-raspall
Copy link
Contributor Author

I also found the definition of isolated and restricted subnets a bit confusing, esp. in some comments where it says that it does not affect VPC peering, and the relation to permit lists. Are isolated and restricted meant to be some default initial config that can be overridden by permit lists? Is the idea like in firewalls where you can deny everything and the except the accepted or allow everything and then except the stuff to be blocked? IMO either a commented example or the interaction would make it clearer... or maybe a matrix with distinct combinations.

Copy link
Contributor

@mrbojangles3 mrbojangles3 left a 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

@@ -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
Copy link
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

"similar a" - typo?

@@ -86,15 +86,15 @@ Switch boot and installation.
* Actual SONiC installers
* Miscellaneous: rsyslog/ntp

## Fabric
## Fabric Agent
Copy link
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

It's "Fabric"

Copy link
Contributor Author

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 ...

Copy link
Member

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

Copy link
Contributor Author

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 ...


Control plane and switch agent.
Control-plane and switch agent.
Copy link
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

No hyphen needed


```yaml
apiVersion: wiring.githedgehog.com/v1alpha2
kind: VLANNamespace
kind: VLANNamespac`
Copy link
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

typo

Copy link
Contributor Author

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 ...

@Frostman
Copy link
Member

I also found the definition of isolated and restricted subnets a bit confusing, esp. in some comments where it says that it does not affect VPC peering, and the relation to permit lists. Are isolated and restricted meant to be some default initial config that can be overridden by permit lists? Is the idea like in firewalls where you can deny everything and the except the accepted or allow everything and then except the stuff to be blocked? IMO either a commented example or the interaction would make it clearer... or maybe a matrix with distinct combinations.

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.

@Fredi-raspall
Copy link
Contributor Author

I also found the definition of isolated and restricted subnets a bit confusing, esp. in some comments where it says that it does not affect VPC peering, and the relation to permit lists. Are isolated and restricted meant to be some default initial config that can be overridden by permit lists? Is the idea like in firewalls where you can deny everything and the except the accepted or allow everything and then except the stuff to be blocked? IMO either a commented example or the interaction would make it clearer... or maybe a matrix with distinct combinations.

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?).

@github-actions github-actions bot temporarily deployed to pull request September 30, 2024 15:43 Inactive
@github-actions github-actions bot temporarily deployed to pull request September 30, 2024 16:14 Inactive
@Frostman
Copy link
Member

Frostman commented Sep 30, 2024

@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

@Fredi-raspall
Copy link
Contributor Author

Understood @Frostman . Thanks!

@github-actions github-actions bot temporarily deployed to pull request October 8, 2024 11:08 Inactive
@Fredi-raspall
Copy link
Contributor Author

@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!

mrbojangles3
mrbojangles3 previously approved these changes Oct 8, 2024
@@ -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 |
Copy link
Member

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.

Copy link
Contributor Author

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?

Copy link
Contributor Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

I've removed it.

Copy link
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.


## 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.
Copy link
Member

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

Copy link
Contributor Author

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"

@@ -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
Copy link
Member

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.

Copy link
Contributor Author

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:

Copy link
Contributor Author

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.
@github-actions github-actions bot temporarily deployed to pull request October 8, 2024 17:31 Inactive
@Frostman
Copy link
Member

Frostman commented Oct 8, 2024

@Fredi-raspall thank you!

@Frostman Frostman merged commit 4065c95 into master Oct 8, 2024
2 checks passed
@Frostman Frostman deleted the fredi/minor_fixes branch October 8, 2024 17:45
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

3 participants