OEM / provider support of OpenNebula
Nobody has claimed this yet.
- Dominant language
- Go
- Stars
- 974
- Forks
- 296
- Avg merge
- 6d 14h
- Merged PRs (30d)
- 9
Description
Feature Request
Currently it is not possible to run CoreOS (using Ignition) on OpenNebula.
It would be nice to have support for this open source cloud platform.
Environment
OpenNebula currently uses a config drive (called CONTEXT and available to the VM as CD drive like /dev/cdrom).
On this CONTEXT disk there usually only exists one file: context.sh This file contains possibly multiline (environment) variables in the format KEY='VALUE'.
On OpenNebulas side one could implement a mechanism to provide a config.ign file on that CONTEXT drive.
Desired Feature
Ignition should be able to access OpenNebulas CONTEXT drive (available on /dev/cdrom) and then read that config.ign file.
Ideally Ignition should even work just with the context.sh file which contains variables like ETH0_IP and use these to configure its own networking.
Contributor guide
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
No source file or test is named. Start by locating how Ignition discovers and reads config drives, then assess support for OpenNebula's /dev/cdrom CONTEXT and its config.ign or context.sh formats. Done means the agreed OpenNebula input is read during first boot, with the scope of context.sh support explicitly settled.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- go
- Domain
- cloud
- Issue type
- Feature
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 30/100