Skip to content

feat: Allow bypassing init-local stage if not needed - #7015

Open
rajibade wants to merge 1 commit into
canonical:mainfrom
rajibade:init-local-option
Open

feat: Allow bypassing init-local stage if not needed#7015
rajibade wants to merge 1 commit into
canonical:mainfrom
rajibade:init-local-option

Conversation

@rajibade

Copy link
Copy Markdown

Proposed Commit Message

Allow the init-local stage to be skipped for configurations that do not need it.

Some images configure a list with network-only datasources. For these images, the init-local stage
just occupies the critical path and doesn't configure anything. Since moving to the single process
optimisation, the socket sync makes skipping it difficult. This adds a check for an opt-in marker at 
`/etc/cloud/cloud-init-local.disabled` just for disabling this stage. Default behaviour unchanged.

Additional Context

This is primarily done testing with amazon linux on EC2, since it uses ec2-net-utils in its network
management but I think it has general use too. Happy to hear alternatives or revisions.

Test Steps

Merge type

  • Squash merge using "Proposed Commit Message"
  • Rebase and merge unique commits. Requires commit messages per-commit each referencing the pull request number (#<PR_NUM>)

Allow the init-local stage to be skipped for configurations that do not
need it.

Since moving to the single process route, this process is always
implicitly run especially which can slow down some platforms that use
the instance metadata service configurer (e.g ec2-net-utils) to before
network bring up.
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant