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

Proposal for supporting trunked port environments #60

Merged
merged 2 commits into from
Oct 11, 2022

Conversation

jacobweinstock
Copy link
Member

@jacobweinstock jacobweinstock commented Aug 23, 2022

Description

Add support for trunked port environments.
Rendered proposal: https://github.com/jacobweinstock/proposals/blob/vlan-support/proposals/0030/README.md

Why is this needed

Fixes: #

How Has This Been Tested?

How are existing users impacted? What migration steps/scripts do we need?

Checklist:

I have:

  • updated the documentation and/or roadmap (if required)
  • added unit or e2e tests
  • provided instructions on how to upgrade

View rendered proposals/0030/README.md

chrisdoherty4
chrisdoherty4 previously approved these changes Sep 8, 2022
Copy link
Member

@chrisdoherty4 chrisdoherty4 left a comment

Choose a reason for hiding this comment

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

Reviewed a while back. Not sure why I didn't approve. Looks great!

mergify bot added a commit to tinkerbell/ipxedust that referenced this pull request Sep 8, 2022
## Description


This allows creating an interface with a vlan tag based off of DHCP option 43, suboption 116. This will not change the existing behavior. The vlan interface is only created if DHCP option 43.116 is set. This PR is the start of the implementation of [proposal 28](tinkerbell/proposals#60).

## Why is this needed



Fixes: #

## How Has This Been Tested?



I have manually test this.


## How are existing users impacted? What migration steps/scripts do we need?



No impact.


## Checklist:

I have:

- [ ] updated the documentation and/or roadmap (if required)
- [ ] added unit or e2e tests
- [ ] provided instructions on how to upgrade
proposals/0028/README.md Outdated Show resolved Hide resolved
Another proposal was merged as 0028, so I
moved this one to 0030. Also, added a comment
regarding DHCP option 132.

Signed-off-by: Jacob Weinstock <[email protected]>
mergify bot added a commit to tinkerbell/tink that referenced this pull request Sep 16, 2022
## Description


This adds vlan id to interfaces in the hardware spec.

FYI, hidden inside of all this generated code, linting, and dependency version updates is the reason for this PR. The small addition of vlan id to the hardware interface struct. Look here: `/pkg/apis/core/v1alpha1/hardware_types.go`.

Also, important to note that this PR updates the Go version from `1.17` to `1.18`, this was required to get the make targets for generating code functioning properly for me.

## Why is this needed


Needed to enabled trunk port support across the stack. See proposal tinkerbell/proposals#60

Fixes: #

## How Has This Been Tested?





## How are existing users impacted? What migration steps/scripts do we need?





## Checklist:

I have:

- [ ] updated the documentation and/or roadmap (if required)
- [ ] added unit or e2e tests
- [ ] provided instructions on how to upgrade
mergify bot added a commit to tinkerbell/smee that referenced this pull request Sep 23, 2022
## Description


This enables Boots to setup DHCP option 43, sub option 116 with the VLAN ID pulled from the hardware record. This also adds a kernel command line parameter to the default (OSIE) installer auto.ipxe script with the vlan id (`vlan_id=`). This will enable Hook to create a tagged vlan interface when it boots up. This is all inline with proposal [0030](tinkerbell/proposals#60). 

This is only being implemented with the Kubernetes backend. The Tink+Postgresql is [deprecated](https://github.com/tinkerbell/proposals/tree/main/proposals/0029) and the Cacher backend is not officially deprecated (yet) but should be considered legacy. 

## Why is this needed



Fixes: #

## How Has This Been Tested?



Manual testing following the K3D guide [here](https://github.com/tinkerbell/boots/blob/main/docs/manifests/k3d.md).


## How are existing users impacted? What migration steps/scripts do we need?



No impacts.


## Checklist:

I have:

- [ ] updated the documentation and/or roadmap (if required)
- [ ] added unit or e2e tests
- [ ] provided instructions on how to upgrade
Hopefully this will help folks that want to dig
into this option 132 a little more.

Signed-off-by: Jacob Weinstock <[email protected]>
@jacobweinstock jacobweinstock requested review from displague and removed request for displague October 5, 2022 01:16
@jacobweinstock jacobweinstock added the ready-to-merge Signal to Mergify to merge the PR. label Oct 11, 2022
@jacobweinstock jacobweinstock requested review from chrisdoherty4 and removed request for chrisdoherty4 October 11, 2022 12:43
@mergify mergify bot merged commit 28ad006 into tinkerbell:main Oct 11, 2022
chrisdoherty4 pushed a commit to chrisdoherty4/tinkerbell-proposals that referenced this pull request Jan 14, 2023
## Description

Add support for trunked port environments.
Rendered proposal: https://github.com/jacobweinstock/proposals/blob/vlan-support/proposals/0030/README.md

## Why is this needed

Fixes: #

## How Has This Been Tested?

## How are existing users impacted? What migration steps/scripts do we need?

## Checklist:

I have:

- [ ] updated the documentation and/or roadmap (if required)
- [ ] added unit or e2e tests
- [ ] provided instructions on how to upgrade

-----
[View rendered proposals/0030/README.md](https://github.com/jacobweinstock/proposals/blob/vlan-support/proposals/0030/README.md)

Signed-off-by: Chris Doherty <[email protected]>
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
ready-to-merge Signal to Mergify to merge the PR.
Projects
None yet
Development

Successfully merging this pull request may close these issues.

3 participants