Add sugar for kdump configuration
Open
Nobody has claimed this yet.
butane
- Dominant language
- Go
- Stars
- 974
- Forks
- 296
- Avg merge
- 6d 14h
- Merged PRs (30d)
- 9
Description
Created originally in Butane by @travier: https://github.com/coreos/butane/issues/175
What are the configuration options for kdump?
Enabling kdump on FCOS (& RHCOS) requires:
- setting a kernel argument (for example:
crashkernel=256M) which has a default suggested value; - setting options in
/etc/kdump.confto configure where the coredump will be stored; - setting options in
/etc/sysconfig/kdumpto configure additional kernel arguments passed to the "dump" kernel instance. - enabling the
kdump.serviceunit.
What would the sugar looks like?
From https://github.com/coreos/fedora-coreos-tracker/issues/622#issuecomment-694225598:
kdump:
crashkernel: 128M
kargs: foo=bar
config: |
net penguin.example.com:/export/cores
References
- RHEL 8 documentation for examples.
- See also initial discussion in https://github.com/coreos/fedora-coreos-tracker/issues/622.
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 file or test is named. Start by reading the requested YAML shape, the Butane migration issue, and the linked FCOS discussion; determine how crashkernel, kargs, /etc/kdump.conf, /etc/sysconfig/kdump, and kdump.service should be represented. Done means the proposed kdump configuration is supported with documented behavior and coverage for its options.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- go, linux
- Domain
- operating-systems
- Issue type
- Feature
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Quiet
- Clarity
- Mostly clear
- Newbie friendliness
- 45/100