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

multipath: add automatic configuration for multipath #780

Merged
merged 1 commit into from Apr 3, 2020

Conversation

darkmuggle
Copy link
Contributor

Add support for 'rd.multipath=default' for using the default
configuration on boot. The intended purpose for this is to help support
ostree-based image boots from multipathed devices (such as Fedora and
Red Hat CoreOS).

Add support for 'rd.multipath=default' for using the default
configuration on boot. The intended purpose for this is to help support
ostree-based image boots from multipathed devices (such as Fedora and
Red Hat CoreOS).
@centos-ci
Copy link
Collaborator

Can one of the admins verify this patch?

@darkmuggle
Copy link
Contributor Author

For background, on RHCOS is part of OpenShift. The user generally does not configure the system in the classic way. Further the initramfs is distributed as part of the RHCOS OStree. By having a kernel flag for rd.multipath=default the user would have the ability to use the default pathing configuration.

Description=Device-Mapper Multipath Default Configuration
Before=iscsi.service iscsid.service lvm2-activation-early.service
Wants=systemd-udev-trigger.service systemd-udev-settle.service local-fs-pre.target
After=systemd-udev-trigger.service systemd-udev-settle.service
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Are the deps on systemd-udev-*.service really needed? AFAICS mpathconf --enable doesn't access any HW; it just writes a config. file...

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.

None yet

4 participants