Repository: brooklyn-docs Updated Branches: refs/heads/master a45ad9664 -> 218ec136e
Fixed links Project: http://git-wip-us.apache.org/repos/asf/brooklyn-docs/repo Commit: http://git-wip-us.apache.org/repos/asf/brooklyn-docs/commit/d80395fc Tree: http://git-wip-us.apache.org/repos/asf/brooklyn-docs/tree/d80395fc Diff: http://git-wip-us.apache.org/repos/asf/brooklyn-docs/diff/d80395fc Branch: refs/heads/master Commit: d80395fcfdd58d48e197cbf2c5be259a39c18c09 Parents: a45ad96 Author: Duncan Godwin <[email protected]> Authored: Wed Jul 6 17:51:36 2016 +0100 Committer: Duncan Godwin <[email protected]> Committed: Wed Jul 6 17:51:36 2016 +0100 ---------------------------------------------------------------------- guide/java/entities.md | 2 +- guide/misc/javadoc/index.md | 2 +- guide/ops/production-installation.md | 12 ++++++------ guide/yaml/ansible/index.md | 2 +- guide/yaml/blueprinting-tips.md | 2 +- guide/yaml/configuring-vms.md | 2 +- guide/yaml/creating-yaml.md | 6 +++--- 7 files changed, 14 insertions(+), 14 deletions(-) ---------------------------------------------------------------------- http://git-wip-us.apache.org/repos/asf/brooklyn-docs/blob/d80395fc/guide/java/entities.md ---------------------------------------------------------------------- diff --git a/guide/java/entities.md b/guide/java/entities.md index b83bfc9..1e2623d 100644 --- a/guide/java/entities.md +++ b/guide/java/entities.md @@ -113,7 +113,7 @@ wiring for the sensors, and the effector implementations. In simple cases it may to capture the behaviour of the effectors in a simple methods. For example deploying a WAR to a cluster can be done as follows: -*This section is not complete. Feel free to [fork]({{site.path.guide}}/dev/code) the docs and lend a hand.* +*This section is not complete. Feel free to [fork](https://github.com/apache/brooklyn-docs) the docs and lend a hand.* <!--- TODO show an effector which recurses across children http://git-wip-us.apache.org/repos/asf/brooklyn-docs/blob/d80395fc/guide/misc/javadoc/index.md ---------------------------------------------------------------------- diff --git a/guide/misc/javadoc/index.md b/guide/misc/javadoc/index.md index 5cf9ebc..6841283 100644 --- a/guide/misc/javadoc/index.md +++ b/guide/misc/javadoc/index.md @@ -6,6 +6,6 @@ toc: ../../toc.json *Javadoc is not available as part of this build.* -Please see the [source code]({{site.path.guide}}/dev/code) to view javadoc. +Please see the [source code](https://github.com/apache/brooklyn) to view javadoc. <!-- This page is normally overwritten by generated javadoc. --> http://git-wip-us.apache.org/repos/asf/brooklyn-docs/blob/d80395fc/guide/ops/production-installation.md ---------------------------------------------------------------------- diff --git a/guide/ops/production-installation.md b/guide/ops/production-installation.md index b0110d5..12f25e8 100644 --- a/guide/ops/production-installation.md +++ b/guide/ops/production-installation.md @@ -15,19 +15,19 @@ To install Apache Brooklyn on a production server: This guide covers the basics. You may also wish to configure: -* [Logging](logging.md) +* [Logging](logging.html) * [Persistence](persistence/) -* [High availability](high-availability.md) +* [High availability](high-availability/) ### <a id="prerequisites"></a>Set up the Prerequisites -Check that the server meets the [requirements](requirements.md). +Check that the server meets the [requirements](requirements.html). Then configure the server as follows: * install Java JRE or JDK (version 7 or later) -* install an [SSH key]({{ site.path.guide }}/ops/locations/ssh-keys.html), if not available -* enable [passwordless ssh login]({{ site.path.guide }}/ops/locations/ssh-keys.html) +* install an [SSH key]({{ site.path.guide }}/ops/locations/index.html#ssh-keys), if not available +* enable [passwordless ssh login]({{ site.path.guide }}/ops/locations/index.html#ssh-keys) * create a `~/.brooklyn` directory on the host with `$ mkdir ~/.brooklyn` * check your `iptables` or other firewall service, making sure that incoming connections on port 8443 is not blocked * check that the [linux kernel entropy]({{ site.path.website }}/documentation/increase-entropy.html) is sufficient @@ -66,7 +66,7 @@ Let's setup some paths for easy commands. ### <a id="configuring-properties"></a>Configuring brooklyn.properties -Set up `brooklyn.properties` as described [here](brooklyn_properties.md): +Set up `brooklyn.properties` as described [here](brooklyn_properties.html): * Configure the users who should have access * Turn on HTTPS http://git-wip-us.apache.org/repos/asf/brooklyn-docs/blob/d80395fc/guide/yaml/ansible/index.md ---------------------------------------------------------------------- diff --git a/guide/yaml/ansible/index.md b/guide/yaml/ansible/index.md index 1cda04e..3f2999c 100644 --- a/guide/yaml/ansible/index.md +++ b/guide/yaml/ansible/index.md @@ -7,7 +7,7 @@ children: --- This guide describes how Brooklyn entities can be created using the Ansible infrastructure management tool - ([ansiblestack.com](ansiblestack.com)). + ([ansible.com](ansible.com)). At present Brooklyn provides basic support for Ansible, operating in a 'masterless' mode. Comments on this support and suggestions for further development are welcome. http://git-wip-us.apache.org/repos/asf/brooklyn-docs/blob/d80395fc/guide/yaml/blueprinting-tips.md ---------------------------------------------------------------------- diff --git a/guide/yaml/blueprinting-tips.md b/guide/yaml/blueprinting-tips.md index 6f02746..c918174 100644 --- a/guide/yaml/blueprinting-tips.md +++ b/guide/yaml/blueprinting-tips.md @@ -48,7 +48,7 @@ and to use these as the target for a BYON location. Docker containers provide a convenient way to test blueprints (and also to run blueprints in production!). -The [Clocker project](www.clocker.io) allows the simple setup of Docker Engine(s), and for Docker +The [Clocker project](http://www.clocker.io) allows the simple setup of Docker Engine(s), and for Docker containers to be used instead of VMs. For testing, this allows each run to start from a fresh container (i.e. no install artifacts from previous runs), while taking advantage of the speed of starting containers. http://git-wip-us.apache.org/repos/asf/brooklyn-docs/blob/d80395fc/guide/yaml/configuring-vms.md ---------------------------------------------------------------------- diff --git a/guide/yaml/configuring-vms.md b/guide/yaml/configuring-vms.md index 97fb9d0..7ae341f 100644 --- a/guide/yaml/configuring-vms.md +++ b/guide/yaml/configuring-vms.md @@ -28,4 +28,4 @@ including: * `machineCreateAttempts` (for dodgy clouds, and they nearly all fail occasionally!) * and things like `imageId` and `userMetadata` and disk and networking options (e.g. `autoAssignFloatingIp` for private clouds) -For more information, see [Operations: Locations](../ops/locations/). +For more information, see [Operations: Locations]({{ site.path.guide }}/ops/locations/index.html). http://git-wip-us.apache.org/repos/asf/brooklyn-docs/blob/d80395fc/guide/yaml/creating-yaml.md ---------------------------------------------------------------------- diff --git a/guide/yaml/creating-yaml.md b/guide/yaml/creating-yaml.md index 8bc22c4..603b0cd 100644 --- a/guide/yaml/creating-yaml.md +++ b/guide/yaml/creating-yaml.md @@ -25,7 +25,7 @@ Here's a very simple YAML blueprint plan, to explain the structure: * The `name` is just for the benefit of us humans. * The `location` specifies where this should be deployed. - If you've [set up passwordless localhost SSH access](../ops/locations/#localhost) + If you've [set up passwordless localhost SSH access]({{ site.path.guide }}/ops/locations/#localhost) you can use `localhost` as above, but if not, just wait ten seconds for the next example. * The `services` block takes a list of the typed services we want to deploy. @@ -37,7 +37,7 @@ then in the "Create Application" dialog at the web console (usually [http://127.0.0.1:8081/](http://127.0.0.1:8081/), paste the copied YAML into the "Yaml" tab of the dialog and press "Finish". There are several other ways to deploy, including `curl` and via the command-line, and you can configure users, https, persistence, and more, -as described [in the ops guide](../ops/). +as described [in the ops guide]({{ site.path.guide }}/ops/). [](web-console-yaml.png) @@ -57,7 +57,7 @@ Topics to explore next on the topic of YAML blueprints are: {% include list-children.html %} Plenty of examples of blueprints exist in the Brooklyn codebase, -so another starting point is to [`git clone`]({{ site.path.guide }}/developers/code/index.html) it +so another starting point is to [`git clone`]({{ site.path.website }}/developers/code/index.html) it and search for `*.yaml` files therein. Brooklyn lived as a Java framework for many years before we felt confident
