+1 for having a good CLI. From a CloudStack user perspective (not admin), I found that the UI does not expose all the functions in the API. And it is not easy for a user to create signed API calls. I have not used the existing CLI tool because it is only referenced in docs, but unclear where to find it.
One question: why not expose all the functions in the API through CLI? Jie -----Original Message----- From: Rohit Yadav (JIRA) [mailto:j...@apache.org] Sent: Wednesday, October 17, 2012 11:14 AM To: cloudstack-dev@incubator.apache.org Subject: [jira] [Commented] (CLOUDSTACK-367) CLI [ https://issues.apache.org/jira/browse/CLOUDSTACK-367?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13478092#comment-13478092 ] Rohit Yadav commented on CLOUDSTACK-367: ---------------------------------------- and use/create a wrapper/shell over cloudstackAPI (cloud-python), so the tool won't need to have hard coded list of APIs; plus some pythonic magic for auto-completion. > CLI > --- > > Key: CLOUDSTACK-367 > URL: https://issues.apache.org/jira/browse/CLOUDSTACK-367 > Project: CloudStack > Issue Type: New Feature > Affects Versions: 4.0.0 > Reporter: Kevin Kluge > > The auto-generated CLI that CloudStack has had is not user friendly and not > in widespread use. > We should design a "real" CLI tool (or set of commands) that exposes a > significant chunk of both the end user and admin API functions. When this > is done we should just remove the old CLI tool. > I think end user is higher priority but both should be done. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira
