Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Configuration driven from cloud-init style yaml files #4

Closed
mudler opened this issue Jan 8, 2021 · 1 comment
Closed

Configuration driven from cloud-init style yaml files #4

mudler opened this issue Jan 8, 2021 · 1 comment
Assignees
Labels
kind/enhancement New feature or request
Projects

Comments

@mudler
Copy link
Contributor

mudler commented Jan 8, 2021

/etc should be configured on boot driven by extensible cloud-init style yaml files.

Similarly, users can drop config files into the /oem ( or /usr/local/oem ) or /usr/local/setup folder to achieve persistent configurations. The cloud-init format should allow extensions too.

A default config should be among the lines of : https://github.com/rancher/k3os/blob/1688b718da51b39d48c17e2a20d453f37f3d58c7/overlay/libexec/k3os/boot

This issue is about finding a tool that accomplishes that, and embed it into the various stages of the OS (at least): initramfs, boot, network. Replacing also the current skel package that does handle /etc setup.

Ideally, the tool that mimic cloud-init shouldn't have dependency, and be portable (possibly written in Go) see for e.g.:

See also https://github.com/mocaccinoOS/os-commons/tree/master/packages/systemd/yip-systemd for a possible integration with systemd boot

@mudler mudler changed the title Boot setup from cloud-init stile yaml files Boot setup from cloud-init style yaml files Jan 8, 2021
@mudler mudler added this to Untriaged in Releases Jan 12, 2021
@mudler mudler changed the title Boot setup from cloud-init style yaml files Configuration driven from cloud-init style yaml files Jan 15, 2021
@mudler mudler moved this from Untriaged to To Do in Releases Jan 15, 2021
@mudler mudler mentioned this issue Jan 28, 2021
8 tasks
@mudler mudler self-assigned this Jan 29, 2021
@mudler mudler moved this from To Do to In Progress in Releases Jan 29, 2021
@mudler mudler added the kind/enhancement New feature or request label Jan 29, 2021
mudler added a commit that referenced this issue Jan 29, 2021
mudler added a commit that referenced this issue Jan 29, 2021
mudler added a commit that referenced this issue Jan 29, 2021
mudler added a commit that referenced this issue Feb 2, 2021
mudler added a commit that referenced this issue Feb 2, 2021
Related to #4
mudler added a commit that referenced this issue Feb 2, 2021
mudler added a commit that referenced this issue Feb 4, 2021
Also drop finalizer from cos-config, not required anymore

See #4
@mudler
Copy link
Contributor Author

mudler commented Feb 9, 2021

Closing this as we have a cloud-config mechanism, for the /oem setup, we will have a follow-up (in #24) as there is no decision yet if that has to be in the persistent area or not

@mudler mudler closed this as completed Feb 9, 2021
Releases automation moved this from In Progress to Done Feb 9, 2021
frelon pushed a commit to frelon/elemental-toolkit that referenced this issue May 12, 2023
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
kind/enhancement New feature or request
Projects
No open projects
Releases
✅ Done
Development

No branches or pull requests

1 participant