Skip to content

image: separate IPv6 address configuration by NIC type #203

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

Merged
merged 4 commits into from
Jun 26, 2025

Conversation

luqmana
Copy link
Contributor

@luqmana luqmana commented May 27, 2025

This adds a new service oxide/net-setup which ensures we have an IPv6 link-local address for the NICs corresponding to each instance of the service. Each instance is named after the corresponding NIC driver (e.g., e1000g, igb, cxgbe).

@luqmana luqmana requested review from jclulow and citrus-it May 27, 2025 21:27
Copy link
Contributor

@citrus-it citrus-it left a comment

Choose a reason for hiding this comment

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

This looks like a much better direction, thanks for this.
Just one minor comment from me, I don't know enough about how the compliance/mfg bits get used to approve but those parts look reasonable.

@luqmana luqmana force-pushed the compliance-net-setup branch from be85579 to 75396a4 Compare May 28, 2025 18:33
Copy link
Collaborator

@jclulow jclulow left a comment

Choose a reason for hiding this comment

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

In general I think anything that isn't specifically related to compliance should have any mention of compliance scrubbed out. We ship the NIC configuration stuff in essentially every image, so I think making it an oxide/ prefix on the FMRI, and removing any mention of compliance, would make it easier to understand the scope.

@luqmana luqmana changed the title Separate T6 and (optional) K.2 NIC setup for compliance images. Add separate oxide/net-setup service to ensure we come up with basic networking on all images. Jun 9, 2025
@luqmana luqmana force-pushed the compliance-net-setup branch 2 times, most recently from c33b717 to 091c1e3 Compare June 10, 2025 23:05
@luqmana luqmana force-pushed the compliance-net-setup branch from 091c1e3 to fa5e12d Compare June 10, 2025 23:08
@citrus-it citrus-it requested review from jclulow and citrus-it June 24, 2025 16:51
@luqmana
Copy link
Contributor Author

luqmana commented Jun 26, 2025

In addition to the adhoc cosmo testing, I pinned an omicron branch to this helios commit and let it generate a TUF repo which I flashed onto a gimlet and things come up properly. The attached igb0 gets an addrconf iface without getting blocked on the t6 service.

@jclulow jclulow changed the title Add separate oxide/net-setup service to ensure we come up with basic networking on all images. image: separate IPv6 address configuration by NIC type Jun 26, 2025
Copy link
Collaborator

@jclulow jclulow left a comment

Choose a reason for hiding this comment

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

Thanks for the changes, and the testing notes! LGTM.

@luqmana luqmana merged commit 7e35d03 into master Jun 26, 2025
@luqmana luqmana deleted the compliance-net-setup branch June 26, 2025 15:39
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