[GitHub] brooklyn-docs pull request #78: Adds details of setting up a HA master-slave...

2016-06-23 Thread asfgit 
Github user asfgit closed the pull request at:

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


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

[GitHub] brooklyn-docs pull request #78: Adds details of setting up a HA master-slave...

2016-06-22 Thread aledsage 
Github user aledsage commented on a diff in the pull request:

https://github.com/apache/brooklyn-docs/pull/78#discussion_r68122663
  
--- Diff: guide/ops/high-availability/high-availability-supplemental.md ---
@@ -0,0 +1,142 @@
+---
+title: High Availability (Supplemental)
+layout: website-normal
+---
+
+This document supplements the High Availability documentation available 
[here](http://brooklyn.apache.org/v/latest/ops/high-availability.html)
+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
+{% endhighlight %}
+
+Once Brooklyn has launched, on the second VM, run the following command to 
launch Brooklyn in standby mode:
+
+{% highlight bash %}
+$ bin/brooklyn launch --highAvailability auto --persist auto 
--persistenceDir /mnt/brooklyn-persistence
+{% endhighlight %}
+
+### Testing
+You can now confirm that Brooklyn is running in high availibility mode on 
the master by logging into the web console at `http://:8081`.
+Similarly you can log into the web console on the standby VM where you 
will see a warning that the server is not the high availability master.
+To test a failover, you can simply terminate the process on the first VM 
and log into the web console on the second VM. Upon launch, Brooklyn will
+output its PID to the file `pid.txt`; you can terminate the process by 
running the following command from the same directory from which you 
+launched Brooklyn:
+
+{% highlight bash %}
+$ kill -9 $(cat pid.txt)
+{% endhighlight %}
+
+It is also possiblity to check the high availability state of a running 
Brooklyn server using the following curl command:
+
+{% highlight bash %}
+$ curl -u myusername:mypassword http://:8081/v1/server/ha/state
+{% endhighlight %}
+
+This will return one of the following states:
+
+{% highlight bash %}
+
+"INITIALIZING"
+"STANDBY"
+"HOT_STANDBY"
+"HOT_BACKUP"
+"MASTER"
+"FAILED"
+"TERMINATED"
+
+{% endhighlight %}
+
+Note: The quotation characters will be included in the reply
+
+To obtain information about all of the nodes in the cluster, run the 
following command against any of the nodes in the cluster:
+
+{% highlight bash %}
+$ curl -u myusername:mypassword 
http://:8081/v1/server/ha/states
+{% endhighlight %}
+
+This will return a JSON document describing the Brooklyn nodes in the 
cluster. An example of two HA Brooklyn nodes is as follows (whitespace 
formatting has been
+added for clarity):
+
+{% highlight yaml %}
+
+{
+  ownId: "XkJeXUXE",
+  masterId: "yAVz0fzo",
+  nodes: {
+yAVz0fzo: {
+  nodeId: "yAVz0fzo",
+  nodeUri: "http://:8081/",
+  status: "MASTER",
+  localTimestamp: 1466414301065,
+  remoteTimestamp: 1466414301000
+},
+XkJeXUXE: {
+  nodeId: "XkJeXUXE",
+  nodeUri: "http://:8081/",
+  status: "STANDBY",
+  localTimestamp: 1466414301066,
+  remoteTimestamp: 1466414301000
+}
+  },
+  links: { }
+}
+
+{% endhighlight %}
+
+The examples above show how to use `curl` to manually check the status of 
Brooklyn via its REST API. The same REST API calls can also be used by
+automated third party monitoring tools such as Monit 
+
+### Failover
+When running as a HA standby node, each standby Brooklyn server (in this 
case there is only one standby) will check the shared persisted state
+every 1 second to determine the state of the HA master. If no heartbeat 
has been recorded for thirty seconds, then an election will be

[GitHub] brooklyn-docs pull request #78: Adds details of setting up a HA master-slave...

2016-06-22 Thread aledsage 
Github user aledsage commented on a diff in the pull request:

https://github.com/apache/brooklyn-docs/pull/78#discussion_r68122294
  
--- Diff: guide/ops/high-availability/high-availability-supplemental.md ---
@@ -0,0 +1,142 @@
+---
+title: High Availability (Supplemental)
+layout: website-normal
+---
+
+This document supplements the High Availability documentation available 
[here](http://brooklyn.apache.org/v/latest/ops/high-availability.html)
+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
+{% endhighlight %}
+
+Once Brooklyn has launched, on the second VM, run the following command to 
launch Brooklyn in standby mode:
+
+{% highlight bash %}
+$ bin/brooklyn launch --highAvailability auto --persist auto 
--persistenceDir /mnt/brooklyn-persistence
+{% endhighlight %}
+
+### Testing
+You can now confirm that Brooklyn is running in high availibility mode on 
the master by logging into the web console at `http://:8081`.
+Similarly you can log into the web console on the standby VM where you 
will see a warning that the server is not the high availability master.
+To test a failover, you can simply terminate the process on the first VM 
and log into the web console on the second VM. Upon launch, Brooklyn will
+output its PID to the file `pid.txt`; you can terminate the process by 
running the following command from the same directory from which you 
+launched Brooklyn:
+
+{% highlight bash %}
+$ kill -9 $(cat pid.txt)
+{% endhighlight %}
+
+It is also possiblity to check the high availability state of a running 
Brooklyn server using the following curl command:
+
+{% highlight bash %}
+$ curl -u myusername:mypassword http://:8081/v1/server/ha/state
+{% endhighlight %}
+
+This will return one of the following states:
+
+{% highlight bash %}
+
+"INITIALIZING"
+"STANDBY"
+"HOT_STANDBY"
+"HOT_BACKUP"
+"MASTER"
+"FAILED"
+"TERMINATED"
+
+{% endhighlight %}
+
+Note: The quotation characters will be included in the reply
+
+To obtain information about all of the nodes in the cluster, run the 
following command against any of the nodes in the cluster:
+
+{% highlight bash %}
+$ curl -u myusername:mypassword 
http://:8081/v1/server/ha/states
+{% endhighlight %}
+
+This will return a JSON document describing the Brooklyn nodes in the 
cluster. An example of two HA Brooklyn nodes is as follows (whitespace 
formatting has been
+added for clarity):
+
+{% highlight yaml %}
+
+{
+  ownId: "XkJeXUXE",
+  masterId: "yAVz0fzo",
+  nodes: {
+yAVz0fzo: {
+  nodeId: "yAVz0fzo",
+  nodeUri: "http://:8081/",
+  status: "MASTER",
+  localTimestamp: 1466414301065,
+  remoteTimestamp: 1466414301000
+},
+XkJeXUXE: {
+  nodeId: "XkJeXUXE",
+  nodeUri: "http://:8081/",
+  status: "STANDBY",
+  localTimestamp: 1466414301066,
+  remoteTimestamp: 1466414301000
+}
+  },
+  links: { }
+}
+
+{% endhighlight %}
+
+The examples above show how to use `curl` to manually check the status of 
Brooklyn via its REST API. The same REST API calls can also be used by
+automated third party monitoring tools such as Monit 
+
+### Failover
+When running as a HA standby node, each standby Brooklyn server (in this 
case there is only one standby) will check the shared persisted state
+every 1 second to determine the state of the HA master. If no heartbeat 
has been recorded for thirty seconds, then an election will be

[GitHub] brooklyn-docs pull request #78: Adds details of setting up a HA master-slave...

2016-06-22 Thread aledsage 
Github user aledsage commented on a diff in the pull request:

https://github.com/apache/brooklyn-docs/pull/78#discussion_r68122178
  
--- Diff: guide/ops/high-availability/high-availability-supplemental.md ---
@@ -0,0 +1,142 @@
+---
+title: High Availability (Supplemental)
+layout: website-normal
+---
+
+This document supplements the High Availability documentation available 
[here](http://brooklyn.apache.org/v/latest/ops/high-availability.html)
+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
+{% endhighlight %}
+
+Once Brooklyn has launched, on the second VM, run the following command to 
launch Brooklyn in standby mode:
+
+{% highlight bash %}
+$ bin/brooklyn launch --highAvailability auto --persist auto 
--persistenceDir /mnt/brooklyn-persistence
+{% endhighlight %}
+
+### Testing
+You can now confirm that Brooklyn is running in high availibility mode on 
the master by logging into the web console at `http://:8081`.
+Similarly you can log into the web console on the standby VM where you 
will see a warning that the server is not the high availability master.
+To test a failover, you can simply terminate the process on the first VM 
and log into the web console on the second VM. Upon launch, Brooklyn will
+output its PID to the file `pid.txt`; you can terminate the process by 
running the following command from the same directory from which you 
+launched Brooklyn:
+
+{% highlight bash %}
+$ kill -9 $(cat pid.txt)
+{% endhighlight %}
+
+It is also possiblity to check the high availability state of a running 
Brooklyn server using the following curl command:
+
+{% highlight bash %}
+$ curl -u myusername:mypassword http://:8081/v1/server/ha/state
+{% endhighlight %}
+
+This will return one of the following states:
+
+{% highlight bash %}
+
+"INITIALIZING"
+"STANDBY"
+"HOT_STANDBY"
+"HOT_BACKUP"
+"MASTER"
+"FAILED"
+"TERMINATED"
+
+{% endhighlight %}
+
+Note: The quotation characters will be included in the reply
+
+To obtain information about all of the nodes in the cluster, run the 
following command against any of the nodes in the cluster:
+
+{% highlight bash %}
+$ curl -u myusername:mypassword 
http://:8081/v1/server/ha/states
+{% endhighlight %}
+
+This will return a JSON document describing the Brooklyn nodes in the 
cluster. An example of two HA Brooklyn nodes is as follows (whitespace 
formatting has been
+added for clarity):
+
+{% highlight yaml %}
+
+{
+  ownId: "XkJeXUXE",
+  masterId: "yAVz0fzo",
+  nodes: {
+yAVz0fzo: {
+  nodeId: "yAVz0fzo",
+  nodeUri: "http://:8081/",
+  status: "MASTER",
+  localTimestamp: 1466414301065,
+  remoteTimestamp: 1466414301000
+},
+XkJeXUXE: {
+  nodeId: "XkJeXUXE",
+  nodeUri: "http://:8081/",
+  status: "STANDBY",
+  localTimestamp: 1466414301066,
+  remoteTimestamp: 1466414301000
+}
+  },
+  links: { }
+}
+
+{% endhighlight %}
+
+The examples above show how to use `curl` to manually check the status of 
Brooklyn via its REST API. The same REST API calls can also be used by
+automated third party monitoring tools such as Monit 
+
+### Failover
+When running as a HA standby node, each standby Brooklyn server (in this 
case there is only one standby) will check the shared persisted state
+every 1 second to determine the state of the HA master. If no heartbeat 
has been recorded for thirty seconds, then an election will be

[GitHub] brooklyn-docs pull request #78: Adds details of setting up a HA master-slave...

2016-06-22 Thread aledsage 
Github user aledsage commented on a diff in the pull request:

https://github.com/apache/brooklyn-docs/pull/78#discussion_r68122041
  
--- Diff: guide/ops/high-availability/high-availability-supplemental.md ---
@@ -0,0 +1,142 @@
+---
+title: High Availability (Supplemental)
+layout: website-normal
+---
+
+This document supplements the High Availability documentation available 
[here](http://brooklyn.apache.org/v/latest/ops/high-availability.html)
+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
+{% endhighlight %}
+
+Once Brooklyn has launched, on the second VM, run the following command to 
launch Brooklyn in standby mode:
+
+{% highlight bash %}
+$ bin/brooklyn launch --highAvailability auto --persist auto 
--persistenceDir /mnt/brooklyn-persistence
+{% endhighlight %}
+
+### Testing
+You can now confirm that Brooklyn is running in high availibility mode on 
the master by logging into the web console at `http://:8081`.
+Similarly you can log into the web console on the standby VM where you 
will see a warning that the server is not the high availability master.
+To test a failover, you can simply terminate the process on the first VM 
and log into the web console on the second VM. Upon launch, Brooklyn will
+output its PID to the file `pid.txt`; you can terminate the process by 
running the following command from the same directory from which you 
+launched Brooklyn:
+
+{% highlight bash %}
+$ kill -9 $(cat pid.txt)
+{% endhighlight %}
+
+It is also possiblity to check the high availability state of a running 
Brooklyn server using the following curl command:
+
+{% highlight bash %}
+$ curl -u myusername:mypassword http://:8081/v1/server/ha/state
+{% endhighlight %}
+
+This will return one of the following states:
+
+{% highlight bash %}
+
+"INITIALIZING"
+"STANDBY"
+"HOT_STANDBY"
+"HOT_BACKUP"
+"MASTER"
+"FAILED"
+"TERMINATED"
+
+{% endhighlight %}
+
+Note: The quotation characters will be included in the reply
+
+To obtain information about all of the nodes in the cluster, run the 
following command against any of the nodes in the cluster:
+
+{% highlight bash %}
+$ curl -u myusername:mypassword 
http://:8081/v1/server/ha/states
+{% endhighlight %}
+
+This will return a JSON document describing the Brooklyn nodes in the 
cluster. An example of two HA Brooklyn nodes is as follows (whitespace 
formatting has been
+added for clarity):
+
+{% highlight yaml %}
+
+{
+  ownId: "XkJeXUXE",
+  masterId: "yAVz0fzo",
+  nodes: {
+yAVz0fzo: {
+  nodeId: "yAVz0fzo",
+  nodeUri: "http://:8081/",
+  status: "MASTER",
+  localTimestamp: 1466414301065,
+  remoteTimestamp: 1466414301000
+},
+XkJeXUXE: {
+  nodeId: "XkJeXUXE",
+  nodeUri: "http://:8081/",
+  status: "STANDBY",
+  localTimestamp: 1466414301066,
+  remoteTimestamp: 1466414301000
+}
+  },
+  links: { }
+}
+
+{% endhighlight %}
+
+The examples above show how to use `curl` to manually check the status of 
Brooklyn via its REST API. The same REST API calls can also be used by
+automated third party monitoring tools such as Monit 
+
+### Failover
+When running as a HA standby node, each standby Brooklyn server (in this 
case there is only one standby) will check the shared persisted state
+every 1 second to determine the state of the HA master. If no heartbeat 
has been recorded for thirty seconds, then an election will be

[GitHub] brooklyn-docs pull request #78: Adds details of setting up a HA master-slave...

2016-06-22 Thread aledsage 
Github user aledsage commented on a diff in the pull request:

https://github.com/apache/brooklyn-docs/pull/78#discussion_r68121515
  
--- Diff: guide/ops/high-availability/high-availability-supplemental.md ---
@@ -0,0 +1,142 @@
+---
+title: High Availability (Supplemental)
+layout: website-normal
+---
+
+This document supplements the High Availability documentation available 
[here](http://brooklyn.apache.org/v/latest/ops/high-availability.html)
+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
+{% endhighlight %}
+
+Once Brooklyn has launched, on the second VM, run the following command to 
launch Brooklyn in standby mode:
+
+{% highlight bash %}
+$ bin/brooklyn launch --highAvailability auto --persist auto 
--persistenceDir /mnt/brooklyn-persistence
+{% endhighlight %}
+
+### Testing
+You can now confirm that Brooklyn is running in high availibility mode on 
the master by logging into the web console at `http://:8081`.
+Similarly you can log into the web console on the standby VM where you 
will see a warning that the server is not the high availability master.
+To test a failover, you can simply terminate the process on the first VM 
and log into the web console on the second VM. Upon launch, Brooklyn will
+output its PID to the file `pid.txt`; you can terminate the process by 
running the following command from the same directory from which you 
+launched Brooklyn:
+
+{% highlight bash %}
+$ kill -9 $(cat pid.txt)
+{% endhighlight %}
+
+It is also possiblity to check the high availability state of a running 
Brooklyn server using the following curl command:
+
+{% highlight bash %}
+$ curl -u myusername:mypassword http://:8081/v1/server/ha/state
+{% endhighlight %}
+
+This will return one of the following states:
+
+{% highlight bash %}
+
+"INITIALIZING"
+"STANDBY"
+"HOT_STANDBY"
+"HOT_BACKUP"
+"MASTER"
+"FAILED"
+"TERMINATED"
+
+{% endhighlight %}
+
+Note: The quotation characters will be included in the reply
+
+To obtain information about all of the nodes in the cluster, run the 
following command against any of the nodes in the cluster:
+
+{% highlight bash %}
+$ curl -u myusername:mypassword 
http://:8081/v1/server/ha/states
+{% endhighlight %}
+
+This will return a JSON document describing the Brooklyn nodes in the 
cluster. An example of two HA Brooklyn nodes is as follows (whitespace 
formatting has been
+added for clarity):
+
+{% highlight yaml %}
+
+{
+  ownId: "XkJeXUXE",
+  masterId: "yAVz0fzo",
+  nodes: {
+yAVz0fzo: {
+  nodeId: "yAVz0fzo",
+  nodeUri: "http://:8081/",
+  status: "MASTER",
+  localTimestamp: 1466414301065,
+  remoteTimestamp: 1466414301000
+},
+XkJeXUXE: {
+  nodeId: "XkJeXUXE",
+  nodeUri: "http://:8081/",
+  status: "STANDBY",
+  localTimestamp: 1466414301066,
+  remoteTimestamp: 1466414301000
+}
+  },
+  links: { }
+}
+
+{% endhighlight %}
+
+The examples above show how to use `curl` to manually check the status of 
Brooklyn via its REST API. The same REST API calls can also be used by
+automated third party monitoring tools such as Monit 
+
+### Failover
+When running as a HA standby node, each standby Brooklyn server (in this 
case there is only one standby) will check the shared persisted state
+every 1 second to determine the state of the HA master. If no heartbeat 
has been recorded for thirty seconds, then an election will be

[GitHub] brooklyn-docs pull request #78: Adds details of setting up a HA master-slave...

2016-06-22 Thread aledsage 
Github user aledsage commented on a diff in the pull request:

https://github.com/apache/brooklyn-docs/pull/78#discussion_r68121310
  
--- Diff: guide/ops/high-availability/high-availability-supplemental.md ---
@@ -0,0 +1,142 @@
+---
+title: High Availability (Supplemental)
+layout: website-normal
+---
+
+This document supplements the High Availability documentation available 
[here](http://brooklyn.apache.org/v/latest/ops/high-availability.html)
+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
+{% endhighlight %}
+
+Once Brooklyn has launched, on the second VM, run the following command to 
launch Brooklyn in standby mode:
+
+{% highlight bash %}
+$ bin/brooklyn launch --highAvailability auto --persist auto 
--persistenceDir /mnt/brooklyn-persistence
+{% endhighlight %}
+
+### Testing
+You can now confirm that Brooklyn is running in high availibility mode on 
the master by logging into the web console at `http://:8081`.
+Similarly you can log into the web console on the standby VM where you 
will see a warning that the server is not the high availability master.
+To test a failover, you can simply terminate the process on the first VM 
and log into the web console on the second VM. Upon launch, Brooklyn will
+output its PID to the file `pid.txt`; you can terminate the process by 
running the following command from the same directory from which you 
+launched Brooklyn:
+
+{% highlight bash %}
+$ kill -9 $(cat pid.txt)
+{% endhighlight %}
+
+It is also possiblity to check the high availability state of a running 
Brooklyn server using the following curl command:
+
+{% highlight bash %}
+$ curl -u myusername:mypassword http://:8081/v1/server/ha/state
+{% endhighlight %}
+
+This will return one of the following states:
+
+{% highlight bash %}
+
+"INITIALIZING"
+"STANDBY"
+"HOT_STANDBY"
+"HOT_BACKUP"
+"MASTER"
+"FAILED"
+"TERMINATED"
+
+{% endhighlight %}
+
+Note: The quotation characters will be included in the reply
+
+To obtain information about all of the nodes in the cluster, run the 
following command against any of the nodes in the cluster:
+
+{% highlight bash %}
+$ curl -u myusername:mypassword 
http://:8081/v1/server/ha/states
+{% endhighlight %}
+
+This will return a JSON document describing the Brooklyn nodes in the 
cluster. An example of two HA Brooklyn nodes is as follows (whitespace 
formatting has been
+added for clarity):
+
+{% highlight yaml %}
+
+{
+  ownId: "XkJeXUXE",
+  masterId: "yAVz0fzo",
+  nodes: {
+yAVz0fzo: {
+  nodeId: "yAVz0fzo",
+  nodeUri: "http://:8081/",
+  status: "MASTER",
+  localTimestamp: 1466414301065,
+  remoteTimestamp: 1466414301000
+},
+XkJeXUXE: {
+  nodeId: "XkJeXUXE",
+  nodeUri: "http://:8081/",
+  status: "STANDBY",
+  localTimestamp: 1466414301066,
+  remoteTimestamp: 1466414301000
+}
+  },
+  links: { }
+}
+
+{% endhighlight %}
+
+The examples above show how to use `curl` to manually check the status of 
Brooklyn via its REST API. The same REST API calls can also be used by
+automated third party monitoring tools such as Monit 
+
+### Failover
+When running as a HA standby node, each standby Brooklyn server (in this 
case there is only one standby) will check the shared persisted state
+every 1 second to determine the state of the HA master. If no heartbeat 
has been recorded for thirty seconds, then an election will be

[GitHub] brooklyn-docs pull request #78: Adds details of setting up a HA master-slave...

2016-06-22 Thread aledsage 
Github user aledsage commented on a diff in the pull request:

https://github.com/apache/brooklyn-docs/pull/78#discussion_r68121198
  
--- Diff: guide/ops/high-availability/high-availability-supplemental.md ---
@@ -0,0 +1,142 @@
+---
+title: High Availability (Supplemental)
+layout: website-normal
+---
+
+This document supplements the High Availability documentation available 
[here](http://brooklyn.apache.org/v/latest/ops/high-availability.html)
+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
+{% endhighlight %}
+
+Once Brooklyn has launched, on the second VM, run the following command to 
launch Brooklyn in standby mode:
+
+{% highlight bash %}
+$ bin/brooklyn launch --highAvailability auto --persist auto 
--persistenceDir /mnt/brooklyn-persistence
+{% endhighlight %}
+
+### Testing
+You can now confirm that Brooklyn is running in high availibility mode on 
the master by logging into the web console at `http://:8081`.
+Similarly you can log into the web console on the standby VM where you 
will see a warning that the server is not the high availability master.
+To test a failover, you can simply terminate the process on the first VM 
and log into the web console on the second VM. Upon launch, Brooklyn will
+output its PID to the file `pid.txt`; you can terminate the process by 
running the following command from the same directory from which you 
+launched Brooklyn:
+
+{% highlight bash %}
+$ kill -9 $(cat pid.txt)
+{% endhighlight %}
+
+It is also possiblity to check the high availability state of a running 
Brooklyn server using the following curl command:
+
+{% highlight bash %}
+$ curl -u myusername:mypassword http://:8081/v1/server/ha/state
+{% endhighlight %}
+
+This will return one of the following states:
+
+{% highlight bash %}
+
+"INITIALIZING"
+"STANDBY"
+"HOT_STANDBY"
+"HOT_BACKUP"
+"MASTER"
+"FAILED"
+"TERMINATED"
+
+{% endhighlight %}
+
+Note: The quotation characters will be included in the reply
+
+To obtain information about all of the nodes in the cluster, run the 
following command against any of the nodes in the cluster:
+
+{% highlight bash %}
+$ curl -u myusername:mypassword 
http://:8081/v1/server/ha/states
+{% endhighlight %}
+
+This will return a JSON document describing the Brooklyn nodes in the 
cluster. An example of two HA Brooklyn nodes is as follows (whitespace 
formatting has been
+added for clarity):
+
+{% highlight yaml %}
+
+{
+  ownId: "XkJeXUXE",
+  masterId: "yAVz0fzo",
+  nodes: {
+yAVz0fzo: {
+  nodeId: "yAVz0fzo",
+  nodeUri: "http://:8081/",
+  status: "MASTER",
+  localTimestamp: 1466414301065,
+  remoteTimestamp: 1466414301000
+},
+XkJeXUXE: {
+  nodeId: "XkJeXUXE",
+  nodeUri: "http://:8081/",
+  status: "STANDBY",
+  localTimestamp: 1466414301066,
+  remoteTimestamp: 1466414301000
+}
+  },
+  links: { }
+}
+
+{% endhighlight %}
+
+The examples above show how to use `curl` to manually check the status of 
Brooklyn via its REST API. The same REST API calls can also be used by
+automated third party monitoring tools such as Monit 
+
+### Failover
+When running as a HA standby node, each standby Brooklyn server (in this 
case there is only one standby) will check the shared persisted state
+every 1 second to determine the state of the HA master. If no heartbeat 
has been recorded for thirty seconds, then an election will be

[GitHub] brooklyn-docs pull request #78: Adds details of setting up a HA master-slave...

2016-06-22 Thread aledsage 
Github user aledsage commented on a diff in the pull request:

https://github.com/apache/brooklyn-docs/pull/78#discussion_r68120968
  
--- Diff: guide/ops/high-availability/high-availability-supplemental.md ---
@@ -0,0 +1,142 @@
+---
+title: High Availability (Supplemental)
+layout: website-normal
+---
+
+This document supplements the High Availability documentation available 
[here](http://brooklyn.apache.org/v/latest/ops/high-availability.html)
+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
+{% endhighlight %}
+
+Once Brooklyn has launched, on the second VM, run the following command to 
launch Brooklyn in standby mode:
+
+{% highlight bash %}
+$ bin/brooklyn launch --highAvailability auto --persist auto 
--persistenceDir /mnt/brooklyn-persistence
+{% endhighlight %}
+
+### Testing
+You can now confirm that Brooklyn is running in high availibility mode on 
the master by logging into the web console at `http://:8081`.
+Similarly you can log into the web console on the standby VM where you 
will see a warning that the server is not the high availability master.
+To test a failover, you can simply terminate the process on the first VM 
and log into the web console on the second VM. Upon launch, Brooklyn will
--- End diff --

Ah, I see you have this already in the "Failover" section.

Maybe re-order this, so that the testing section comes after "Failover", 
but before "Client configuration".

You could have a "Monitoring" section here though, that says about the 
web-console and has the curl commands.


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

[GitHub] brooklyn-docs pull request #78: Adds details of setting up a HA master-slave...

2016-06-22 Thread aledsage 
Github user aledsage commented on a diff in the pull request:

https://github.com/apache/brooklyn-docs/pull/78#discussion_r68120602
  
--- Diff: guide/ops/high-availability/high-availability-supplemental.md ---
@@ -0,0 +1,142 @@
+---
+title: High Availability (Supplemental)
+layout: website-normal
+---
+
+This document supplements the High Availability documentation available 
[here](http://brooklyn.apache.org/v/latest/ops/high-availability.html)
+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
+{% endhighlight %}
+
+Once Brooklyn has launched, on the second VM, run the following command to 
launch Brooklyn in standby mode:
+
+{% highlight bash %}
+$ bin/brooklyn launch --highAvailability auto --persist auto 
--persistenceDir /mnt/brooklyn-persistence
+{% endhighlight %}
+
+### Testing
+You can now confirm that Brooklyn is running in high availibility mode on 
the master by logging into the web console at `http://:8081`.
+Similarly you can log into the web console on the standby VM where you 
will see a warning that the server is not the high availability master.
+To test a failover, you can simply terminate the process on the first VM 
and log into the web console on the second VM. Upon launch, Brooklyn will
--- End diff --

I'd add: If the master is terminated gracefully, the secondary will be 
immediately promoted to mater. Otherwise, the secondary will be promoted after 
heartbeats are missed for a given length of time. This defaults to thirty 
seconds, and is configured in brooklyn.properties using 
`brooklyn.ha.heartbeatTimeout`.

Perhaps miss out the `kill` command here - it's described in the docs that 
@rdowner contributed (though without the `-9`)?


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

[GitHub] brooklyn-docs pull request #78: Adds details of setting up a HA master-slave...

2016-06-22 Thread aledsage 
Github user aledsage commented on a diff in the pull request:

https://github.com/apache/brooklyn-docs/pull/78#discussion_r68120636
  
--- Diff: guide/ops/high-availability/high-availability-supplemental.md ---
@@ -0,0 +1,142 @@
+---
+title: High Availability (Supplemental)
+layout: website-normal
+---
+
+This document supplements the High Availability documentation available 
[here](http://brooklyn.apache.org/v/latest/ops/high-availability.html)
+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
+{% endhighlight %}
+
+Once Brooklyn has launched, on the second VM, run the following command to 
launch Brooklyn in standby mode:
+
+{% highlight bash %}
+$ bin/brooklyn launch --highAvailability auto --persist auto 
--persistenceDir /mnt/brooklyn-persistence
+{% endhighlight %}
+
+### Testing
+You can now confirm that Brooklyn is running in high availibility mode on 
the master by logging into the web console at `http://:8081`.
+Similarly you can log into the web console on the standby VM where you 
will see a warning that the server is not the high availability master.
+To test a failover, you can simply terminate the process on the first VM 
and log into the web console on the second VM. Upon launch, Brooklyn will
+output its PID to the file `pid.txt`; you can terminate the process by 
running the following command from the same directory from which you 
+launched Brooklyn:
+
+{% highlight bash %}
+$ kill -9 $(cat pid.txt)
+{% endhighlight %}
+
+It is also possiblity to check the high availability state of a running 
Brooklyn server using the following curl command:
+
+{% highlight bash %}
+$ curl -u myusername:mypassword http://:8081/v1/server/ha/state
--- End diff --

again https and 8443


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

[GitHub] brooklyn-docs pull request #78: Adds details of setting up a HA master-slave...

2016-06-22 Thread aledsage 
Github user aledsage commented on a diff in the pull request:

https://github.com/apache/brooklyn-docs/pull/78#discussion_r68119110
  
--- Diff: guide/ops/high-availability/high-availability-supplemental.md ---
@@ -0,0 +1,142 @@
+---
+title: High Availability (Supplemental)
+layout: website-normal
+---
+
+This document supplements the High Availability documentation available 
[here](http://brooklyn.apache.org/v/latest/ops/high-availability.html)
--- End diff --

Use `This document supplements the [High Availability]]({{ site.path.guide 
}}/ops/high-availability.html) documentation.` Don't use absolute links to 
things in the docs; and I have a personal preference for the link not being 
"here", but being the name of what it's linking to.


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

[GitHub] brooklyn-docs pull request #78: Adds details of setting up a HA master-slave...

2016-06-22 Thread aledsage 
Github user aledsage commented on a diff in the pull request:

https://github.com/apache/brooklyn-docs/pull/78#discussion_r68119573
  
--- Diff: guide/ops/high-availability/high-availability-supplemental.md ---
@@ -0,0 +1,142 @@
+---
+title: High Availability (Supplemental)
+layout: website-normal
+---
+
+This document supplements the High Availability documentation available 
[here](http://brooklyn.apache.org/v/latest/ops/high-availability.html)
+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 infrastruct...@apache.org or file a JIRA ticket
with INFRA.
---

[GitHub] brooklyn-docs pull request #78: Adds details of setting up a HA master-slave...

2016-06-22 Thread aledsage 
Github user aledsage commented on a diff in the pull request:

https://github.com/apache/brooklyn-docs/pull/78#discussion_r68119397
  
--- Diff: guide/ops/high-availability/high-availability-supplemental.md ---
@@ -0,0 +1,142 @@
+---
+title: High Availability (Supplemental)
+layout: website-normal
+---
+
+This document supplements the High Availability documentation available 
[here](http://brooklyn.apache.org/v/latest/ops/high-availability.html)
+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
--- End diff --

I'd word it as `...on both VMs, following the instructions in `[Running 
Apache Brooklyn]({{ site.path.guide 
}}/start/running.html#install-apache-brooklyn).`


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

[GitHub] brooklyn-docs pull request #78: Adds details of setting up a HA master-slave...

2016-06-20 Thread drigodwin 
Github user drigodwin commented on a diff in the pull request:

https://github.com/apache/brooklyn-docs/pull/78#discussion_r67667031
  
--- Diff: guide/ops/high-availability-supplemental.md ---
@@ -0,0 +1,97 @@
+---
+title: High Availability (Supplemental)
+layout: website-normal
+---
+
+This document supplements the High Availability documentation available 
[here](http://brooklyn.apache.org/v/latest/ops/high-availability.html)
+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/amp-persistence` and 
both machines can write to the folder
+
+### Launching
+To start, download the latest Apache Brooklyn release on both VMs, extract 
it and navigate to the root folder:
+
+{% highlight bash %}
+wget -O apache-brooklyn-0.9.0-bin.tar.gz 
"https://www.apache.org/dyn/closer.lua?action=download=brooklyn/apache-brooklyn-0.9.0/apache-brooklyn-0.9.0-bin.tar.gz;
--- End diff --

You should use apache-brooklyn_{{site.brooklyn-version}} instead of naming 
a specific version 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 infrastruct...@apache.org or file a JIRA ticket
with INFRA.
---

[GitHub] brooklyn-docs pull request #78: Adds details of setting up a HA master-slave...

2016-06-20 Thread drigodwin 
Github user drigodwin commented on a diff in the pull request:

https://github.com/apache/brooklyn-docs/pull/78#discussion_r67666709
  
--- Diff: guide/ops/high-availability-supplemental.md ---
@@ -0,0 +1,97 @@
+---
+title: High Availability (Supplemental)
+layout: website-normal
+---
+
+This document supplements the High Availability documentation available 
[here](http://brooklyn.apache.org/v/latest/ops/high-availability.html)
--- End diff --

Would this not be better as a multiple section sub-section similar to 
locations?


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

[GitHub] brooklyn-docs pull request #78: Adds details of setting up a HA master-slave...

2016-06-20 Thread nakomis 
GitHub user nakomis opened a pull request:

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

Adds details of setting up a HA master-slave pair



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

$ git pull https://github.com/nakomis/brooklyn-docs ha-supplemental

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

https://github.com/apache/brooklyn-docs/pull/78.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 #78


commit a8f837a939a28a495a26403c78a0af624f107082
Author: Martin Harris 
Date:   2016-06-20T09:47:05Z

Adds details of setting up a HA master-slave pair




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