[
https://issues.apache.org/jira/browse/JCLOUDS-581?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14017159#comment-14017159
]
Ignasi Barrera commented on JCLOUDS-581:
----------------------------------------
The point here is that not all providers support the powerOff operation. For
example in AWS you can't powerOff certain types of micro instances, etc.
Others, such as DigitalOcean, IIRC, don't support the suspend operation. That's
why it is difficult/tricky to map every single operation in the portable
interface.
Instead, we have a domain model with (what we call) portable states and
portable semantics, and providers map their specific operations to the ones in
the portable model. In the cases where one needs a more fine-grained control
over the details of how the actual suspend or resume happens on a provider, we
encourage using the provider specific api instead. Adding the four operations
suspend/resume/powerOn/powerOff, might end up in providers supporting only some
of them, and that could break the "portable" concept of the compute service.
Back to your issue, does the suspendNode work for you, or you need to
explicitly differentiate between a suspended and powered off node? (Given that
the jclouds portable states only considers the suspended state too?).
> 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)
