You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@brooklyn.apache.org by bostko <gi...@git.apache.org> on 2017/01/26 08:26:46 UTC
[GitHub] brooklyn-docs pull request #143: Update RAM and Disk requirements
GitHub user bostko opened a pull request:
https://github.com/apache/brooklyn-docs/pull/143
Update RAM and Disk requirements
You can merge this pull request into a Git repository by running:
$ git pull https://github.com/bostko/brooklyn-docs update-requirements
Alternatively you can review and apply these changes as the patch at:
https://github.com/apache/brooklyn-docs/pull/143.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 #143
----
commit 55e2afd6de0a8dda0cd24a82c573b03526417285
Author: Valentin Aitken <bo...@gmail.com>
Date: 2017-01-26T08:26:06Z
Update RAM and Disk requirements
----
---
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 #143: Update disk usage explanation
Posted by neykov <gi...@git.apache.org>.
Github user neykov commented on a diff in the pull request:
https://github.com/apache/brooklyn-docs/pull/143#discussion_r97998577
--- Diff: guide/ops/requirements.md ---
@@ -24,8 +24,8 @@ any binaries for custom blueprints/integrations.
There are three main consumers of disk space:
* **Static files**: these are the Apache Brooklyn distribution with its own
- dependencies, plus binaries for custom blueprints and integrations added to
- the `lib` directory. Note that Brooklyn requires that Java is installed which
+ dependencies, plus OSGi bundles for custom blueprints and integrations added to
+ the `data/cache` directory. Note that Brooklyn requires that Java is installed which
--- End diff --
Custom bundles would be added to `deploy` folder, `data/cache` is an internal detail.
---
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 #143: Update disk usage explanation
Posted by drigodwin <gi...@git.apache.org>.
Github user drigodwin commented on the issue:
https://github.com/apache/brooklyn-docs/pull/143
This change is only true for the Karaf distibution of Apache Brooklyn. This is not the default so I would suggest holding off merging this PR until it is.
---
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 #143: Update disk usage explanation
Posted by tbouron <gi...@git.apache.org>.
Github user tbouron commented on the issue:
https://github.com/apache/brooklyn-docs/pull/143
Now that Brooklyn uses Karaf as default launcher, we should probably merge this @drigodwin
---
[GitHub] brooklyn-docs pull request #143: Update RAM and Disk requirements
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/143#discussion_r97959750
--- Diff: guide/ops/requirements.md ---
@@ -12,7 +12,7 @@ The size of server required by Brooklyn depends on the amount of activity. This
* the amount of management and monitoring required per entity
For dev/test or when there are only a handful of VMs being managed, a small VM is sufficient.
-For example, an AWS m3.medium with one vCPU, 3.75GiB RAM and 4GB disk.
+For example, an AWS m3.medium with one vCPU, 6GiB RAM and 8GB disk.
--- End diff --
The previous values were correct for `m3.medium` see: https://aws.amazon.com/ec2/instance-types/#m3
---
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 #143: Update disk usage explanation
Posted by asfgit <gi...@git.apache.org>.
Github user asfgit closed the pull request at:
https://github.com/apache/brooklyn-docs/pull/143
---