[jira] [Commented] (BROOKLYN-477) Add docs for target machine requirements/expectations

["ASF GitHub Bot (JIRA)" <ji...@apache.org>]

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

ASF GitHub Bot commented on BROOKLYN-477:
-----------------------------------------

GitHub user aledsage opened a pull request:

    https://github.com/apache/brooklyn-docs/pull/192

    BROOKLYN-477: add “Provisioned Machine Requirements”

    

You can merge this pull request into a Git repository by running:

    $ git pull https://github.com/aledsage/brooklyn-docs BROOKLYN-477-add-vm-requirements

Alternatively you can review and apply these changes as the patch at:

    https://github.com/apache/brooklyn-docs/pull/192.patch

To close this pull request, make a commit to your master/trunk branch
with (at least) the following in the commit message:

    This closes #192
    
----
commit e846906d8ef49d47efb77c0b1912f036b6e262da
Author: Aled Sage <al...@gmail.com>
Date:   2017-05-24T13:29:30Z

    BROOKLYN-477: add “Provisioned Machine Requirements”

----


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