Github user aledsage commented on a diff in the pull request:
https://github.com/apache/brooklyn-docs/pull/102#discussion_r76941471
--- Diff: guide/ops/starting-stopping-monitoring.md ---
@@ -3,81 +3,119 @@ 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).
+**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).
-## Packages for RHEL/CentOS and Ubuntu
+<ul class="nav nav-tabs">
+ <li class="active impl-1-tab"><a data-target="#impl-1, .impl-1-tab"
data-toggle="tab" href="#">Vagrant</a></li>
+ <li class="impl-2-tab"><a data-target="#impl-2, .impl-2-tab"
data-toggle="tab" href="#">Centos / RHEL</a></li>
+ <li class="impl-3-tab"><a data-target="#impl-3, .impl-3-tab"
data-toggle="tab" href="#">Ubuntu / Debian</a></li>
+ <li class="impl-4-tab"><a data-target="#impl-4, .impl-4-tab"
data-toggle="tab" href="#">OSX / Linux</a></li>
+</ul>
-If you are using the `.rpm` or `.deb` package of Apache Brooklyn, then
Brooklyn
-will integrate with your OS service management. Commands such as
-`service brooklyn start` will work as expected, and Brooklyn's PID file
will be
-stored in the normal location for your OS, such as `/var/run/brooklyn.pid`.
+<div class="tab-content">
+<strong class="hidden started-pdf-include">Vagrant</strong>
+Now start the provided brooklyn instance supplying your brooklyn Download
credentials in place of the `myuser` and `mypassword` exbrooklynles below
-## Platform-independent distributions
+{% highlight bash %}
+$ user=myuser password=mypassword vagrant up brooklyn
+{% endhighlight %}
-The platform-independent distributions are packaged in `.tar.gz` and `.zip`
-files.
+If you do not know your username or password (it should have been provided
in your welcome email) please contact <a
href="mailto:[email protected]";>[email protected]</a> for assistance.
+You can check if brooklyn has launched successfully with the command:
-### Starting
+{% highlight bash %}
+$ vagrant ssh brooklyn --command 'sudo systemctl status brooklyn'
+{% endhighlight %}
-To launch Brooklyn, from the directory where Brooklyn is unpacked, run:
+The application logs can be tailed using:
{% highlight bash %}
-% bin/brooklyn launch > /dev/null 2>&1 & disown
+$ vagrant ssh brooklyn --command 'tail -f
/home/vagrant/cloudsoft-brooklyn-karaf/log/brooklyn.info.log'
+$ vagrant ssh brooklyn --command 'tail -f
/home/vagrant/cloudsoft-brooklyn-karaf/log/brooklyn.debug.log'
{% 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.
+</div>
+<div id="impl-2" class="tab-pane fade">
-See the [Server CLI Reference](server-cli-reference.html) for more
information
-about the Brooklyn server process.
+<strong class="hidden started-pdf-include">Centos / RHEL</strong>
-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.
+brooklyn is managed as a system service using the appropriate tool for
your system (e.g. systemd). When the brooklyn package is installed, the
`brooklyn` service is started for you.
+Now, as root (or using sudo), you can monitor brooklyn's status, and stop
and start it, with the following commands for systemd:
-### Stopping
+{% highlight bash %}
+$ systemctl status brooklyn
+$ systemctl stop brooklyn
+$ systemctl start brooklyn
+{% endhighlight %}
-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.
+The application should then output its logs to
`/opt/brooklyn/log/brooklyn.info.log` and
`/opt/brooklyn/log/brooklyn.debug.log`.
-For example:
+Brooklyn will integrate with your OS service management. Commands such as
`service brooklyn start` will work as expected, and Brooklyn's PID file will be
stored in the normal location for your OS, such as `/var/run/brooklyn.pid`.
+
+</div>
+
+<div id="impl-3" class="tab-pane fade">
+
+<strong class="hidden started-pdf-include">Ubuntu / Debian</strong>
+
+brooklyn is managed as a system service using the appropriate tool for
your system (e.g. upstart). When the brooklyn package is installed, the
`brooklyn` service is started for you.
+
+Now, as root (or using sudo), you can monitor brooklyn's status, and stop
and start it, with the following commands for upstart:
{% highlight bash %}
-% kill $( cat pid_java )
-{% endhighlight bash %}
+$ status brooklyn
+$ stop brooklyn
+$ start brooklyn
+{% endhighlight %}
+
+The application should then output its logs to
`/opt/brooklyn/log/brooklyn.info.log` and
`/opt/brooklyn/log/brooklyn.debug.log`.
+
+Brooklyn will integrate with your OS service management. Commands such as
`service brooklyn start` will work as expected, and Brooklyn's PID file will be
stored in the normal location for your OS, such as `/var/run/brooklyn.pid`.
+
+</div>
+
+<div id="impl-4" class="tab-pane fade">
+
+<strong class="hidden started-pdf-include">OSX / Linux</strong>
+
+To start Cloudsoft brooklyn (assuming you are in the
cloudsoft-brooklyn-karaf-{{ site.brooklyn-version }}/bin directory):
--- End diff --
Not "Cloudsoft". Search and remove all mention.
---
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 [email protected] or file a JIRA ticket
with INFRA.
---
