Investigate making cloud-init → BOSH-agent network handoff explicit via service ordering (Azure)

未关闭
#791 0 条评论 0 个 reaction 已指派 0 人 在 GitHub 查看

维护者通常 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.service to bosh-agent.service is 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

环境准备

从这里开始

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

cloudfoundry/bosh-linux-stemcell-builder 的其他 Issue

查看 cloudfoundry/bosh-linux-stemcell-builder 的全部 Issue

相似的 Issue

更多 Ruby Issue

把新 issue 发到你的邮箱

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