You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@brooklyn.apache.org by "Aled Sage (JIRA)" <ji...@apache.org> on 2017/04/19 14:00:49 UTC
[jira] [Created] (BROOKLYN-477) Add docs for target machine
requirements/expectations
Aled Sage created BROOKLYN-477:
----------------------------------
Summary: Add docs for target machine requirements/expectations
Key: BROOKLYN-477
URL: https://issues.apache.org/jira/browse/BROOKLYN-477
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 https://issues.apache.org/jira/browse/BROOKLYN-475 (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 be
done for only "interactive" shells (see http://stackoverflow.com/a/415444/1393883 for more
details).
{noformat}
There are no doubt many other things we could mention, such as:
* {{/tmp/}} should be writable
* Sufficient entropy (e.g. see https://brooklyn.apache.org/v/latest/ops/troubleshooting/increase-entropy.html for setting up Brooklyn itself)
* Outbound network connectivity (but not all blueprints require that)
--
This message was sent by Atlassian JIRA
(v6.3.15#6346)