You are viewing a plain text version of this content. The canonical link for it is here.

Posted to dev@brooklyn.apache.org by ahgittin <gi...@git.apache.org> on 2016/08/23 14:31:13 UTC

[GitHub] brooklyn-server issue #304: Adds a target configuration to the SSH command e...

Github user ahgittin commented on the issue:

    https://github.com/apache/brooklyn-server/pull/304
  
    would it make sense to split up `SshCommandMembershipTrackingPolicy` so that we have`InvokeEffectorMembershipTrackingPolicy` and `SshMultiEntityCommandEffector` -- where the latter has the configurable target you've introduced here (and where `TARGET` defaults to the current entity if it has an `SshMachineLocation`, to sshable members if it's a group, and to sshable children otherwise;  and could be set to be an `Entity` or the enum you provide) ?
    
    (then to handle DNS i think we don't even need a membership tracking policy if we have a suitably configured group and an aggregator on hostnames -- all we need is an `InvokeEffectorOnSensorChangePolicy`)


---
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 infrastructure@apache.org or file a JIRA ticket
with INFRA.
---