cloudstack-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "ASF subversion and git services (JIRA)" <>
Subject [jira] [Commented] (CLOUDSTACK-94) API command, listIsos documentation clarity
Date Mon, 11 Mar 2013 17:33:13 GMT


ASF subversion and git services commented on CLOUDSTACK-94:

Commit 85e9d63be4d7c275dedd773c63a6aca0cde03356 in branch refs/heads/ui-multiple-nics from
Chip Childers <>
[;h=85e9d63 ]

CLOUDSTACK-94: API command, listIsos documentation clarity

Updated API documentation for listIsos command.

Descriptions for id and isofilter descriptions clarified:
- Updated isofilter description with all options and verbiage taken from VirtualMachineTemplate
- Updated id description

Signed-off-by: Chip Childers <>

> API command, listIsos documentation clarity
> -------------------------------------------
>                 Key: CLOUDSTACK-94
>                 URL:
>             Project: CloudStack
>          Issue Type: Bug
>      Security Level: Public(Anyone can view this level - this is the default.) 
>          Components: Doc
>    Affects Versions: 4.1.0
>         Environment: This document:
>            Reporter: Jesse Callaway
>            Assignee: David Grizzanti
>            Priority: Minor
>              Labels: api, documentation
>             Fix For: 4.1.0
>   Original Estimate: 20m
>  Remaining Estimate: 20m
> Bug description:
> The isofilter parameter copy does not list all valid arguments. Where they are listed,
it is confusing to read.
> In particular, the "all" argument should be listed.
> Related bug:
> The description of the "id" parameter is incorrect. It does not list all iso's by id.
It is the id of the ISO to be listed. The word _all_ in this context is not only confusing,
but is incorrect, since a uuid is universally unique.
> Further consideration:
> "isofilter=all" should be the default behavior. However, that is not a documentation
bug, but a usability preference.

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:

View raw message