Skip to content

Conversation

@jgallagher
Copy link
Contributor

@jgallagher jgallagher commented Oct 27, 2025

This is built on top of #9250, and is related to both #9238 and #8949:

  • Trims down some of the BlueprintResourceAllocator internals
  • Adds an explicit ExternalIpPolicy type; today it holds a couple of IP pools and a set of external DNS IPs, but it gives us a cleaner place to integrate all the IP pool work that @bnaecker is doing with Reconfigurator

Since we don't actually have external DNS IPs in a policy anywhere, this adds DataStore::external_dns_external_ips_specified_by_rack_setup() (which is implemented as "load the current target blueprint and scan it for external DNS zones"; i.e., exactly what the builder was doing before). We should eventually delete this method once it's possible for an operator to reconfigure the external DNS IPs, but this lets the planning input build up the policy as though we already had this information available, more or less. Other than that new method, almost all the changes in this PR are to tests; the non-test changes are pretty minimal.

// This can't be `#[cfg(test)]` because it's used by the `ExampleSystem`
// helper (which itself is used by reconfigurator-cli and friends). We give
// it a scary name instead.
pub(crate) fn inject_untracked_external_dns_ip(
Copy link
Contributor

Choose a reason for hiding this comment

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

🎉

Copy link
Collaborator

@bnaecker bnaecker left a comment

Choose a reason for hiding this comment

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

This is a solid cleanup. I have a few questions, but they're mostly small. I like where we're going on this.

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.

4 participants