brooklyn-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Svetoslav Neykov (JIRA)" <j...@apache.org>
Subject [jira] [Comment Edited] (BROOKLYN-160) No-op entity for Windows VMs
Date Tue, 20 Jun 2017 15:27:00 GMT

    [ https://issues.apache.org/jira/browse/BROOKLYN-160?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16055934#comment-16055934
] 

Svetoslav Neykov edited comment on BROOKLYN-160 at 6/20/17 3:26 PM:
--------------------------------------------------------------------

There's {{EmptyWindowsProcess}} now where the various operations can be disabled.


was (Author: svet):
There's {{EmptyWindowsProcess}} now.

> No-op entity for Windows VMs
> ----------------------------
>
>                 Key: BROOKLYN-160
>                 URL: https://issues.apache.org/jira/browse/BROOKLYN-160
>             Project: Brooklyn
>          Issue Type: New Feature
>    Affects Versions: 0.7.0
>            Reporter: Aled Sage
>             Fix For: 0.9.0
>
>
> A user is interested in Brooklyn provisioning a Windows VM from an AWS marketplace AMI,
but where that Windows VM does not have WinRM enabled.
> http://stackoverflow.com/questions/31241606/how-to-install-tibco-spotfire-with-apache-brooklyn
> There is no convenient Windows no-op entity (the VanillaWindowsProcess currently always
executes commands).
> The workaround is to use EmptySoftwareProcess, which expects an SshMachineLocation, but
with it configured to execute nothing (so it never notices that the SshMachineLocation is
not ssh'able!)



--
This message was sent by Atlassian JIRA
(v6.4.14#64029)

Mime
View raw message