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

ASF GitHub Bot commented on CLOUDSTACK-9351:
--------------------------------------------

Github user koushik-das commented on the pull request:

    https://github.com/apache/cloudstack/pull/1497#issuecomment-217789291
  
    @nvazquez The test results show that it took ~20mins to complete. Why list 
tests are taking so long?
    Some observations:
    - Tests are not tagged, please tag them (refer to existing tests). I ran 
them in a simulator setup and they passed so these can be added to Travis once 
the overall time is reduced and proper tags added
    - Templates created as part of tests is not cleaned up.
    - time.sleep(720). I saw the comment about vm snapshot issue, better to 
disable the vm snapshot test and enable it once snapshot issue is fixed


> Add ids parameter to resource listing API calls
> -----------------------------------------------
>
>                 Key: CLOUDSTACK-9351
>                 URL: https://issues.apache.org/jira/browse/CLOUDSTACK-9351
>             Project: CloudStack
>          Issue Type: Improvement
>      Security Level: Public(Anyone can view this level - this is the 
> default.) 
>          Components: API
>    Affects Versions: 4.9.0
>            Reporter: Nicolas Vazquez
>             Fix For: 4.9.0
>
>
> h2. General behaviour
> A new parameter is added in each method, its type a list of IDs of the 
> entity, it will be mutually exclusive with id. (Similar to {{id}} and {{ids}} 
> parameters in {{listVirtualMachines}} method)
> h3. API Methods affected
> * +{{listTemplates}}+: new parameter *{{ids}}*, mutually exclusive with {{id}}
> * +{{listVolumes}}+: new parameter *{{ids}}*, mutually exclusive with {{id}}
> * +{{listSnapshots}}+: new parameter *{{ids}}*, mutually exclusive with {{id}}
> * +{{listVMSnapshots}}+: new parameter *{{vmsnapshotids}}*, mutually 
> exclusive with {{vmsnapshotid}}



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

Reply via email to