Mailing-List: contact dev-help@brooklyn.apache.org; run by ezmlm
Precedence: bulk
Reply-To: dev@brooklyn.apache.org
From: aledsage <git@git.apache.org>
To: dev@brooklyn.apache.org
Reply-To: dev@brooklyn.apache.org
References: <git-pr-79-brooklyn-docs@git.apache.org>
In-Reply-To: <git-pr-79-brooklyn-docs@git.apache.org>
Subject: [GitHub] brooklyn-docs pull request #79: Ops guides updates for monitoring and disk s...
Content-Type: text/plain
Message-Id: <20160621082941.6C2CEE020A@git1-us-west.apache.org>
Date: Tue, 21 Jun 2016 08:29:41 +0000 (UTC)
archived-at: Tue, 21 Jun 2016 08:29:43 -0000

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