[
https://issues.apache.org/jira/browse/BROOKLYN-477?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16024479#comment-16024479
]
ASF GitHub Bot commented on BROOKLYN-477:
-----------------------------------------
Github user drigodwin commented on a diff in the pull request:
https://github.com/apache/brooklyn-docs/pull/192#discussion_r118453118
--- Diff: guide/locations/provisioned-machine-requirements.md ---
@@ -0,0 +1,161 @@
+---
+title: Provisioned Machine Requirements
+layout: website-normal
+---
+
+The requirements for how a provisioned machine should behave will depend
on the
+entites subsequently deployed there.
+
+Below are a set of common assumptions, made by many entity
implementations, which
+could cause subsequent errors if they do not hold. These relate to the
machine's
+configuration, rather than additional networking or security that a given
Cloud
+might offer.
+
+Also see the [Troubleshooting]({{ site.path.guide }}/ops/troubleshooting/)
docs.
+
+
+## Remote Access
+
+### SSH or WinRM Access
+
+Many entities require ssh'ing (or using WinRM for Windows), to install and
configure
--- End diff --
I'm not a fan of `ssh'ing` would change `require ssh'ing` to `require
[ssh](https://en.wikipedia.org/wiki/Secure_Shell) enabled`
> 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)
