Github user sjcorbett commented on a diff in the pull request:
https://github.com/apache/incubator-brooklyn/pull/763#discussion_r35646665
--- Diff:
software/base/src/main/java/brooklyn/entity/software/MachineLifecycleEffectorTasks.java
---
@@ -151,8 +151,18 @@ public void attachLifecycleEffectors(Entity entity) {
.build();
}
+ /** @see {@link #newStartEffector()} */
+ public Effector<Void> newSuspendEffector() {
+ return Effectors.effector(Void.class, "suspend")
+ .description("Suspend the process/service represented by
an entity")
+ .parameter(StopSoftwareParameters.STOP_PROCESS_MODE)
+ .parameter(StopSoftwareParameters.STOP_MACHINE_MODE)
+ .impl(newSuspendEffectorTask())
+ .build();
+ }
--- End diff --
Suspending a machine has the same semantics as stopping a machine. They
both use `MachineLifecycleEffectorTasks#doStop`. The former calls
`MachineProvisioningLocation#release` (which becomes
`JcloudsLocation#releaseNode`), the latter
`MachineManagementMixins.SuspendsMachines#suspendMachine` (which becomes
`JcloudsLocation#suspendMachine`). A suspended machine cannot subsequently be
stopped if `IF_NOT_STOPPED` is true because
`MachineLifecycleEffectorTasks#doStop` sets the entity's state to `STOPPED`.
---
If your project is set up for it, you can reply to this email and have your
reply appear on GitHub as well. If your project does not have this feature
enabled and wishes so, or if the feature is enabled but not working, please
contact infrastructure at [email protected] or file a JIRA ticket
with INFRA.
---
