[
https://issues.apache.org/jira/browse/JCLOUDS-610?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14044168#comment-14044168
]
ASF subversion and git services commented on JCLOUDS-610:
---------------------------------------------------------
Commit 3f1ed2fd5bd6f84aff39b26456a80c5437934089 in jclouds-karaf's branch
refs/heads/master from [~andrewp]
[ https://git-wip-us.apache.org/repos/asf?p=jclouds-karaf.git;h=3f1ed2f ]
JCLOUDS-610: Aligning overrides in ComputeServiceEventProxy with ComputeService
See https://git-wip-us.apache.org/repos/asf?p=jclouds.git;h=8598ee8
> reboot, suspend, and resumeNodesMatching methods gain functionality similar
> to that of destroyNodesMatching
> -----------------------------------------------------------------------------------------------------------
>
> Key: JCLOUDS-610
> URL: https://issues.apache.org/jira/browse/JCLOUDS-610
> Project: jclouds
> Issue Type: Improvement
> Components: jclouds-compute
> Affects Versions: 1.7.3
> Reporter: Christopher Dancy
> Labels: ComputeService
> Fix For: 1.8.0
>
> Attachments: JCLOUDS-610-karaf.patch, JCLOUDS-610.patch
>
>
> We'd like to refactor ComputeService, and specifically the methods
> suspendNodesMatching, resumeNodesMatching, and rebootNodesMatching, to match
> the functionality provided by method destroyNodesMatching of the same class;
> that being: allow these methods to return a 'Set<? extends NodeMetadata>'.
> We currently have a high-level wrapper around jclouds which returns objects
> populated with ONLY a few variables available from NodeMetadata. Currently we
> can not provide that information if we attempt to suspend, resume, and/or
> reboot a set of nodes. The above change will provide that.
> This does require a change to the ComputeService API but only insofar as to
> what the methods return and NOT what they are named and/or what is passed
> into them. This has the added benefit of not being a destructive change for
> any current users of these method calls as things will "just work" for them
> as they always have. However, and for future users of these calls, we will
> now be able to retrieve a 'Set<? extends NodeMetadata>'.
--
This message was sent by Atlassian JIRA
(v6.2#6252)
