LVM support
Nobody has claimed this yet.
- Dominant language
- Go
- Stars
- 974
- Forks
- 296
- Avg merge
- 6d 14h
- Merged PRs (30d)
- 9
Description
For provisioning OpenShift worker nodes on bare-metal that will also host Ceph storage, it would be nice to be able to configure Logical Volume Management via Ignition.
This would be in support of servers with multiple SSDs installed.
The implementation might be able to borrow from the methods used by Anaconda Kickstart:
For example:
part pv.1 --fstype="lvmpv" --ondisk=${disk1} --size=1024 --grow --maxsize=2000000
part pv.2 --fstype="lvmpv" --ondisk=${disk2} --size=1024 --grow --maxsize=2000000
volgroup centos --pesize=4096 pv.1 pv.2
...
logvol swap --fstype="swap" --size=16064 --name=swap --vgname=centos
logvol / --fstype="xfs" --grow --maxsize=2000000 --size=1024 --name=root --vgname=centos
...
etc...
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
The issue names no files, tests, or entry points. Start by reviewing Ignition's existing storage configuration and comparing it with the Anaconda Kickstart example, focusing on physical volumes, volume groups, and logical volumes across multiple SSDs. Done should mean that OpenShift bare-metal worker nodes can configure the requested LVM layout through Ignition.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- go
- Domain
- infrastructure, operating-systems
- Issue type
- Feature
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 25/100