-
Notifications
You must be signed in to change notification settings - Fork 500
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
use mdadm instead of LVM if it is available #789
use mdadm instead of LVM if it is available #789
Conversation
devs=$(echo "$ssd_mounts" | awk '{print $2}') | ||
raid_dev=/dev/md0 | ||
|
||
# If RAID or LVM is already in use, this may have been re-deployed. |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
When USE_LVM
is changed from 1
to 0
, will combined disks with mdadm be wiped?
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
The disks would never be wiped again if the write to /var/dev_wiped/
is persisted. But this comment is to indicate that if we detect an existing LVM or RAID setup then don't go down this path where we wipe the disks.
The design of the script is that it to detect if it already ran and to never change what it has already done. So if you change to USE_LVM=1 that will effectively be ignored if the raid device has already been created.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
LGTM
/run-e2e-tests |
/run-e2e-tests |
1 similar comment
/run-e2e-tests |
local-volume-provisioner for GKE. Use mdadm in preference to LVM. Initial tests indicate this may perform better. This only works on Ubuntu. COS for GKE 1.14 is suppose to support RAID, but the mdadm binary is not there yet.
This has been tested on GKE to work on both COS and Ubuntu.