cloudstack-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Prasanna Santhanam (JIRA)" <j...@apache.org>
Subject [jira] [Resolved] (CLOUDSTACK-367) CLI
Date Thu, 18 Oct 2012 04:08:03 GMT

     [ https://issues.apache.org/jira/browse/CLOUDSTACK-367?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]

Prasanna Santhanam resolved CLOUDSTACK-367.
-------------------------------------------

    Resolution: Duplicate

Rohit - take a look at CLOUDSTACK-132. We have some the groundwork needed in Marvin's libraries.
Providing a properties file with API signature and SECRET key signature that marvin will read
at startup can easily switch between admin and user functions. 
                
> 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
>            Assignee: Rohit Yadav
>
> 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