brooklyn-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From aledsage <>
Subject [GitHub] brooklyn-docs pull request #78: Adds details of setting up a HA master-slave...
Date Wed, 22 Jun 2016 19:32:55 GMT
Github user aledsage commented on a diff in the pull request:
    --- Diff: guide/ops/high-availability/ ---
    @@ -0,0 +1,142 @@
    +title: High Availability (Supplemental)
    +layout: website-normal
    +This document supplements the High Availability documentation available [here](
    +and provides an example of how to configure a pair of Apache Brooklyn servers to run
in master-standby mode with a shared NFS datastore
    +### Prerequisites
    +- Two VMs (or physical machines) have been provisioned
    +- NFS or another suitable file system has been configured and is available to both VMs*
    +- An NFS folder has been mounted on both VMs at `/mnt/brooklyn-persistence` and both
machines can write to the folder
    +\* Brooklyn can be configured to use either an object store such as S3, or a shared NFS
mount. The recommended option is to use an object
    +store as described in the [Object Store Persistence](./persistence/#object-store-persistence)
documentation. For clarity, a shared NFS folder
    +is assumed in this example
    +### Launching
    +To start, download and install the latest Apache Brooklyn release on both VMs following
the 'OSX / Linux' section
    +of the [Running Apache Brooklyn](../start/running.html#install-apache-brooklyn) documentation
    +On the first VM, which will be the master node, run the following to start Brooklyn in
high availability mode:
    +{% highlight bash %}
    +$ bin/brooklyn launch --highAvailability master --persist auto --persistenceDir /mnt/brooklyn-persistence
    --- End diff --
    Given this is docs for production, let's use `--https` (and use port 8443 below).

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 or file a JIRA ticket
with INFRA.

View raw message