You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@cloudstack.apache.org by "Kevin Kluge (JIRA)" <ji...@apache.org> on 2012/10/17 19:50:02 UTC
[jira] [Created] (CLOUDSTACK-367) CLI
Kevin Kluge created CLOUDSTACK-367:
--------------------------------------
Summary: 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
RE: [jira] [Commented] (CLOUDSTACK-367) CLI
Posted by Jie Feng <Ji...@citrix.com>.
+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:jira@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
RE: [jira] [Assigned] (CLOUDSTACK-367) CLI
Posted by "Musayev, Ilya" <im...@webmd.net>.
+1 for me, I can be guiney pig when test version comes and participate on dev to best of my abilities.
-----Original Message-----
From: edison su (JIRA) [mailto:jira@apache.org]
Sent: Wednesday, October 17, 2012 2:36 PM
To: cloudstack-dev@incubator.apache.org
Subject: [jira] [Assigned] (CLOUDSTACK-367) CLI
[ https://issues.apache.org/jira/browse/CLOUDSTACK-367?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
edison su reassigned CLOUDSTACK-367:
------------------------------------
Assignee: Rohit Yadav
It's your show time:)
> 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
[jira] [Assigned] (CLOUDSTACK-367) CLI
Posted by "edison su (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/CLOUDSTACK-367?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
edison su reassigned CLOUDSTACK-367:
------------------------------------
Assignee: Rohit Yadav
It's your show time:)
> 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
[jira] [Commented] (CLOUDSTACK-367) CLI
Posted by "edison su (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/CLOUDSTACK-367?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13478085#comment-13478085 ]
edison su commented on CLOUDSTACK-367:
--------------------------------------
+1, add a requirement: the CLI needs to support auto complete, like xe command line.
> 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
[jira] [Resolved] (CLOUDSTACK-367) CLI
Posted by "Prasanna Santhanam (JIRA)" <ji...@apache.org>.
[ 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
[jira] [Commented] (CLOUDSTACK-367) CLI
Posted by "Jie Feng (JIRA)" <ji...@apache.org>.
[ 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
[jira] [Commented] (CLOUDSTACK-367) CLI
Posted by "Musayev, Ilya (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/CLOUDSTACK-367?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13478217#comment-13478217 ]
Musayev, Ilya commented on CLOUDSTACK-367:
------------------------------------------
+1 for me, I can be guiney pig when test version comes and participate on dev to best of my abilities.
> 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
[jira] [Commented] (CLOUDSTACK-367) CLI
Posted by "David Nalley (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/CLOUDSTACK-367?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13478088#comment-13478088 ]
David Nalley commented on CLOUDSTACK-367:
-----------------------------------------
Before we reinvent the wheel - lets take a look at what is already out there:
Off the top of my head I know of a Datapipe authored project on google code, Arcus (ruby based), a python written tool by jgaret, and then there is a jclouds based command-line tool that would probably work, or at least would be easily modified.
> 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
[jira] [Commented] (CLOUDSTACK-367) CLI
Posted by "Rohit Yadav (JIRA)" <ji...@apache.org>.
[ 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