Add methods to get and set the glusterfs op-version #45091
Conversation
|
This is my first PR to this project and Github, so please let me know if there is anything I missed / could do better. I made these changes locally on my salt master to assist with upgrading Glusterfs versions in our environment. Post upgrade, glusterfs documentation recommends updating the op-version, http://docs.gluster.org/en/latest/Upgrade-Guide/op_version/. Now I'm just trying to share my additions with the community. |
|
Also, according to the coding-style section, I need to bring up that I am not sure what should be added to the function documentation for versionadded. |
There was a problem hiding this comment.
Welcome @robertpenberthy! Thank you for submitting your addition. This is a really great start.
I have a couple of comments. Most are documentation updates, but there are a couple of things in the state functions that need to be fixed in the code.
Can you also write some tests for these new functions?
Please let us know if you have any questions!
salt/modules/glusterfs.py
Outdated
|
|
||
| def get_op_version(name): | ||
| ''' | ||
| Returns the glusterfs volume op-version |
There was a problem hiding this comment.
Can you add a .. versionadded:: Fluorine tag here for this new function?
This comment applies to the other functions you've added here as well. :)
salt/modules/glusterfs.py
Outdated
| ''' | ||
|
|
||
| version = '' | ||
| cmd = 'gluster volume get {0} cluster.op-version'.format(name) |
There was a problem hiding this comment.
Can you change this to a list of command options, rather than a string? It's safer that way since name could pass in anything.
There was a problem hiding this comment.
To make sure I understand what you're asking, is this what I should change it to?
cmd = ['gluster', 'volume', 'get', name, 'cluster.op-version']
salt/modules/glusterfs.py
Outdated
| salt '*' glusterfs.set_op_version <volume> | ||
| ''' | ||
|
|
||
| cmd = 'gluster volume set all cluster.op-version {0}'.format(version) |
There was a problem hiding this comment.
Same comment here about lists vs. a string.
salt/states/glusterfs.py
Outdated
| def op_version(name, version): | ||
| ''' | ||
| Add brick(s) to an existing volume | ||
|
|
There was a problem hiding this comment.
versionadded tags are needed for these 2 new state functions as well.
salt/modules/glusterfs.py
Outdated
| ''' | ||
| Returns the glusterfs volume's max op-version value | ||
| Requires Glusterfs version > 3.9 | ||
| ''' |
There was a problem hiding this comment.
This function needs a CLI Example.
salt/states/glusterfs.py
Outdated
| ret['result'] = True | ||
| return ret | ||
|
|
||
| result = __salt__['glusterfs.set_op_version'](version) |
There was a problem hiding this comment.
This state function needs to support test=true behavior before actually changing anything. Can you add that, please?
salt/states/glusterfs.py
Outdated
| ret['result'] = True | ||
| return ret | ||
|
|
||
| result = __salt__['glusterfs.set_op_version'](max_version) |
There was a problem hiding this comment.
This state function also needs to support test=true functionality.
rallytime
added
the
Needs-Testcase
Changing cmd to list. Adding test=True handling for the states. Added try / except around calls to the execution module.
|
Thanks @robertpenberthy! This looks great. Now all we need is some unit tests and we'll be good to go. There's some docs on that here. Let us know if you have any questions. :) |
|
@rallytime Yep, I'm aware that I need to add those unit tests. It may take me a while to get those done, due to some of my other priorities, as well as I am new to Python (doing this custom module is pretty much the only Python I have ever written) and have never written Unit tests before. I hope to get through the documentation soon and then the tests written. I've looked at the existing tests for these modules and hopefully can easily pattern after them. |
|
@robertpenberthy Wonderful! Thank you so much. Definitely let us know if you have troubles. |
|
@rallytime So I've been looking at how the tests are written for the existing functions in the module execution module and realize that these methods are all executing their commands through the _gluster_xml private method. I've also learned a bit more about how the existing functions work. The existing functions use the string.format(variable) syntax, which you told me to change to a list for my functions. When passing the list to the _gluster_xml function, it returns with an error. It does work if I use the string.format(variable) syntax. So now I am wondering, should I switch my command back to string.format(variable) and make my functions execute the commands in the same way as the existing code? Should I go through and change the existing functions to use and accept the list format? Or break from the existing pattern in this specific module and its unit tests, executing my code how I wrote it initially and write my tests to fit how I executed the commands? |
- Changed the functions to execute the commands in the same manner as the pre-existing functions. - Added unit tests
|
@rallytime I assumed I should change it up to be like the pre-existing fucntions and did so, then wrote some unit tests. Just wrote them for the execution module functions so far. Please let me know if I got anything wrong with them. |
…velop' into glusterfs-op-version-upstream/develop
|
@rallytime I've added tests. I believe I've completed all requests in the code review. |
rallytime
removed
the
Needs-Testcase
|
Thanks @robertpenberthy! |
What does this PR do?
Adds methods to the existing glusterfs execution and state modules to querying and setting the glusterfs op-version.
What issues does this PR fix or reference?
None
Tests written?
No
Commits signed with GPG?
Yes