Thanks! That will work.
Not actually a "user-friendly" approach, but at least scriptable :)
ср, 13 июл. 2016 г. в 8:41, Atin Mukherjee <amukherj@xxxxxxxxxx>:
OK, so we already have this in glusterd's statedump. If you execute kill -SIGUSR1 $(pidof glusterd) you will get a glusterd statedump file with naming convention as glusterdump.<pid of glusterd>.dump. <time instance> in /var/run/gluster. This file would contain glusterd.max-op-version value under [xlator.glusterd.priv] section.HTH,On Wed, Jul 13, 2016 at 6:11 AM, Atin Mukherjee <amukherj@xxxxxxxxxx> wrote:
On Wednesday 13 July 2016, Pavel Malyshev <p.malishev@xxxxxxxxx> wrote:I have an automated system to deploy and upgrade gluster clusters, but till now I had to spend precious time to find out actual version value and set it manually...I tried to convert current gluster package version to op-version, like 3.7.1 to 30701, but it didn't work with 3,5&3.6 patches and some 3.7 patches (like 3.7.9, 3.7.11, etc).Each time I upgrade, since "op-version" was introduced I scratch my head and google a bit to find out which "op-version" should I set to my cluster.Hello!I use gluster for quite a long time and even survived a bunch of upgrades..
Last few times I had to download latest gluster sources and grep for 'GD_OP_VERSION' to find out the new value, which is not user friendly (or completely user unfriendly?).So my question is there any way to get the maximum supported op-version of installed glusterd daemon (not cluster version) via cli?No, we dont have. I think we can capture this in glusterd's statedump.
--
Atin
Sent from iPhone
----Atin
_______________________________________________ Gluster-users mailing list Gluster-users@xxxxxxxxxxx http://www.gluster.org/mailman/listinfo/gluster-users
