incubator-cloudstack-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Jie Feng (JIRA)" <j...@apache.org>
Subject [jira] [Commented] (CLOUDSTACK-367) CLI
Date Wed, 17 Oct 2012 18:24:05 GMT

    [ https://issues.apache.org/jira/browse/CLOUDSTACK-367?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13478103#comment-13478103
] 

Jie Feng commented on CLOUDSTACK-367:
-------------------------------------

+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


                
> 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

Mime
View raw message