brooklyn-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Aled Sage (JIRA)" <>
Subject [jira] [Commented] (BROOKLYN-477) Add docs for target machine requirements/expectations
Date Wed, 19 Apr 2017 14:05:42 GMT


Aled Sage commented on BROOKLYN-477:

For the no-extra-stdout requirements, I wanted to also give a simple test such as:
run `ssh <user>@<ip> whoami` to confirm that no extra stdout is returned.

However, it seems our use of sshj behaves differently from the command-line ssh. If the VM
has in its {{~/.bash_profile}} something like {{echo "IN .BASH_PROFILE"}} then that is included
in the stdout of the ssh commands executed by Brooklyn. However, when using {{ssh}} at the
command line it is only written out if doing {{ssh <user>@<ip>}} rather than if
just executing a remote command. I couldn't reproduce Brooklyn's behaviour at the {{ssh}}
command line with {{-t}} or {{-tt}} either (see

> Add docs for target machine requirements/expectations
> -----------------------------------------------------
>                 Key: BROOKLYN-477
>                 URL:
>             Project: Brooklyn
>          Issue Type: Improvement
>            Reporter: Aled Sage
>            Priority: Minor
> We should improve our docs for the machine requirements/expectations, for blueprints
to behave as expected.
> This became evident when investigating
(extra stdout when ssh'ing). For example, our docs could say:
> {noformat}
> It is strongly recommended that VMs are configured so that no additional stdout is written

> when executing remote ssh (or WinRM) commands. Such stdout risks interfering with the
> response parsing in some blueprints.
> For example, if configuring the VM to write out "Last login" information, this should
> done for only "interactive" shells (see for
> details).
> {noformat}
> There are no doubt many other things we could mention, such as:
> * {{/tmp/}} should be writable
> * Sufficient entropy (e.g. see
for setting up Brooklyn itself)
> * Outbound network connectivity (but not all blueprints require that)

This message was sent by Atlassian JIRA

View raw message