github-starred/zfs-ha
2
0
Fork 0
mirror of https://github.com/ewwhite/zfs-ha.git synced 2026-05-15 22:05:04 -06:00
Code Issues 11 Projects Packages Wiki Activity Actions

[GH-ISSUE #30] Proxmox and zfs-ha #29

New issue
Closed
opened 2026-05-05 03:31:33 -06:00 by gitea-mirror · 1 comment
gitea-mirror commented 2026-05-05 03:31:33 -06:00
Owner
Copy link

Originally created by @Crow-Control on GitHub (Sep 25, 2019).
Original GitHub issue: https://github.com/ewwhite/zfs-ha/issues/30

Considering the used technologies, this seems to be almost made to be used with Proxmox.

Has anyone tried it with proxmox instead of redhat?
What changes need to be done to get it running in such a way that it doesn't fuck with proxmox default config? (aka break on update is not chill).

edit
Somethings i'm not sure about:

  1. If there are non-storage nodes in the cluster, how would it differentiate between those?
  2. Depending on the answer on 1, quorum would be "okey" I guess. As one would have at least 3 nodes (one hosting VM's and 2 storage nodes connected to JBOD)
Originally created by @Crow-Control on GitHub (Sep 25, 2019). Original GitHub issue: https://github.com/ewwhite/zfs-ha/issues/30 Considering the used technologies, this seems to be almost made to be used with Proxmox. Has anyone tried it with proxmox instead of redhat? What changes need to be done to get it running in such a way that it doesn't fuck with proxmox default config? (aka break on update is not chill). *edit* Somethings i'm not sure about: 1. If there are non-storage nodes in the cluster, how would it differentiate between those? 2. Depending on the answer on 1, quorum would be "okey" I guess. As one would have at least 3 nodes (one hosting VM's and 2 storage nodes connected to JBOD)
gitea-mirror commented 2026-05-05 03:31:40 -06:00
Author
Owner
Copy link

@wmantly commented on GitHub (Nov 25, 2019):

Why did you close this? Do you know something?

<!-- gh-comment-id:557988947 --> @wmantly commented on GitHub (Nov 25, 2019): Why did you close this? Do you know something?
Sign in to join this conversation.
No Branch/Tag specified
Branches Tags
master
No results found.
Labels
Clear labels   
pull-request

Mirrored from GitHub Pull Request

No labels
pull-request
Milestone
Clear milestone
No items
No milestone
Projects
Clear projects
No items
No project
Assignees
Clear assignees
No assignees
1 participant
Notifications
Due date
The due date is invalid or out of range. Please use the format "yyyy-mm-dd".

No due date set.

Dependencies

No dependencies set.

Reference: github-starred/zfs-ha#29
No description provided.
Delete branch "%!s()"

Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?