Investigate making cloud-init → BOSH-agent network handoff explicit via service ordering (Azure)
维护者通常 1 天内回复
还没有人认领这个 Issue。
评估
- 难度
- 3/5
- 预计耗时
- 1-2 天
- 新手友好度
- 30/100
- Issue 类型
- 重构
- 描述清晰度
- 基本清楚
- 活跃度
- 活跃
- 技术栈
- azure
调研方向
Start with the unit file stemcell_builder/stages/bosh_go_agent/assets/bosh-agent.service, which currently has only After=network.target, and compare it with the Azure firstboot blocker at stemcell_builder/stages/system_azure_init/assets/etc/systemd/system/cloud-config.service.d/firstboot-blocker.conf. Work out whether ordering after cloud-final.service is safe on stemcells without cloud-init, which the issue asks about. Done means a documented ordering decision with the reasoning, and ideally a boot check on an Azure stemcell.
由索引模型根据 Issue 内容生成。
描述
PR cloudfoundry/bosh-agent#495 fixed an Azure-specific file-ordering collision between cloud-init/netplan's networkd profile and bosh-agent's profile by prefixing the BOSH file with 09-. During review, @s4heid suggested investigating whether the ownership contract between cloud-init and bosh-agent should be made more explicit in the service startup order.
Area for investigation
The current bosh-agent.service unit only declares After=network.target. There is no explicit dependency that ensures cloud-init has fully completed before bosh-agent applies its network configuration. If cloud-init runs again after bosh-agent (e.g. on certain Azure VM events), it could overwrite the networkd state bosh-agent set up.
bosh-agent.service lives at: stemcell_builder/stages/bosh_go_agent/assets/bosh-agent.service
The Azure init stage already uses a similar pattern for blocking cloud-config: stemcell_builder/stages/system_azure_init/assets/etc/systemd/system/cloud-config.service.d/firstboot-blocker.conf
It is worth investigating:
- Whether adding
After=cloud-final.servicetobosh-agent.serviceis safe and sufficient, or whether stronger constraints are needed. - What the impact would be on IaaS providers where cloud-init is absent.
- Whether this interacts with the existing firstboot-blocker mechanism on Azure.
Related to: https://github.com/cloudfoundry/bosh-agent/issues/500
- 主要语言
- Ruby
- 星标
- 52
- 派生
- 124
- 平均合并
- 1 天 2 小时
- 30 天内合并 PR
- 23
环境准备
- 没有 Dockerfile 或 Docker Compose 文件
- 有 Pull Request 模板
- 阅读贡献指南
从这里开始
- 先读完整个 Issue,再读项目的贡献指南。
- 在 Issue 下留言说明你要接手 —— 这能避免两个人做同样的事。
- Fork 仓库,在一个分支上完成修改。
- 提交 Pull Request,并在描述里引用这个 Issue 编号。
cloudfoundry/bosh-linux-stemcell-builder 的其他 Issue
-
难度 2/5 1-3 小时 新手友好度 68/100
cloudfoundry/bosh-linux-stemcell-builder#802 ·
维护者通常 1 天内回复
-
Pin and verify tools in the OS image stemcell builder可能已有人在做 @vighes 于 3 天前认领。 未关闭
难度 4/5 3-5 天 新手友好度 35/100
cloudfoundry/bosh-linux-stemcell-builder#806 · 2 条评论 ·
维护者通常 1 天内回复
-
难度 3/5 1-2 天 新手友好度 35/100
cloudfoundry/bosh-linux-stemcell-builder#803 ·
维护者通常 1 天内回复
-
难度 5/5 一周以上 新手友好度 25/100
cloudfoundry/bosh-linux-stemcell-builder#738 · 1 条评论 ·
维护者通常 1 天内回复
-
难度 5/5 一周以上 新手友好度 35/100
cloudfoundry/bosh-linux-stemcell-builder#676 · 4 条评论 · 1 个 reaction ·
维护者通常 1 天内回复
查看 cloudfoundry/bosh-linux-stemcell-builder 的全部 Issue
相似的 Issue
-
Bug Ruby
难度 2/5 1-3 小时 新手友好度 76/100
getsentry/sentry-ruby#3211 · 1 条评论 ·
维护者通常 2 天内回复
-
enhancement
难度 2/5 1-3 小时 新手友好度 66/100
internetee/registry#2984 ·
维护者通常 6 天内回复
-
难度 2/5 1-3 小时 新手友好度 82/100
ecosyste-ms/issues#862 ·
维护者通常 1 天内回复
-
Redis Lua error `@user_script:52: ERR value is not an integer or out of range` when `window_size` is configured可能已有人在做 @mimosa 今天认领。 未关闭bug
难度 2/5 1-3 小时 新手友好度 82/100
维护者通常 1 天内回复
-
难度 2/5 1-3 小时 新手友好度 67/100
riscv/riscv-unified-db#2829 ·
维护者通常 1 天内回复