You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Currently the output of gluster get-state command is read from a file. This file is in ini format and we just read that into json. Each section in the file becomes one dictionary with entries as keys in dictionary. It would be better parseable/processable if we create a proper hierarchical dictionary as below out of this data and then update the detail into central store
This would make looping through the details and updation in central store more predictable and errors can be handled more effectively (as in case a KeyError for one volume doesnt cause other volume details updation failures and the error could be logged for that specific volume only)
The text was updated successfully, but these errors were encountered:
Currently the output of
gluster get-state
command is read from a file. This file is inini
format and we just read that into json. Each section in the file becomes one dictionary with entries as keys in dictionary. It would be better parseable/processable if we create a proper hierarchical dictionary as below out of this data and then update the detail into central storeThis would make looping through the details and updation in central store more predictable and errors can be handled more effectively (as in case a
KeyError
for one volume doesnt cause other volume details updation failures and the error could be logged for that specific volume only)The text was updated successfully, but these errors were encountered: