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

Aperta
#791 0 commenti 0 reazioni 0 assegnatari Vedi su GitHub

I maintainer di solito rispondono entro 1 giorno

Nessuno ha ancora preso questa issue.

Valutazione

Difficoltà
3/5
Tempo stimato
1-2 giorni
Idoneità per principianti
30/100
Tipo di issue
Refactoring
Chiarezza
Abbastanza chiara
Stato di attività
Attiva
Stack tecnologico
azure

Direzione di ricerca

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.

Scritto dal modello di indicizzazione a partire dal testo della issue.

Descrizione

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

Lingua principale
Ruby
Stelle
52
Fork
124
Merge medio
1g 2h
PR unite (30g)
23

Preparare l'ambiente

Come iniziare

  1. Leggi tutta la issue e poi la guida ai contributi del progetto.
  2. Commenta sulla issue per dire che te ne occupi tu — evita che due persone facciano lo stesso lavoro.
  3. Fai un fork del repository e lavora su un branch.
  4. Apri una pull request che faccia riferimento al numero della issue.

Altre issue di cloudfoundry/bosh-linux-stemcell-builder

Tutte le issue di cloudfoundry/bosh-linux-stemcell-builder

Issue simili

Altre issue su Ruby

Ricevi le nuove issue nella tua casella

Un breve riepilogo di issue GitHub adatte ai principianti.