You are viewing a plain text version of this content. The canonical link for it is here.

Posted to notifications@jclouds.apache.org by "Andrew Bayer (JIRA)" <ji...@apache.org> on 2013/11/14 19:07:26 UTC

[jira] [Reopened] (JCLOUDS-361) Support for filters in EC2's DescribeInstances calls

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

Andrew Bayer reopened JCLOUDS-361:
----------------------------------


> Support for filters in EC2's DescribeInstances calls
> ----------------------------------------------------
>
>                 Key: JCLOUDS-361
>                 URL: https://issues.apache.org/jira/browse/JCLOUDS-361
>             Project: jclouds
>          Issue Type: Improvement
>          Components: jclouds-compute
>            Reporter: Andrew Bayer
>            Assignee: Andrew Bayer
>             Fix For: 1.7.0
>
>
> DescribeInstances allows you to specify filters - we should support that. And once we have that, we should do things like switch EC2ListNodesStrategy.listDetailsOnNodesMatching and EC2ComputeService.destroyNodesMatching (and resume, reboot, etc, etc) to take advantage of the server-side filtering. That should cut down on the volume of data being transferred considerably.



--
This message was sent by Atlassian JIRA
(v6.1#6144)