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

Posted to dev@brooklyn.apache.org by "Iker (JIRA)" <ji...@apache.org> on 2015/08/10 09:22:45 UTC

[jira] [Comment Edited] (BROOKLYN-160) No-op entity for Windows VMs

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

Iker edited comment on BROOKLYN-160 at 8/10/15 7:21 AM:
--------------------------------------------------------

About the proposed solution of Aled Sage, it does not work (am I doing something wrong). There is a comment in the thread of Stackoverflow


was (Author: ikercrg):
About the proposed solution of Aled Sage, it does not work (am I doing something wrong). There is a comment in the thread.

> 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
>
> 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.3.4#6332)