You are viewing a plain text version of this content. The canonical link for it is here.

Posted to dev@brooklyn.apache.org by richardcloudsoft <gi...@git.apache.org> on 2016/06/20 15:09:34 UTC

[GitHub] brooklyn-docs pull request #79: Ops guides updates for monitoring and disk s...

GitHub user richardcloudsoft opened a pull request:

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

    Ops guides updates for monitoring and disk space

    Some additions to the User Guide "Operations" section, covering starting, monitoring and stopping the server, and a discussion of its disk space usage.

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

    $ git pull https://github.com/rdowner/brooklyn-docs ops-update-monitoring-diskspace

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

    https://github.com/apache/brooklyn-docs/pull/79.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 #79
    
----
commit 07101c40758f286a4a084ff6828c7e16a3dc999b
Author: Richard Downer <ri...@apache.org>
Date:   2016-06-20T15:08:02Z

    Ops guides updates for monitoring and disk space
    
    Some additions to the User Guide "Operations" section, covering start,
    monitoring and stopping the server, and a discussion of its disk space
    usage.

----


---
If your project is set up for it, you can reply to this email and have your
reply appear on GitHub as well. If your project does not have this feature
enabled and wishes so, or if the feature is enabled but not working, please
contact infrastructure at infrastructure@apache.org or file a JIRA ticket
with INFRA.
---

[GitHub] brooklyn-docs pull request #79: Ops guides updates for monitoring and disk s...

Posted by aledsage <gi...@git.apache.org>.

Github user aledsage commented on a diff in the pull request:

    https://github.com/apache/brooklyn-docs/pull/79#discussion_r67830154
  
    --- Diff: guide/ops/starting-stopping-monitoring.md ---
    @@ -0,0 +1,66 @@
    +---
    +title: Starting, Stopping and Monitoring
    +layout: website-normal
    +---
    +
    +**NOTE:** This document is for information on starting an Apache Brooklyn
    +Server.  For information on using the Brooklyn Client CLI to access an already
    +running Brooklyn Server, refer to [Client CLI Reference](cli/index.html).
    +
    +
    +## Starting
    +
    +To launch Brooklyn, from the directory where Brooklyn is unpacked, run:
    +
    +{% highlight bash %}
    +% bin/brooklyn launch > /dev/null 2>&1 & disown
    --- End diff --
    
    Looking more closely, I see that the server-cli-reference doesn't have a good "stop" section. Where do you think is most appropriate to put your new section on stopping? (bearing in mind we'll need two variants: one for this approach, and one for rpm/deb packages).


---
If your project is set up for it, you can reply to this email and have your
reply appear on GitHub as well. If your project does not have this feature
enabled and wishes so, or if the feature is enabled but not working, please
contact infrastructure at infrastructure@apache.org or file a JIRA ticket
with INFRA.
---

[GitHub] brooklyn-docs issue #79: Ops guides updates for monitoring and disk space

Posted by aledsage <gi...@git.apache.org>.

Github user aledsage commented on the issue:

    https://github.com/apache/brooklyn-docs/pull/79
  
    Looks good - a few minor comments.
    
    We should see how this relates / overlaps with what @nakomis has been writing (which is mostly related to HA). In particular, your monitoring section could include the relevant REST api call for a basic health check.


---
If your project is set up for it, you can reply to this email and have your
reply appear on GitHub as well. If your project does not have this feature
enabled and wishes so, or if the feature is enabled but not working, please
contact infrastructure at infrastructure@apache.org or file a JIRA ticket
with INFRA.
---

[GitHub] brooklyn-docs issue #79: Ops guides updates for monitoring and disk space

Posted by aledsage <gi...@git.apache.org>.

Github user aledsage commented on the issue:

    https://github.com/apache/brooklyn-docs/pull/79
  
    LGTM; merging.


---
If your project is set up for it, you can reply to this email and have your
reply appear on GitHub as well. If your project does not have this feature
enabled and wishes so, or if the feature is enabled but not working, please
contact infrastructure at infrastructure@apache.org or file a JIRA ticket
with INFRA.
---

[GitHub] brooklyn-docs issue #79: Ops guides updates for monitoring and disk space

Posted by rdowner <gi...@git.apache.org>.

Github user rdowner commented on the issue:

    https://github.com/apache/brooklyn-docs/pull/79
  
    How bizarre! Branch lives on the `rdowner` repository, but I inadvertently opened the PR under the `richardcloudsoft` user -- and GitHub let me do it??!! \U0001f616 


---
If your project is set up for it, you can reply to this email and have your
reply appear on GitHub as well. If your project does not have this feature
enabled and wishes so, or if the feature is enabled but not working, please
contact infrastructure at infrastructure@apache.org or file a JIRA ticket
with INFRA.
---

[GitHub] brooklyn-docs pull request #79: Ops guides updates for monitoring and disk s...

Posted by aledsage <gi...@git.apache.org>.

Github user aledsage commented on a diff in the pull request:

    https://github.com/apache/brooklyn-docs/pull/79#discussion_r67829739
  
    --- Diff: guide/ops/starting-stopping-monitoring.md ---
    @@ -0,0 +1,66 @@
    +---
    +title: Starting, Stopping and Monitoring
    +layout: website-normal
    +---
    +
    +**NOTE:** This document is for information on starting an Apache Brooklyn
    +Server.  For information on using the Brooklyn Client CLI to access an already
    +running Brooklyn Server, refer to [Client CLI Reference](cli/index.html).
    +
    +
    +## Starting
    +
    +To launch Brooklyn, from the directory where Brooklyn is unpacked, run:
    +
    +{% highlight bash %}
    +% bin/brooklyn launch > /dev/null 2>&1 & disown
    --- End diff --
    
    It feels like this bit is duplicating http://brooklyn.apache.org/v/latest/ops/server-cli-reference.html
    
    Perhaps we should just reference that instead of having the starting/stopping sub-sections, and ensure that the server-cli-reference is good enough?


---
If your project is set up for it, you can reply to this email and have your
reply appear on GitHub as well. If your project does not have this feature
enabled and wishes so, or if the feature is enabled but not working, please
contact infrastructure at infrastructure@apache.org or file a JIRA ticket
with INFRA.
---

[GitHub] brooklyn-docs pull request #79: Ops guides updates for monitoring and disk s...

Posted by rdowner <gi...@git.apache.org>.

Github user rdowner commented on a diff in the pull request:

    https://github.com/apache/brooklyn-docs/pull/79#discussion_r67850130
  
    --- Diff: guide/ops/starting-stopping-monitoring.md ---
    @@ -0,0 +1,66 @@
    +---
    +title: Starting, Stopping and Monitoring
    +layout: website-normal
    +---
    +
    +**NOTE:** This document is for information on starting an Apache Brooklyn
    +Server.  For information on using the Brooklyn Client CLI to access an already
    +running Brooklyn Server, refer to [Client CLI Reference](cli/index.html).
    +
    +
    +## Starting
    +
    +To launch Brooklyn, from the directory where Brooklyn is unpacked, run:
    +
    +{% highlight bash %}
    +% bin/brooklyn launch > /dev/null 2>&1 & disown
    --- End diff --
    
    @aledsage My opinion is that this page serves a different purpose to the CLI reference page and we should keep both. This is duplicating a just a few lines, and then sending the reader to the Server CLI page. I think this is the smallest possible amount of duplication that keeps both pages useful.


---
If your project is set up for it, you can reply to this email and have your
reply appear on GitHub as well. If your project does not have this feature
enabled and wishes so, or if the feature is enabled but not working, please
contact infrastructure at infrastructure@apache.org or file a JIRA ticket
with INFRA.
---

[GitHub] brooklyn-docs pull request #79: Ops guides updates for monitoring and disk s...

Posted by aledsage <gi...@git.apache.org>.

Github user aledsage commented on a diff in the pull request:

    https://github.com/apache/brooklyn-docs/pull/79#discussion_r67827160
  
    --- Diff: guide/ops/requirements.md ---
    @@ -19,6 +19,43 @@ at least 8GB RAM and 100GB disk. The disk is just for logs, a small amount of pe
     any binaries for custom blueprints/integrations.
     
     
    +### Disk Space
    +
    +There are three main consumers of disk space:
    +
    +* **Static files**: these are the Apache Brooklyn files themselves, plus
    --- End diff --
    
    Perhaps reword: the installation and dependencies (e.g. Java). Therefore it would be applicable to RPM installs as well.
    
    Separate point for blueprints added to the catalog. These can include: OSGi bundles for Java-based blueprints or associated resources; and/or jars added to the `lib/dropins/` directory for old-style Java-based blueprints.


---
If your project is set up for it, you can reply to this email and have your
reply appear on GitHub as well. If your project does not have this feature
enabled and wishes so, or if the feature is enabled but not working, please
contact infrastructure at infrastructure@apache.org or file a JIRA ticket
with INFRA.
---

[GitHub] brooklyn-docs pull request #79: Ops guides updates for monitoring and disk s...

Posted by aledsage <gi...@git.apache.org>.

Github user aledsage commented on a diff in the pull request:

    https://github.com/apache/brooklyn-docs/pull/79#discussion_r67830328
  
    --- Diff: guide/ops/starting-stopping-monitoring.md ---
    @@ -0,0 +1,66 @@
    +---
    +title: Starting, Stopping and Monitoring
    +layout: website-normal
    +---
    +
    +**NOTE:** This document is for information on starting an Apache Brooklyn
    +Server.  For information on using the Brooklyn Client CLI to access an already
    +running Brooklyn Server, refer to [Client CLI Reference](cli/index.html).
    +
    +
    +## Starting
    +
    +To launch Brooklyn, from the directory where Brooklyn is unpacked, run:
    +
    +{% highlight bash %}
    +% bin/brooklyn launch > /dev/null 2>&1 & disown
    +{% endhighlight %}
    +
    +With no configuration, this will launch the Brooklyn web console and REST API on [`http://localhost:8081/`](http://localhost:8081/).
    +No password is set, but the server is listening only on the loopback network interface for security.
    +Once [security is configured](brooklyn_properties.html), Brooklyn will listen on all network interfaces by default.
    +
    +See the [Server CLI Reference](server-cli-reference.html) for more information
    +about the Brooklyn server process.
    +
    +The Brooklyn startup script will create a file name `pid_java` at the root of
    +the Brooklyn directory, which contains the PID of the last Brooklyn process to
    +be started.
    +
    +
    +## Stopping
    +
    +To stop Brooklyn, simply send a `TERM` signal to the Brooklyn process. The PID
    +of the most recently run Brooklyn process can be found in the `pid_java` file at
    +the root of the Brooklyn directory.
    +
    +For example:
    +
    +{% highlight bash %}
    +% kill $( cat pid_java )
    +{% endhighlight bash %}
    +
    +
    +## Monitoring
    +
    +As already mentioned, the Brooklyn startup script will create a file name
    +`pid_java` at the root of the Brooklyn directory, which contains the PID of the
    +last Brooklyn process to be started. You can examine this file to discover the
    +PID, and then test that the process is still running.
    +
    +This should lead to a fairly straightforward integration with many monitoring
    +tools - the monitoring tool can discover the expected PID, and can execute the
    +start or stop commands shown above as necessary.
    +
    +For example, here is a fragment of a `monitrc` file as used by [Monit](http://https://mmonit.com/monit/):
    +
    +{% highlight text %}
    +check process apachebrooklyn with pidfile /opt/apache-brooklyn/pid_java
    +    start program = "/bin/bash -c '/opt/apache-brooklyn/bin/brooklyn launch & disown'" with timeout 10 seconds
    --- End diff --
    
    Can we include the `--persist auto` here?


---
If your project is set up for it, you can reply to this email and have your
reply appear on GitHub as well. If your project does not have this feature
enabled and wishes so, or if the feature is enabled but not working, please
contact infrastructure at infrastructure@apache.org or file a JIRA ticket
with INFRA.
---

[GitHub] brooklyn-docs pull request #79: Ops guides updates for monitoring and disk s...

Posted by aledsage <gi...@git.apache.org>.

Github user aledsage commented on a diff in the pull request:

https://github.com/apache/brooklyn-docs/pull/79#discussion_r68123295

--- Diff: guide/ops/requirements.md ---
@@ -19,6 +19,43 @@ at least 8GB RAM and 100GB disk. The disk is just for logs, a small amount of pe
any binaries for custom blueprints/integrations.

+### Disk Space
+
+There are three main consumers of disk space:
+
+* **Static files**: these are the Apache Brooklyn files themselves, plus
+ binaries for custom blueprints and integrations added to the `lib` directory.
+* **Persisted state**: when using [Persistence](persistence/index.html) -- which
+ is a prerequisite for [High Availability](high-availability.html) -- Brooklyn
+ will save data to a store location. Items in the persisted state include
+ metadata about the Brooklyn servers, catalog items, and metadata about all
+ running applications and entities.
+* **Log files**: Brooklyn writes detailed log files by default to its own
+ installation directory. This can be reconfigured to change the destination
+ files, and increase or decrease the detail of the logs. See the
+ [Logging](logging.html) page for more details.
+
+
+The Apache Brooklyn distribution itself, when unpacked, consumes approximately
+75MB of disk space. The space consumed by additional binaries for custom
+blueprints and integrations is application-specific.
+
+Persisted state, excluding catalog data, is relatively small, starting at
+approximately 300KB for a clean, idle Brooklyn server. Deploying blueprints will
+add to this - how much depends exactly on the entities involved and is therefore
+application specific, but as a guideline, a 3-node Riak cluster adds
+approximately 500KB to the persistence store.
+
+Log data can be a large consumer of disk space. By default Brooklyn generates
+two logfiles, one which logs notable information only, and another which logs at
--- End diff --

You're right - I just talked to someone about doing this! It's not been done.

---
If your project is set up for it, you can reply to this email and have your
reply appear on GitHub as well. If your project does not have this feature
enabled and wishes so, or if the feature is enabled but not working, please
contact infrastructure at infrastructure@apache.org or file a JIRA ticket
with INFRA.
---

[GitHub] brooklyn-docs pull request #79: Ops guides updates for monitoring and disk s...

Posted by drigodwin <gi...@git.apache.org>.

Github user drigodwin commented on a diff in the pull request:

    https://github.com/apache/brooklyn-docs/pull/79#discussion_r67713010
  
    --- Diff: guide/ops/starting-stopping-monitoring.md ---
    @@ -0,0 +1,66 @@
    +---
    +title: Starting, Stopping and Monitoring
    +layout: website-normal
    +---
    +
    +**NOTE:** This document is for information on starting an Apache Brooklyn
    +Server.  For information on using the Brooklyn Client CLI to access an already
    +running Brooklyn Server, refer to [Client CLI Reference](cli/index.html).
    +
    +
    +## Starting
    +
    +To launch Brooklyn, from the directory where Brooklyn is unpacked, run:
    +
    +{% highlight bash %}
    +% bin/brooklyn launch > /dev/null 2>&1 & disown
    --- End diff --
    
    Again this is not true when launched as a service


---
If your project is set up for it, you can reply to this email and have your
reply appear on GitHub as well. If your project does not have this feature
enabled and wishes so, or if the feature is enabled but not working, please
contact infrastructure at infrastructure@apache.org or file a JIRA ticket
with INFRA.
---

[GitHub] brooklyn-docs pull request #79: Ops guides updates for monitoring and disk s...

Posted by drigodwin <gi...@git.apache.org>.

Github user drigodwin commented on a diff in the pull request:

https://github.com/apache/brooklyn-docs/pull/79#discussion_r67710473

--- Diff: guide/ops/requirements.md ---
@@ -19,6 +19,43 @@ at least 8GB RAM and 100GB disk. The disk is just for logs, a small amount of pe
any binaries for custom blueprints/integrations.

This is a repeat of [above](https://github.com/apache/brooklyn-docs/pull/79#discussion_r67708812)

[GitHub] brooklyn-docs pull request #79: Ops guides updates for monitoring and disk s...

Posted by aledsage <gi...@git.apache.org>.

Github user aledsage commented on a diff in the pull request:

https://github.com/apache/brooklyn-docs/pull/79#discussion_r67827849

--- Diff: guide/ops/requirements.md ---
@@ -19,6 +19,43 @@ at least 8GB RAM and 100GB disk. The disk is just for logs, a small amount of pe
any binaries for custom blueprints/integrations.

And associated dependencies (i.e. Java).

[GitHub] brooklyn-docs issue #79: Ops guides updates for monitoring and disk space

Posted by rdowner <gi...@git.apache.org>.

Github user rdowner commented on the issue:

    https://github.com/apache/brooklyn-docs/pull/79
  
    @aledsage @drigodwin I've addressed your review comments.


---
If your project is set up for it, you can reply to this email and have your
reply appear on GitHub as well. If your project does not have this feature
enabled and wishes so, or if the feature is enabled but not working, please
contact infrastructure at infrastructure@apache.org or file a JIRA ticket
with INFRA.
---

[GitHub] brooklyn-docs pull request #79: Ops guides updates for monitoring and disk s...

Posted by aledsage <gi...@git.apache.org>.

Github user aledsage commented on a diff in the pull request:

    https://github.com/apache/brooklyn-docs/pull/79#discussion_r67831210
  
    --- Diff: guide/ops/starting-stopping-monitoring.md ---
    @@ -0,0 +1,66 @@
    +---
    +title: Starting, Stopping and Monitoring
    +layout: website-normal
    +---
    +
    +**NOTE:** This document is for information on starting an Apache Brooklyn
    +Server.  For information on using the Brooklyn Client CLI to access an already
    +running Brooklyn Server, refer to [Client CLI Reference](cli/index.html).
    +
    +
    +## Starting
    +
    +To launch Brooklyn, from the directory where Brooklyn is unpacked, run:
    +
    +{% highlight bash %}
    +% bin/brooklyn launch > /dev/null 2>&1 & disown
    +{% endhighlight %}
    +
    +With no configuration, this will launch the Brooklyn web console and REST API on [`http://localhost:8081/`](http://localhost:8081/).
    +No password is set, but the server is listening only on the loopback network interface for security.
    +Once [security is configured](brooklyn_properties.html), Brooklyn will listen on all network interfaces by default.
    +
    +See the [Server CLI Reference](server-cli-reference.html) for more information
    +about the Brooklyn server process.
    +
    +The Brooklyn startup script will create a file name `pid_java` at the root of
    +the Brooklyn directory, which contains the PID of the last Brooklyn process to
    +be started.
    +
    +
    +## Stopping
    +
    +To stop Brooklyn, simply send a `TERM` signal to the Brooklyn process. The PID
    +of the most recently run Brooklyn process can be found in the `pid_java` file at
    +the root of the Brooklyn directory.
    +
    +For example:
    +
    +{% highlight bash %}
    +% kill $( cat pid_java )
    +{% endhighlight bash %}
    +
    +
    +## Monitoring
    +
    +As already mentioned, the Brooklyn startup script will create a file name
    +`pid_java` at the root of the Brooklyn directory, which contains the PID of the
    +last Brooklyn process to be started. You can examine this file to discover the
    +PID, and then test that the process is still running.
    +
    +This should lead to a fairly straightforward integration with many monitoring
    +tools - the monitoring tool can discover the expected PID, and can execute the
    +start or stop commands shown above as necessary.
    +
    +For example, here is a fragment of a `monitrc` file as used by [Monit](http://https://mmonit.com/monit/):
    +
    +{% highlight text %}
    +check process apachebrooklyn with pidfile /opt/apache-brooklyn/pid_java
    +    start program = "/bin/bash -c '/opt/apache-brooklyn/bin/brooklyn launch & disown'" with timeout 10 seconds
    +    stop  program = "/bin/bash -c 'kill $( cat /opt/apache-brooklyn/pid_java )'"
    --- End diff --
    
    (Not necessary for this PR, unless there is a quick answer). What are the best practices for handling missing or stale pid files? Should we `rm` the file?
    
    We'll need to add something about when it's running as a service, but that can be a separate PR.


---
If your project is set up for it, you can reply to this email and have your
reply appear on GitHub as well. If your project does not have this feature
enabled and wishes so, or if the feature is enabled but not working, please
contact infrastructure at infrastructure@apache.org or file a JIRA ticket
with INFRA.
---

[GitHub] brooklyn-docs pull request #79: Ops guides updates for monitoring and disk s...

Posted by drigodwin <gi...@git.apache.org>.

Github user drigodwin commented on a diff in the pull request:

    https://github.com/apache/brooklyn-docs/pull/79#discussion_r67708812
  
    --- Diff: guide/ops/requirements.md ---
    @@ -19,6 +19,43 @@ at least 8GB RAM and 100GB disk. The disk is just for logs, a small amount of pe
     any binaries for custom blueprints/integrations.
     
     
    +### Disk Space
    +
    +There are three main consumers of disk space:
    +
    +* **Static files**: these are the Apache Brooklyn files themselves, plus
    +  binaries for custom blueprints and integrations added to the `lib` directory.
    +* **Persisted state**: when using [Persistence](persistence/index.html) -- which
    +  is a prerequisite for [High Availability](high-availability.html) -- Brooklyn
    +  will save data to a store location. Items in the persisted state include
    +  metadata about the Brooklyn servers, catalog items, and metadata about all
    +  running applications and entities.
    +* **Log files**: Brooklyn writes detailed log files by default to its own
    +  installation directory. This can be reconfigured to change the destination
    --- End diff --
    
    I dont think this is true for the RPM or deb which install services - perhaps add something about where they put logs?


---
If your project is set up for it, you can reply to this email and have your
reply appear on GitHub as well. If your project does not have this feature
enabled and wishes so, or if the feature is enabled but not working, please
contact infrastructure at infrastructure@apache.org or file a JIRA ticket
with INFRA.
---

[GitHub] brooklyn-docs pull request #79: Ops guides updates for monitoring and disk s...

Posted by aledsage <gi...@git.apache.org>.

Github user aledsage commented on a diff in the pull request:

https://github.com/apache/brooklyn-docs/pull/79#discussion_r67828945

--- Diff: guide/ops/requirements.md ---
@@ -19,6 +19,43 @@ at least 8GB RAM and 100GB disk. The disk is just for logs, a small amount of pe
any binaries for custom blueprints/integrations.

Perhaps we should mention some other production-quality logging technologies (e.g. syslog, logstash, splunk, etc).

While you're looking at this, can you double-check and fix this section: http://brooklyn.apache.org/v/latest/ops/logging.html#logging-aggregators. Does one really write to the syslog in order to feed the logs to logstash?! Although that's possible, I'd assume one uses a configuration more like that in https://www.elastic.co/guide/en/logstash/current/config-examples.html (but I'm not certain).

[GitHub] brooklyn-docs pull request #79: Ops guides updates for monitoring and disk s...

Posted by rdowner <gi...@git.apache.org>.

Github user rdowner commented on a diff in the pull request:

https://github.com/apache/brooklyn-docs/pull/79#discussion_r67849723

--- Diff: guide/ops/requirements.md ---
@@ -19,6 +19,43 @@ at least 8GB RAM and 100GB disk. The disk is just for logs, a small amount of pe
any binaries for custom blueprints/integrations.

@aledsage I've checked the master source code - I can see config files for the jclouds logging, but the only reference that includes the jclouds log config is commented out. Are you sure this is enabled by default?

[GitHub] brooklyn-docs pull request #79: Ops guides updates for monitoring and disk s...

Posted by aledsage <gi...@git.apache.org>.

Github user aledsage commented on a diff in the pull request:

https://github.com/apache/brooklyn-docs/pull/79#discussion_r67828097

--- Diff: guide/ops/requirements.md ---
@@ -19,6 +19,43 @@ at least 8GB RAM and 100GB disk. The disk is just for logs, a small amount of pe
any binaries for custom blueprints/integrations.

This has changed recently in master. We now write the jclouds wire log to a separate file.

[GitHub] brooklyn-docs pull request #79: Ops guides updates for monitoring and disk s...

Posted by aledsage <gi...@git.apache.org>.

Github user aledsage commented on a diff in the pull request:

https://github.com/apache/brooklyn-docs/pull/79#discussion_r67827766

--- Diff: guide/ops/requirements.md ---
@@ -19,6 +19,43 @@ at least 8GB RAM and 100GB disk. The disk is just for logs, a small amount of pe
any binaries for custom blueprints/integrations.

Agreed. Perhaps we don't need to say here where it's written to - you've already linked to the logging section. Instead just say:

**Log files**: Brooklyn writes info and debug log files. By default, these are
written to the local filesystem. This can be reconfigured to set the destination
and to increase or decrease the detail in the logs. See the
[Logging](logging.html) section for more details.

[GitHub] brooklyn-docs pull request #79: Ops guides updates for monitoring and disk s...

Posted by aledsage <gi...@git.apache.org>.

Github user aledsage commented on a diff in the pull request:

https://github.com/apache/brooklyn-docs/pull/79#discussion_r67829261

--- Diff: guide/ops/requirements.md ---
@@ -19,6 +19,43 @@ at least 8GB RAM and 100GB disk. The disk is just for logs, a small amount of pe
any binaries for custom blueprints/integrations.

The recommended operating system is CentOS 6.x or RedHat 6.x.
--- End diff --

At some point we should add CentOS 7.x, but let's not do that yet.

Can you change the line below this to Ubuntu 14.04 please (rather than 12.04).

[GitHub] brooklyn-docs pull request #79: Ops guides updates for monitoring and disk s...

Posted by asfgit <gi...@git.apache.org>.

Github user asfgit closed the pull request at:

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


---
If your project is set up for it, you can reply to this email and have your
reply appear on GitHub as well. If your project does not have this feature
enabled and wishes so, or if the feature is enabled but not working, please
contact infrastructure at infrastructure@apache.org or file a JIRA ticket
with INFRA.
---