-
-
Notifications
You must be signed in to change notification settings - Fork 15.5k
glusterfs: 3.12.12 -> 4.0.0 #49743
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
glusterfs: 3.12.12 -> 4.0.0 #49743
Conversation
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.
From my point of view we can merge this. I might find some time to have a look at upgrading to version 5 after this.
Why not jump to latest v4.x maintenance release (v4.1.5) then? |
@c0bw3b Because I haven't tested that. The 4.0 version I have tested extensively, so I feel more confident in submitting that. Glusterfs is difficult to upgrade in the sense that they call a lot of utilities (especially python and bash) at runtime for specific use cases, so if one doesn't test things in anger, one cannot really be sure that the point release doesn't break things, especially related to packaging. |
Hi @nh2 can you elaborate more on your last post? I see that now the gluster people released version 6 just few days ago, can you point me to something more specific about those upgrade issues? also the issue you referred to in the changelogs ( https://bugzilla.redhat.com/show_bug.cgi?id=1509340 ) is marked as closed now |
@azazel75 Sure, which parts do you want to know about? What I was saying in my post is: GlusterFS does not only include some C programs. The servers included will also invoke other utilities, sometimes across multiple machines, with For the PR I made, I tried to test as many Gluster features as possible (e.g. geo-replication) to see if I hit any such hardcoded paths. With new Gluster releases, they may have added more features (and thus such paths), which ideally should also be tested. Hope that helps; don't hesitate to ask more. |
Clarifying @azazel75's question on
My answer:
|
Motivation for this change
Upgrade to new major release.
Things done
sandbox
innix.conf
on non-NixOS)nix-shell -p nox --run "nox-review wip"
./result/bin/
)nix path-info -S
before and after)CC @bachp
I have tested this for a long time on my Gluster cluster.
Now I'm moved to ceph, but I still want to upstream the improvements to NixOS.
Note that the 4.0.0 point release is older (in date) than the current 3.12.12 point release. Thus it may not have the same level of security patches.
Note both 4.0.* and 3.* are already EOL according to https://www.gluster.org/release-schedule/, so we have to upgrade further anyway for NixOS 19.03. I hope that this PR, especially the upgrading of the NixOS specific patches, helps with that.