DHCP Configuration concept

未关闭
  • 哪里不对？
#68 2 条评论 0 个 reaction 已指派 0 人 在 GitHub 查看

还没有人认领这个 Issue。

评估

难度
5/5
预计耗时
一周以上
新手友好度
25/100
Issue 类型
功能
描述清晰度
基本清楚
活跃度
停滞
技术栈
grpc
领域
api, backend-api-design, networking

调研方向

先阅读 RFC 2132、RFC 3004 和 RFC 3442，然后审查现有的 ironcore(-net)、metalnet 和 dpservice GRPC API 方案。在两个 API 层定义所选的 DHCP 选项、API 概念以及向后兼容行为。完成的标准是在不实现该功能的情况下，记录 networking 和 ironcore-api 的验收标准。

由索引模型根据 Issue 内容生成。

描述

area/iaas area/networking

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
主要语言
Shell
星标
1
派生
1
30 天内没有已合并 PR

环境准备

这个项目没有提供开发容器、Dockerfile 或贡献指南，环境需要你自己搭建：先看它的 README，通用步骤见我们的新手贡献指南。

从这里开始

  1. 先读完整个 Issue，再读项目的贡献指南。
  2. 在 Issue 下留言说明你要接手 —— 这能避免两个人做同样的事。
  3. Fork 仓库，在一个分支上完成修改。
  4. 提交 Pull Request，并在描述里引用这个 Issue 编号。

ironcore-dev/roadmap 的其他 Issue

查看 ironcore-dev/roadmap 的全部 Issue

相似的 Issue

更多 Shell/Bash Issue

把新 issue 发到你的邮箱

精选适合新手参与的 GitHub issue 摘要。