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.

Sign up for GitHub

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

Jump to bottom

Dynamically assign boundary services address #3278

Closed
internet-diglett opened this issue Jun 2, 2023 · 2 comments
Closed

Dynamically assign boundary services address #3278

internet-diglett opened this issue Jun 2, 2023 · 2 comments
Labels
networking Related to the networking.

Comments

@internet-diglett
Copy link
Contributor

Currently the boundary services address is hard-coded to be assigned to the first switch. Once we enable multi-switch capability, we will need to be able to determine which switch should get the address based off of the configuration.
@internet-diglett internet-diglett added the networking Related to the networking. label Jun 2, 2023
@internet-diglett internet-diglett mentioned this issue Jun 2, 2023
Merged
@internet-diglett
Copy link
Contributor Author

Ref: #3262 (comment)

Currently the strategy being implemented in #3262 is to create NAT entries on switches that have external networking configured.

@davepacheco davepacheco mentioned this issue Jan 17, 2024
Closed
@rcgoodfellow
Copy link
Contributor

As of #3859 boundary services underlay addresses are no longer managed by Omicron. They are transient dynamic addresses that are managed by mgd with a lifetime that is tied to the switch zone lifetime they are assigned to. More details are in RFD 404 Section 2.1.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
networking Related to the networking.
Projects
None yet
Milestone
No milestone
Development

No branches or pull requests
2 participants
@rcgoodfellow @internet-diglett