MPIC: both primary and remote should know about perspectives #7819
Assignees
Milestone
Comments
This was referenced Nov 21, 2024
beautifulentropy
added a commit
that referenced
this issue
Nov 25, 2024
…te (#7839) - 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
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Discussed in #7817 (comment) and at standup.
It's useful for the the primary VA to know what its backend perspectives are. It can check at startup that all its perspectives are distinct. And it can log errors by perspective even when those errors are due to a perspective being down.
However, there's a risk that the primary VA could be configured wrong: it could think a given backend is perspective A, when actually it's perspective B. In fact, a given SRV record could mistakenly resolve to a pool of backends with some in perspective A and some in perspective B!
We can add some double-checking here. We should have the primary know which perspective each of its backends is in, and assert that in each RPC. The backends (remotes) should also know what perspective it considers itself to be in. They can check the asserted perspective against the locally configured perspective, and return an error if there is a mismatch.
The text was updated successfully, but these errors were encountered: