Mark Wu has posted comments on this change.
Change subject: Fix usage message for vdsm-tool
......................................................................
Patch Set 1: (1 inline comment)
....................................................
File vdsm-tool/vdsm-tool
Line 96: print "Usage: %s [options] <action> [arguments]\n" %
sys.argv[0]
Ryan,
I don't understand why you said we need specify both the command name and its module
name. From the code of vdsm-tool, it collects all exposed function by scanning all *.py
files in 'vdsm.tool' directory and puts into one dict: tool_command.
So, we needn't specify module name to invoke a command. If the same command name
appears in different module, it could cause conflict. In that case, specifying a module in
the command line of vdsm-tool could help. Is the "module" name is needed in
design but not implemented?
Thanks
--
To view, visit
http://gerrit.ovirt.org/4065
To unsubscribe, visit
http://gerrit.ovirt.org/settings
Gerrit-MessageType: comment
Gerrit-Change-Id: I5382130f9003da983c88a708aa9ee2abe072f3d5
Gerrit-PatchSet: 1
Gerrit-Project: vdsm
Gerrit-Branch: master
Gerrit-Owner: Wenyi Gao <wenyi(a)linux.vnet.ibm.com>
Gerrit-Reviewer: Adam Litke <agl(a)us.ibm.com>
Gerrit-Reviewer: Dan Kenigsberg <danken(a)redhat.com>
Gerrit-Reviewer: Federico Simoncelli <fsimonce(a)redhat.com>
Gerrit-Reviewer: Mark Wu <wudxw(a)linux.vnet.ibm.com>
Gerrit-Reviewer: Ryan Harper <ryanh(a)us.ibm.com>
Gerrit-Reviewer: ShaoHe Feng <shaohef(a)linux.vnet.ibm.com>
Gerrit-Reviewer: Shu Ming <shuming(a)linux.vnet.ibm.com>
Gerrit-Reviewer: Wenyi Gao <wenyi(a)linux.vnet.ibm.com>