[
https://issues.apache.org/jira/browse/JCLOUDS-581?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14019205#comment-14019205
]
Christopher Dancy commented on JCLOUDS-581:
-------------------------------------------
Gotcha. It seems that if we were to put the burden on providers to implement
suspend/resume/powerOff/powerOn they could then decide whether to code an
actual powerOff or just forward the request to suspend. Either way it would at
least make some distinction and not cause confusion/frustration on developers
looking for a powerOff/powerOnf call at the ComputeService level (seeing as how
there is seemingly everything else).
With that said I do understand your predicament. Yes the current code does work
as I need; the names however are just misleading. I can absolutely get by it
would just be a nice-to-have.
> Method calls "startNodesMatching" and "stopNodesMatching" added to
> BaseComputeService
> -------------------------------------------------------------------------------------
>
> Key: JCLOUDS-581
> URL: https://issues.apache.org/jira/browse/JCLOUDS-581
> Project: jclouds
> Issue Type: New Feature
> Components: jclouds-compute
> Affects Versions: 1.7.3
> Reporter: Christopher Dancy
> Labels: BaseComputeService, startNodesMatching, stopNodesMatching
>
> Addition of methods "startNodesMatching" and "stopNodesMatching" added to
> BaseComputeService. We are coding this very thing on our end for
> openstack/rackspace but seems a fairly common enough thing that all providers
> and/or users of jclouds could take advantage of.
--
This message was sent by Atlassian JIRA
(v6.2#6252)
