brooklyn-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Iker (JIRA)" <>
Subject [jira] [Commented] (BROOKLYN-160) No-op entity for Windows VMs
Date Mon, 10 Aug 2015 07:21:45 GMT


Iker commented on BROOKLYN-160:

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:
>             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.
> 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

View raw message