DHCP Configuration concept

Summary

Currently DHCP(v6) configuration possibilities like DNS Server IP, hostname, DNS search domain, FQDN, NTP Server Ip etc.
are not all offered and the ones which are offered are not centrally configurable by the ironcore API user.
There is a need to identify an unified way of handling DHCP related configurations/settings effecting the created
ironcore VMs and Metal Machines.

---

Scope

✅ In Scope

• Research the relevant RFCs like RFC 2132, 3004, 3442 for DHCPv4 and DHCPv6 to determine the configurations which can be offered
  to ironcore API users.
• Define a concept together with ironcore API. Define the ironcore(-net) / metalnet layer API. Define possible dpservice GRPC changes.
• Make sure that the new concept is backward compatible with the current approach that is being used.

❌ Out of Scope

• Full Coverage of All Possible DHCP Options: Only a subset of DHCP options relevant to ironcore VM and metal machine provisioning will be considered. Full support for the entire range of options defined in the RFCs is not targeted.
• Implementation is not part of this work.

---

Responsible Areas

• Networking
• ironcore-api

---

Contributors

• @afritzler
• @guvenc
• @byteocean
• @MalteJ

---

Acceptance Criteria

• Networking

  • A clear concept on metalnet and dpservice GRPC API level defined.
  • Each needed DHCP option is reflected on low level API.
  • Backward compatibility on metalnet / dpservice level defined.

• ironcore-api

  • A clear concept on ironcore(-net) API level defined.
  • Each needed DHCP option is identified.
  • Backward compatibility on ironcore(-net) defined.

---

Action Items

• Assign labels (e.g., area/ironcore-api, kind/design)
• Set milestone (e.g., H1/2025)
• Assign dependent sub-issues in each required area
• Assign an owner to the issue using the GitHub "Assignee" field
• List all contributors in the "Contributors" section above
• Add this issue to the Roadmap project board

Start by reading RFC 2132, RFC 3004, and RFC 3442, then review the existing ironcore(-net), metalnet, and dpservice GRPC API approaches. Define the selected DHCP options, API concepts, and backward-compatibility behavior at both API layers. Done means the networking and ironcore-api acceptance criteria are documented without implementing the feature.