Join GitHub today
GitHub is home to over 36 million developers working together to host and review code, manage projects, and build software together.Sign up
cli: Backward compatibility for option names #739
Since Glusterd2 loads list of xlator options directly from
This may break many applications, tests and other integrations. APIs can continue to use the option names as Glusterd2 expects, CLI should convert old option name to new option name(excluding the ones which needs name change for usability)
referenced a pull request that will
May 29, 2018
Unsure which other issue to post this comment to, so using this one that talks about backward compatibility.
Questions and thoughts:
All volume set related to io-stat will be set under
Makes sense, does glusterd1 supports this? my understanding was glusterd1 is acting as router user sees the option related to feature but internally it sets to respective xlator. For example, user sets "cluster.data-self-heal", but internally it is set to "replicate.data-self-heal". This avoids confusion if user thinks why he need to set "replicate.*" option when using disperse Volume.
We need enhancement in volgen, if options needs to be filtered based on graph type.
Not yet available
referenced this issue
Jul 20, 2018
@aravindavk - We need to get this addressed sooner so that we would be able to run the existing test suites from glusterfs (the xxx.t files) and all the Glusto test cases. We can have a discussion on this topic to see what are the current gaps and how soon we can address them.