[
https://issues.apache.org/jira/browse/JCLOUDS-361?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13810887#comment-13810887
]
Andrew Bayer commented on JCLOUDS-361:
--------------------------------------
Initial PR up at https://github.com/jclouds/jclouds/pull/194 - this is just
adding a filterInstancesInRegion(region, filter) method to AWSInstanceApi and
related tests. The hard part is still to come - figuring out how to translate
the Predicate<NodeMetadata>s passed to destroyNodesMatching and its kin into
filter multimaps. If anyone has any ideas on that, I'd love to hear them. =)
> 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)
