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

Posted to dev@brooklyn.apache.org by "Svetoslav Neykov (JIRA)" <ji...@apache.org> on 2017/06/20 15:27:00 UTC

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

     [ https://issues.apache.org/jira/browse/BROOKLYN-160?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Svetoslav Neykov resolved BROOKLYN-160.
---------------------------------------
       Resolution: Fixed
    Fix Version/s: 0.9.0

> 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)