-
Notifications
You must be signed in to change notification settings - Fork 2
[multicast] Narrow to admin-local Omicron underlay & match Omicron updates to mcast lifecycle #162
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
base: main
Are you sure you want to change the base?
Conversation
This PR is a precursor to a follow-up PR that leverages updated code in `omicron-common`. This gets dendrite in line with Omicron `main`, capturing an upstream type change that we needed to accomodate.
Previously, internal multicast groups accepted admin-scoped addresses
including admin-local (ff04), site-local (ff05), and org-local (ff08).
This narrows the scope to only admin-local (ff04::/16), which is what
Omicron *now* dictates.
- [ ] This should be merged after
oxidecomputer/omicron#9450 is reviewed
and merged into Omicron. We now make Dendrite/Dpd match Omicron
consistently for validation.
Key changes:
- Remove IPV6_SITE_LOCAL_PATTERN and IPV6_ORG_SCOPE_PATTERN from P4
- Update P4 table entries to only match admin-local (size 4→2)
- Add ADMIN_LOCAL_PREFIX const to dpd-types with RFC doc links
- Update validation to use `is_admin_local_multicast()` from oxnet v0.1.4
- Bump to API version 2 for doc changes (only)
- Update README with OpenAPI generation instructions
- Use new multicast subnet constants from `omicron-common` for validation
6f00b19 to
94e91ca
Compare
|
@rcgoodfellow updated for your review. |
FelixMcFelix
left a comment
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.
Thanks Zeeshan, the updates to the allowed IP families all make sense. Just some questions on the expanded comments on the decapsualtion bitmaps in the dataplane.
Yep. No questions, just my bad in context. Fixed. |
FelixMcFelix
left a comment
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.
Thanks for fixing up those comments!
|
@rcgoodfellow, let me know if you'd like another look at this. I'll be doing a follow-up PR as well on some ssm/asm updates. |
| // | ||
| // Copyright 2025 Oxide Computer Company | ||
|
|
||
| // Port Bitmap Check Table |
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.
Thanks for adding this.
This diffset handles our move toward ASM groups being able to have source IPs. Includes: - Replace IpSrc::Subnet with IpSrc::Any for any-source multicast filtering - Add source filter normalization: when Any is present, collapse to single /0 entry; empty sources treated as allow-any - API versioning - Add tag ownership validation for group updates and deletes (v4 API) - Add v2/v3 API version adapters for backward compatibility - Fix test_service_ipv4_unknown_address to set NAT-only on correct port - #172 - I had to fix this here, as it was failing consistently locally.
|
|
||
| # Workaround for omicron's bootstore transitive dependency on pq-sys | ||
| [env] | ||
| DEP_PQ_LIBDIRS = "1" |
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.
Sadly, this is now always necessary, having updated to a new Omicron commit. It's on maghemite too: https://github.com/oxidecomputer/maghemite/blob/main/.cargo/config.toml#L13.
…specification
Multicast groups now require tag-based validation for mutations (delete/update)
in API v4 (current). Tags are assigned at creation (user-provided or
auto-generated as `{uuid}:{group_ip}`) and are immutable. This prevents
accidental modification or deletion of groups associated with other components,
and better works with Omicron's retry model.
This commit also addresses several issues with this branch's multicast API
versioning scheme, including restructuring versions on this branch to
follow this ordering:
- v4 = TAG_OWNERSHIP: required tags for delete/update as query params, IpSrc::Any
- v3 = SOURCE_FILTER_ANY: optional tags, IpSrc::Any
- (MCAST_DOCS_ADMIN_LOCAL was removed)
- v2 = DUAL_STACK_NAT_WORKFLOW: optional tags, IpSrc::Subnet
- v1 = INITIAL
API version 4 changes:
- DELETE requires tag query parameter that must match the group's tag
- PUT validates that the provided tag matches the existing group's tag
- All response types have `tag: String` (always present, never null)
Backward compatibility (v1-v3):
- DELETE does not require tag (handler looks up existing tag internally)
- PUT tag is optional; if omitted, existing tag is preserved
- Response types have `tag: Option<String>` for v3, converted from v4
Tag format: 1-80 ASCII bytes, alphanumeric plus hyphens, underscores,
colons, and periods. Constraint matches Omicron's database schema
(post-update there).
6b8ba63 to
a253044
Compare
|
@FelixMcFelix @rcgoodfellow I had to rework the API mgmt here, but this is now ready for another look. |
|
PR description updated btw to capture everything here. |
…4::/16
As per Omicron, customers can use admin-local IPv6 multicast addresses
(ff04::/16) for external groups, except for the reserved underlay subnet
(ff04::/64) which is used for internal underlay multicast allocation.
Changes:
- switch external-group validation from validate_not_admin_local_ipv6()
to validate_not_underlay_subnet()
- validate_not_underlay_subnet() now only rejects ff04::/64
- validate_nat_target() now requires NAT IPs in UNDERLAY_MULTICAST_SUBNET
- VLAN tagging logic uses UNDERLAY_MULTICAST_SUBNET,
removed dead is_unique_local() check (multicast IPs can't be ULA)
- removed unused IPV6_SCOPE_MASK, IPV6_ULA_MASK/PATTERN from P4
- removed dead ULA entry from mcast_tag_check table (const size = 1)
- Updated integration test assertions, added unit tests
API v4 (MCAST_STRICT_UNDERLAY) changes:
- Renamed AdminScopedIpv6 to UnderlayMulticastIpv6 to better reflect its
purpose as the underlay multicast subnet type
- Tightened validation from ff04::/16 (admin-local scope) to ff04::/64
to match Omicron's UNDERLAY_MULTICAST_SUBNET allocation
- Tag validation now required for update/delete operations (as before)
API v3 backward compatibility:
- Added v3::AdminScopedIpv6 type that accepts the broader ff04::/16 range
- v3 endpoints use v3::MulticastUnderlayGroupIpParam and convert to the
v4 type with appropriate error handling for out-of-range addresses
…ion via dropshot Path try_map Includes: - delegate a versioned endpoint in lib.rs from api-server.rs - Cargo.lock updated for new dropshot/omicron
This PR aligns with the implicit lifecycle work that was recently merged into Omicron: oxidecomputer/omicron#9450.
Previously, internal/underlay multicast groups accepted admin-configured addresses, including admin-local (
ff04), site-local (ff05), and org-local (ff08). This narrows the scope to only admin-local (ff04::/16), with ff04::/64 reserved for Omicron's internal underlay allocation.The first set of key changes included:
After the Omicron work finally landed, which this PR relied on, we also addressed ASM groups with sources and explicit tagging:
ASM source filtering: Source filters are now allowed on ASM addresses (previously SSM-only). IpSrc::Subnet was replaced with IpSrc::Any for any-source matching.
P4 source filter changes: The source filter tables changed from exact to lpm matching on IPv6, and the multicast check was broadened from SSM-only ranges (232.0.0.0/8, ff3x::/16) to all multicast (224.0.0.0/4, ff00::/8).
Tag ownership: Multicast groups now require tag-based validation for mutations (delete/update) in API v4 (current). Tags are assigned at creation (user-provided or auto-generated as {uuid}:{group_ip}). Tags cannot be changed post-creation and must match for mutations; this is enforced by requiring the existing tag, not by rejecting tag-change requests. This prevents accidental modification or deletion of groups associated with other components, and better works with Omicron's retry model.
The API structure is now modeled as:
underlay subnet restricted to ff04::/64 (not all of ff04::/16)