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

va: Make the primary VA aware of the Perspective and RIR of each remote #7839

Merged
merged 4 commits into from
Nov 25, 2024

Conversation

beautifulentropy
Copy link
Member

@beautifulentropy beautifulentropy commented Nov 21, 2024

  • Make the primary VA aware of the expected Perspective and RIR of each remote VA.
  • All Perspectives should be unique, have the primary VA check for duplicate Perspectives at startup.
  • Update test setup functions to ensure that each remote VA client and corresponding inmem impl have a matching perspective and RIR.

Part of #7819


Updated IN-10231 and created IN-10840.

@beautifulentropy beautifulentropy force-pushed the trust-but-verify branch 3 times, most recently from a68fa53 to 0d9ba2a Compare November 21, 2024 23:19
@beautifulentropy beautifulentropy changed the title WIP va/remoteva: Validate that perspectives are unique and remain consistent Nov 21, 2024
@beautifulentropy beautifulentropy changed the title va/remoteva: Validate that perspectives are unique and remain consistent va: Validate that perspectives are unique and remain consistent Nov 21, 2024
@beautifulentropy beautifulentropy changed the title va: Validate that perspectives are unique and remain consistent va: Ensure perspectives are unique and remain consistent Nov 21, 2024
Copy link
Contributor

@beautifulentropy, this PR appears to contain configuration and/or SQL schema changes. Please ensure that a corresponding deployment ticket has been filed with the new values.

va/va.go Outdated Show resolved Hide resolved
@beautifulentropy beautifulentropy changed the title va: Ensure perspectives are unique and remain consistent va: Make the primary VA aware of the Perspective and RIR of each remote Nov 22, 2024
Copy link
Contributor

@aarongable aarongable left a comment

Choose a reason for hiding this comment

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

Love the va_test cleanup. LGTM with nits.

test/config-next/remoteva-a.json Show resolved Hide resolved
cmd/config.go Outdated Show resolved Hide resolved
va/va_test.go Outdated Show resolved Hide resolved
// ServerAddress, DNSAuthority, [Timeout], [HostOverride]
// SRVLookup, DNSAuthority, [Timeout], [HostOverride], [SRVResolver]
// SRVLookups, DNSAuthority, [Timeout], [HostOverride], [SRVResolver]
type RemoteVAGRPCClientConfig struct {
Copy link
Contributor

Choose a reason for hiding this comment

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

Technically I don't think this type has to be Exported anymore -- only its fields have to be public for parsing.

@beautifulentropy beautifulentropy merged commit c394831 into main Nov 25, 2024
14 checks passed
@beautifulentropy beautifulentropy deleted the trust-but-verify branch November 25, 2024 18:02
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