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

feat: add Longhorn V2 provisioner (backport #129) #133

Merged
merged 3 commits into from
Sep 13, 2024

Conversation

tserong
Copy link
Contributor

@tserong tserong commented Sep 13, 2024

Manual backport because mergify and/or github got very confused (see comments in #132)

Signed-off-by: Tim Serong <tserong@suse.com>
(cherry picked from commit 9e0fb40)
Signed-off-by: Tim Serong <tserong@suse.com>
(cherry picked from commit 58b42e7)
This allows adding extra disks for use by Longhorn's V2 data engine.
I've implemented this as a separate LonghornV2Provisioner for the
sake of neatness, rather than grafting it into LonghornV1Provisioner
with a bunch of `if` statements, but some of the implementation
(the UnProvision() and Update() functions) still call back to the
LonghornV1Provisioner to avoid excessive code duplication.

The current implementation theoretically supports using virtio disks,
except that NDM as a whole ignores those, as they don't have WWNs.
This is something we need to address separately as part of
harvester/harvester#6034

Related issue: harvester/harvester#5274

Signed-off-by: Tim Serong <tserong@suse.com>
(cherry picked from commit 83b58dd)
Copy link
Collaborator

@Vicente-Cheng Vicente-Cheng left a comment

Choose a reason for hiding this comment

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

LGTM, let's wait for the CI

@Vicente-Cheng Vicente-Cheng merged commit d8c4ad3 into harvester:v0.7.x Sep 13, 2024
5 checks passed
@tserong tserong deleted the wip-backport-129 branch September 13, 2024 07:31
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.

3 participants